Privacy Policy

Effective date: 2026-10-08 Contact: [email protected]

PCOS Coach ("we", "us", "our") is a self-care companion for people managing PCOS. Your health data is sensitive, and we treat it that way. This document explains what we collect, how we use it, and the controls you have.

Data we collect

We collect only what we need to run the product:

• Account data: email address, account creation date, sign-in provider (Apple / Google / email), and an account identifier used internally and by our analytics and subscription providers.
• Contact email (optional): during setup we offer "Continue with Apple" so you can share your email with us; we use it only to write to you now and then and ask how Peach is working for you — we do not send newsletters or marketing emails. You can skip it. Apple lets you share your real address or a private relay address ("Hide My Email"), and we only receive the one you choose — not your name, and no account is created on our servers. If you share it, we keep it on your device and with RevenueCat and PostHog (see "Who we share with"), linked to your account identifier. You can ask us to stop or have it removed at any time by replying to any of our emails or writing to [email protected], and you can stop Peach from using your Apple ID in iOS Settings → your name → Sign-In & Security → Sign in with Apple.
• How you found Peach: your answer to "How did you find Peach?" during setup and, from our attribution provider AppsFlyer, whether your install came from an ad or not, and from which channel and campaign.
• Tracker data: cycle phase, period flow, mood scores, symptoms, free-text notes, weights, and habit completions you choose to log.
• Profile data: birthday, height, weight goal, gender, activity level, PCOS subtype, and dietary preferences from onboarding.
• Photos you submit: meal photos and body/scalp/hair progress photos you choose to capture. Meal photos are sent to our AI provider for a nutrition estimate; body and scalp/hair progress photos stay on your device and are never uploaded. Neither is ever used for advertising.
• Recipes you save: which recipes you've kept across regenerations.
• Feedback you send us: if you answer "What made you cancel?" or use Settings → Send Feedback, we store your answer and message — and your email address only if you type it in, so we can reply. We attach your app version, language, and subscription plan, never your health data.
• Device data: OS version, app version, locale, and the region set on your device (a two-letter country code from your settings, not your location). Used to debug crashes, adapt the UI, and understand where Peach is used.

We do not collect precise location, contacts, photos outside what you explicitly attach, or social-graph data. See "App Tracking Transparency & advertising identifier" below for how the iOS advertising identifier (IDFA) is handled.

How we use it

• To operate the app: when you log a symptom, we store it; when you ask Peach, we send your message to our AI provider so Peach can answer.
• To personalize recipes and insights from your tracker data.
• To process subscription payments via Apple In-App Purchase and RevenueCat, and to send billing events (purchase, renewal, cancellation, refund) from RevenueCat to our analytics tool for all subscribers, tied to your account identifier — never your name or payment details.
• To improve the product through usage analytics — see "Analytics" below for exactly what's on by default, what's opt-in, and how to turn it off.
• To write to you, if you gave us your email: occasional questions about how Peach is working for you. No newsletters or marketing emails.
• To measure which channels and campaigns bring new users (marketing attribution) via AppsFlyer — see "Who we share with" below.
• To comply with legal obligations.

We do not sell your data. We do not use your data to train third-party AI models — our AI provider, OpenAI, operates under commercial terms that prohibit training on our customer prompts.

Analytics

We use PostHog, hosted in the United States, to understand how Peach is used and to fix what's broken. Every event is tied to your account identifier. If you gave us your email during setup, it is stored on that same analytics profile, so we know who we are writing to; the events themselves never contain your email. We never send raw chat text, notes, recipe or food names, medication names, exact health dates, or photo data to PostHog.

• Usage analytics (which screens you open, taps, load times, errors, how you found Peach, and the region set on your device — never anything about your cycle, symptoms, or health logs): on by default. You can turn it off at any time in Settings → Privacy & data → "Analytics & usage data." If you already made a choice there, or in the in-app question we used to show in the EU, EEA, UK, and Switzerland, that choice is kept.
• Health-related analytics (that a cycle log, symptom check-in, or reminder happened — never the specific value, date, or content): off by default, regardless of your usage-analytics choice above. It only turns on if you separately enable Settings → Privacy & data → "Health data in analytics," and you can turn it back off at any time.
• Billing events: purchase, renewal, cancellation, and refund events are sent from RevenueCat to PostHog for all subscribers, tied to your account identifier. This happens independently of the two toggles above, because it is contractual/billing information, not product-usage or health data.
• We do not use IP-based location (GeoIP is disabled on our PostHog project), and we do not record session replay.
• Turning usage analytics off stops collection from that moment. To erase what was already collected, delete your account or write to us.
• Deleting your account (Settings → Delete account) also deletes your PostHog analytics profile and its events.

App Tracking Transparency & advertising identifier (IDFA)

Peach does not currently show Apple's App Tracking Transparency (ATT) prompt, so your device's advertising identifier (IDFA) is not collected. To understand which marketing channel brought you to Peach, AppsFlyer relies on your device's vendor identifier (IDFV) and Apple's aggregated install signals instead. If we ever start asking, declining will keep the IDFA uncollected, and your answer will never change your analytics settings.

Who we share with

We share data only with the infrastructure providers that make the app run:

• Supabase — stores your account, tracker, and profile data. Hosted on AWS in the EU region. https://supabase.com/privacy
• OpenAI — receives the meal photos you submit for analysis, so the AI can score your food. Scalp/hair photos are never sent to OpenAI — they stay on your device. OpenAI processes this under their commercial terms and does not train on it. https://openai.com/policies/privacy-policy
• Open Food Facts — when you scan a barcode or search for a food, we send the scanned barcode or your food-name search term to look up public nutrition data. No account id, token, or device identifier is attached, so the request is not tied to you. https://world.openfoodfacts.org/terms-of-use
• Apple / Google — handle sign-in via "Sign in with Apple" or Google OAuth, if you choose those methods. During setup, "Continue with Apple" gives us the email address you choose to share.
• RevenueCat — processes subscription state and entitlements, forwards billing events (see "Analytics" above) to PostHog on our behalf, and stores your contact email if you gave one. https://www.revenuecat.com/privacy
• PostHog — product analytics and billing-event storage, hosted in the US, including your contact email if you gave one. See "Analytics" above for exactly what is and isn't sent, and how to control it. https://posthog.com/privacy
• Brevo — delivers the feedback you send us to our inbox: your answer, your message, and your email address if you gave one. https://www.brevo.com/legal/privacypolicy/
• AppsFlyer — mobile attribution. So we can understand which channels and campaigns bring new users, AppsFlyer processes your device's vendor identifier (IDFV), IP address, install, and basic in-app events (e.g. account created, subscription started). It tells us whether your install came from an ad and from which channel and campaign, and we keep that on your analytics profile. AppsFlyer never receives your health data, your logs, or your email. https://www.appsflyer.com/legal/services-privacy-policy/

We do not sell your data and we do not work with data brokers. AppsFlyer (above) is used only to measure marketing attribution, never to serve you ads.

Data retention

• Account, profile, and tracker data: retained for as long as your account is active.
• Feedback you send us: kept until you delete your account, or sooner if you ask us at [email protected].
• Contact email: kept until you delete your account or ask us to remove it.
• On account deletion: removed from our live databases within 30 days. Your PostHog analytics profile and its events are deleted as part of that same process.
• Backups: fully purged within 90 days of deletion.

Your rights

You can, at any time, from inside the app:

• Access a copy of your data — Settings → Export my data
• Correct any tracker entry — open the day and edit
• Delete your account and all associated data, including your analytics profile — Settings → Delete account
• Withdraw consent to processing — turn off analytics anytime in Settings → Privacy & data without deleting your account, or uninstall the app and delete your account

If you live in the EEA, UK, or California, you have additional rights under GDPR / CCPA including data portability, restriction of processing, and the right to lodge a complaint with your supervisory authority. Contact us at [email protected] to exercise these rights.

Children

PCOS Coach is not intended for users under 13. We do not knowingly collect data from children under 13. If you believe a child has used the app, contact us at [email protected] and we will delete the account.

Apple Health (HealthKit)

Connecting Apple Health is optional and off by default. If you tap "Connect to Apple Health" in the Tracker and grant permission, PCOS Coach will:

• Write the entries you log — weight, meals, water, workouts, cycle/menstrual flow, and symptoms — to Apple Health, so they're available to your other health apps.
• Read weight, water, steps, active energy, and cycle data from Apple Health to keep your Tracker in sync.

Health data read from or written to Apple Health stays on your device and in Apple Health; we do not upload your HealthKit data to our servers, use it for advertising, or share it with third parties. You can revoke access at any time in iOS Settings → Privacy & Security → Health, and you can disconnect in the app. If you never connect Apple Health, we collect health data only via what you log directly in PCOS Coach.

Security

• All data in transit uses TLS 1.2+.
• Data at rest is encrypted by Supabase (AES-256).
• Row-level security (RLS) is enforced on every database table — your account can only access rows belonging to your user id.
• Service-role keys live in our backend secret store, never in the mobile app or in source control.

Medical disclaimer

PCOS Coach is a self-care tracking and education tool. It is not a medical device, and it does not provide medical diagnosis, treatment, or advice. Always consult a qualified clinician for medical decisions, including about your medications, supplements, and reproductive care.

Changes to this policy

We will notify you in-app and via email at least 14 days before any material change to this policy.

Contact

Questions or requests: [email protected].