Privacy Policy
Plain language. No surprises.
Effective date: March 21, 2026 · Developer: Chris Murphy
Introduction
Daisies in the Dark is a personal tracking app built for people navigating chronic illness. Your health data is sensitive, and we take that seriously. This policy explains what we collect, why, and how we protect it — in plain language, not legalese.
If you have questions at any point, email us: chris@daisiesinthedark.com
What We Collect
- · Account information — your email address, used to create and access your account.
- · Health and symptom data — pain levels, energy, mood, symptoms, and any journal entries you choose to log. You control what you share.
- · Usage data — basic, anonymized analytics such as app opens and feature usage. This data contains no personally identifiable information and is used only to understand how the app is being used in aggregate.
How We Use Your Data
- · To provide the core app functionality: logging, pattern insights, and Daisy chat.
- · To improve the app over time, using anonymized and aggregated analytics only.
We do not sell your data. We do not share your data with third parties except as required by law.
Data Storage
Your data is stored securely using Supabase, a cloud database provider. All data is encrypted in transit (TLS) and at rest. Your health data is tied to your private account and is not accessible to other users.
Your Rights
- · You can request a copy of your data at any time by emailing us.
- · You can delete your account and all associated data from within the app (Settings → Account → Delete Account) or by emailing us directly.
- · We will fulfill all deletion requests within 30 days.
Children's Privacy
Daisies in the Dark is not directed at children under 13. We do not knowingly collect personal data from children. If you believe a child has provided us with data, please contact us and we will delete it promptly.
Changes to This Policy
We may update this policy from time to time. We'll notify users of any significant changes through the app or via email. The effective date at the top of this page will always reflect the most recent revision.