Privacy Policy
Your health data is yours. ORLENE is private by design — this page explains, in plain language, what we collect, what we never collect, and what you control.
In short
- Your health data — periods, symptoms, moods, pregnancies, kick sessions, medications, journals, AI conversations — is private to you.
- We never sell your health data.
- We never show your health data to advertisers, and we never use it to target marketing.
- Analytics are anonymised aggregates only — never per-user rows, never health facts attached to an identity.
- You can export your data, and you can delete your account.
Separate boundaries
Your data lives in separate access boundaries: public content, profile metadata, health data, AI data, payment data, and audit data. Health data is private by default and protected by row-level security — every read is scoped to your account, and no other user, admin, or anonymous visitor can read it. Admins cannot read an individual user's health data. Published educational content is the only thing an anonymous visitor can read.
What we collect
- Account data: your email address and profile details you provide (name, goal, dates you choose to enter).
- Health data you log: periods, symptoms, moods, pregnancies, kick sessions, medications, and journal entries. You choose what to log; nothing is collected without you entering it.
- AI conversations: only what you type to Ask ORLENE, and only with your AI consent. Journal entries are never sent to the AI unless you paste them yourself.
- Usage signals: anonymised, aggregate events (for example, how many users completed onboarding this week). Small groups are suppressed so no one can be identified.
What we never do
- Never sell health data, or any personal data.
- Never put health data in a notification, an email subject, or an analytics event.
- Never send marketing in your first 30 days, and never more than one marketing message a week after that.
- Never let an admin read your health records.
What you control
- Notification preferences, per category, including quiet hours.
- AI consent and journal consent, as separate toggles.
- Analytics and crash reporting, both off by default.
- Export of your data, and account deletion — deletion needs explicit confirmation plus re-authentication, and has a 7-day grace period during which signing in cancels it.
Sign-in and sessions
Sign-in uses Supabase Auth. Your session is stored in your browser so you stay signed in; signing out clears your locally cached health data from the device, while your server data is preserved for your next sign-in.