Privacy Policy

1. Who we are

PeriFlow ("we", "us", "our") is operated by the developer of the PeriFlow mobile app, available on the Apple App Store and Google Play. This Privacy Policy explains how we handle personal information when you use the app or this website (periflow.io).

We are the data controller for the personal information described below.

2. What we collect

2.1 Account information

• Email address — required to sign in via magic link, Sign in with Apple, or Sign in with Google.
• Display name — optional. We use whatever Apple or Google passes us when you sign in via those providers; otherwise we derive a placeholder from your email's local-part.
• Authentication metadata — provider type (apple / google / email), unique provider identifier, timestamps of sign-in events. Managed by our authentication provider, Supabase Auth.

2.2 Health and wellness data

This is special category data under the UK and EU General Data Protection Regulation (Article 9). We treat it with the corresponding extra care.

• Cycle data — period start dates and the days you tag as bleeding.
• Symptom logs — the symptoms you record (energy, hot flashes, sleep, mood, brain fog, anxiety, and others) and the values you assign on each day.
• Fasting sessions — when you start and end a fast, the goal you set, the optional meal that broke the fast, the cycle phase you were in.
• Meal logs — meals you marked as eaten or rated, and any meals you saved as favourites.
• Movement and exercise check-ins — the daily activities you ticked off.
• Journal entries — free-form notes you write, with the optional mood you tagged them with.
• Relief exercise history — completions of breathing, body-scan, and grounding exercises.
• Profile preferences — diet style, weight unit, weight (you can leave this blank), baseline symptom rating.

2.3 Subscription and billing

• Subscription status — whether you are on free or premium, plan type (monthly or annual), trial / active / cancelled / expired state, current period end date.
• We never see your payment card or bank details. Apple and Google process your payment under their own privacy policies; our subscription processor (RevenueCat) tells us which entitlement you hold.

2.4 Consent records

• Audit log — when you opted in to processing of your health data, and if you ever withdrew. Required by GDPR Article 7.

2.5 Technical and diagnostic data

• App-level event telemetry — anonymous counts of which screens are viewed and which features are tapped, used to understand which parts of the app are useful. We do not log symptom values, cycle dates, or any free-text content to analytics.
• Crash reports — if the app crashes, we may receive a stack trace and basic device model / OS version. We do not attach your account identifier to crash reports.
• Standard server logs — IP address, timestamp, and request type for security and abuse prevention. Retained for up to 30 days.

2.6 What we do not collect

• Your contacts, photos, location, microphone, camera, calendar, or files (we don't request permission for any of these).
• Health data from Apple Health, Google Fit, or any wearable — unless and until we add an explicit opt-in integration in a future version, and only with your permission at that time.
• Third-party advertising identifiers. PeriFlow contains no advertising and no advertising SDKs.

3. How we use it

• To run the app — calculating your cycle phase, suggesting meals, tracking fasts, surfacing patterns from your symptoms.
• To sync across your devices — so when you sign in on a new phone or tablet, your data is there.
• To process your subscription — verifying entitlement and renewing or cancelling as you choose.
• To answer your support requests — when you email hello@periflow.io.
• To improve the app — using the anonymous event telemetry described in 2.5.
• To meet legal obligations — including responding to lawful requests and fulfilling our regulatory responsibilities.

We do not use your data to train machine-learning models, sell it to anyone, share it with insurers, share it with advertisers, or use it for marketing purposes outside of the optional in-app prompts we send to your registered email.

4. Legal basis (UK / EU users)

Under UK GDPR and EU GDPR, we rely on the following lawful bases:

• Consent (Article 6(1)(a) and Article 9(2)(a)) — for processing your health data. You give this consent during onboarding and may withdraw it at any time by deleting your account.
• Contract (Article 6(1)(b)) — for account creation, sign-in, subscription processing, and providing the core app features you've signed up for.
• Legitimate interests (Article 6(1)(f)) — for security, fraud prevention, anonymous app-level telemetry, and crash reports. Our interest is keeping the app secure and working; the impact on you is minimal.
• Legal obligation (Article 6(1)(c)) — for compliance with laws applicable to us.

5. Who we share it with

We use the following processors. Each is bound by a contract that limits how they use your data and prohibits them from using it for their own purposes.

• Supabase — managed Postgres database and authentication. Hosts your account, cycle, symptom, and other in-app data. EU region (eu-west-1, Ireland). Supabase Privacy Policy.
• RevenueCat — subscription state management. Sees your anonymous user identifier and subscription events; does not see your email or health data. RevenueCat Privacy Policy.
• Apple — App Store distribution, Sign in with Apple, in-app purchases. Subject to Apple's Privacy Policy.
• Google — Google Play distribution, Sign in with Google, in-app purchases. Subject to Google's Privacy Policy.

We may also disclose information if required by law (court order, valid government request) or to protect the rights, safety, or property of PeriFlow or others. We will challenge overbroad requests where we have a basis to do so.

If PeriFlow is acquired or merged, your data may transfer to the acquiring entity, but only on the condition they continue to honour this policy or give you advance notice and the chance to delete your account.

6. Where it lives, how long we keep it

Your data is stored on Supabase infrastructure in Ireland (eu-west-1). RevenueCat operates from the United States.

We keep your data for as long as your account is active. When you delete your account from inside the app (Settings → Delete Account), we wipe every row across all tables and the authentication record itself within seconds. Backups are retained for up to 30 days for disaster recovery, after which point your data is irrecoverable.

Server logs and crash reports are retained for up to 30 days.

7. How we protect it

• Encrypted in transit — TLS 1.2 or higher between your device, our servers, and our processors.
• Encrypted at rest — AES-256 on the database disk.
• Row-level security — every table is protected by database policies that mathematically prevent one user from reading another's data, even in the case of a code bug.
• Magic-link authentication — no passwords to be reused or leaked.
• Apple Sign-In and Google Sign-In — verified via cryptographically signed identity tokens; PeriFlow never sees your Apple or Google password.
• No advertising SDKs — there are no third-party trackers in the app or on this website.

No system is perfect. If we ever experience a personal-data breach affecting you, we will notify you and the relevant supervisory authority within 72 hours of becoming aware, in line with UK / EU GDPR requirements.

8. Your rights

You have the right to:

• Access the data we hold about you. The app's "Export My Data" feature gives you a clinical-format report of everything we store; an alternative machine-readable export is available on request to hello@periflow.io.
• Correct inaccurate data. Most fields are editable in the app's Settings or directly inside the relevant feature (cycle calendar, journal, etc.). For anything you cannot edit, email us.
• Delete your data. Use Settings → Danger Zone → Delete Account inside the app. This wipes everything within seconds. Backups are purged within 30 days.
• Restrict or object to processing — for example, by withdrawing consent for the optional anonymous telemetry. Email us if you want to exercise this.
• Data portability — receive a copy of your data in a structured, machine-readable format. Email us to request this.
• Withdraw consent — at any time, by deleting your account.
• Lodge a complaint with a supervisory authority. In the UK, the Information Commissioner's Office (ico.org.uk). In the EU, your member state's data protection authority.

We aim to respond to all data-subject requests within 30 days.

9. Children

PeriFlow is intended for adults aged 18 and over. The app's content and features are designed for women navigating perimenopause, typically aged 40–55. We do not knowingly collect personal information from anyone under 18. If you believe we have inadvertently collected information from a minor, please contact us and we will delete it.

10. International transfers

If you are outside the EU / UK, your data is still stored on EU infrastructure. Where a processor (such as RevenueCat) is based outside the EU / UK, transfers are protected by appropriate safeguards including Standard Contractual Clauses approved by the European Commission and the UK Information Commissioner.

11. California residents

If you are a California resident, the California Consumer Privacy Act (CCPA, as amended by the CPRA) gives you rights similar to those described in section 8: to know what personal information we collect, to delete it, to correct it, and to opt out of any "sale" or "sharing" of personal information. We do not sell or share personal information as those terms are defined under the CCPA. To exercise any CCPA right, email hello@periflow.io.

12. Changes to this policy

If we make a material change to this policy, we will post the updated version here, change the "Last updated" date, and notify you in-app (and by email, where applicable) before the change takes effect. Continued use of PeriFlow after a change means you accept the updated policy. Past versions are available on request.

13. Contact

For privacy questions, data-subject requests, or to report a concern:

hello@periflow.io