Privacy policy (draft)
DRAFT. Not reviewed by a lawyer. This text was written from what the app and its server do as of 22 November 2026. It has had no legal review, it is not in force, and it will change. Items shown like [this] are placeholders for facts that are not settled yet.
This page is in English only for now. Esta página solo está disponible en inglés por ahora. Esta página só está disponível em inglês por enquanto.
Family Flow Tracker is a period tracker for one person or several. It handles health information, so this policy tries to say exactly what happens to it, including the limits of our protections.
1. Who we are
Family Flow Tracker is operated by [operating entity name], [postal address] (“we”). Contact: support@familyflowtracker.com.
2. The short version
- If you use the app without an account, what you log stays on your phone and we never receive it.
- If you sign in and agree, your own tracking is saved to your account on our server.
- Profiles of other people on your phone are sent to our server only if you turn on Backup, or hand a profile over to the person it is about.
- There is no advertising SDK and no analytics SDK in the app. We do not sell personal data and we do not use it for advertising.
- Notes are never shared with other users.
- Account data is encrypted on our server, but our server holds the key. It is not end-to-end encrypted.
3. What is collected, by how you use the app
3.1 Without an account (everything on one phone)
Period days, flow, symptoms, mood, notes, the names and colours of profiles, an optional age range (13–17 or 18+) per person, your settings and the estimates the app works out are stored in an encrypted file on your phone. None of it is sent to us. The only thing the app sends in this mode is the anonymous counts in section 6, which you can turn off.
3.2 With an account
When you sign in we store your email address and a display name. Sign-in is by a one-time code sent to your email; there is no password. [Sign in with Apple and Google are planned; when they work, we will also store the identifier Apple or Google gives us for you]
Before any health information is saved to your account the app asks for your agreement. If you agree, we store on our server:
- the period days, flow, symptoms and mood you log for yourself;
- your notes (only ever shown to you);
- estimates of upcoming periods and patterns, which the server works out from your entries;
- your optional age range;
- when you agreed and to which version of the wording.
If you choose “Not now”, your tracking stays on your phone. You can withdraw your agreement in Profile at any time and delete what is on the server.
We also keep the date your account was created, the date it was last active (a date, not a time), your sign-in sessions, and your plan (which plan, since when). If notifications that need our server are switched on, we store the push token your phone’s notification service gives the app. [The current app schedules reminders on the phone and does not send a push token; confirm before launch]
3.3 Sharing between accounts
If you create an invite code and someone redeems it, we store the connection between the two accounts and the switches you chose: period days, predictions, flow, symptoms, mood, whether they may log for you, and whether their phone may remind them about you. The other person sees only what you switched on, and your display name. Notes are never included. You can change the switches or stop sharing at any time and it takes effect on their next request to the server. Invite codes can be used once and expire.
If you allow someone to log for you, each entry records who logged it. For 30 days you can see earlier values of days that were changed or deleted and put them back.
3.4 Backup of other people’s profiles
Backup is off by default. If you turn it on, the profiles of other people kept on your phone are stored on our server under your account: each profile’s name, colour and age range, everything logged for them, and the notes written for them. The app does not ask the people in those profiles. The account holder agrees on their behalf, and the app tells the account holder to check with them first. We record that this agreement was given, when, and to which wording. You can turn Backup off at any time and choose to delete the copies from the server. [Lawyer to settle: whether an account holder’s agreement is a sufficient basis for storing another person’s health data, especially for people aged 13 to 17]
3.5 Handing a profile to the person it is about
You can give a profile its own account. That one profile is uploaded, a code is made, and the other person redeems it on their phone after seeing what your phone will keep seeing. The first phone removes its copy only after the server confirms.
3.6 Purchases
Purchases are made through Apple’s App Store or Google Play. We do not receive your card details. We receive whether you have a plan, which one, and store transaction identifiers. [Purchase service provider, planned: RevenueCat, which would receive a random identifier for your install or account and no health data. Not yet integrated]
3.7 Age
The app asks for your birth year to check that you are 13 or older. The birth year is not stored and is not sent to us. If the answer is under 13, the app remembers on that phone only that it is not available.
3.8 Support email
If you write to us we receive your email address and whatever you write. Please do not send health details.
4. What we do not collect
- No advertising identifier, no location, no contacts, no photos.
- No advertising, analytics, attribution or crash-reporting SDK is in the app.
- No record of which features an account uses.
- Apple Health and Health Connect are not read or written.
5. How we use it
Only to run the app for you: to save and sync your tracking, to work out estimates, to show people what others chose to share with them, to check your plan, to keep the service secure, and to answer you when you write. Health information is never used for advertising and never sold. The recommended-products list in the app is the same for everyone and is not based on anything you log.
6. The four anonymous counts
To know whether the app is used at all, it sends four counts: first open, second person added, plans shown and purchase completed. Each is sent with a random identifier made up for that install and the date, and nothing else: no account, no name, nothing about anyone’s cycle. The server refuses any other field, refuses a request that carries a sign-in, and stores no address with it. The raw rows are deleted after 30 days; a total per day is kept. You can turn the counts off in Profile (“Anonymous usage counts”); then nothing is sent.
One honest limit: the counts and your signed-in requests come from the same phone, so someone able to watch network traffic could notice both. We do not store anything that links them.
7. Where it is stored and how it is protected
- On your phone: the app’s data file is encrypted, with the key kept in the phone’s secure storage. You can also turn on an app lock that uses the phone’s biometrics or passcode.
- In transit: the app talks to our server over an encrypted connection (HTTPS).
- On our server: entry details (whether a day is a period day, flow, symptoms, mood), notes and estimates are encrypted field by field with AES-256-GCM, using a key that is kept outside the database.
- Not field-encrypted on the server: which dates have an entry (but not what the entry says), display names, the optional age range, email addresses, who shares with whom and with which switches, and when an estimate was last worked out.
- The limit of this: our server holds the encryption key, so it can read account data in order to work. That means the operator, anyone who fully compromised the server, or a party with a valid legal demand could obtain account data. Data that stays on your phone is not held by us and cannot be handed over by us.
The server is located in [hosting provider and country; not yet chosen]. No iCloud or other third-party cloud storage is used for your tracking.
8. Who else receives data
We do not sell personal data and we do not share it for advertising. These service providers handle data for us:
| Provider | What for | What it can see |
|---|---|---|
| [hosting provider] | Runs the server and database | Stored account data (sensitive fields encrypted as in section 7) |
| [network edge provider] | Carries traffic between the app and the server | Can technically see the content of requests in transit |
| [email provider] | Sends sign-in codes and account notices | Your email address; never cycle data |
| Apple and Google | App stores, purchases, notifications [and sign-in, when enabled] | Purchase and device information under their own policies. Notifications sent through them carry no health content |
| [purchase service provider, if used] | Confirms purchases | A random identifier and purchase status; no health data |
Other users see what you chose to share with them (section 3.3). We may disclose data when the law requires it; we can only disclose what we hold.
The recommended-products page in the app links to Amazon. A link opens in your browser only when you tap it, and the app sends nothing about you or your cycle. See product links.
9. How long we keep it
| Data | Kept |
|---|---|
| Your account and tracking | Until you delete it or delete your account |
| Deleted entries, and earlier values of changed entries (the 30-day history) | 30 days, so that a change made by you or by someone logging for you can be undone, then removed |
| Used, cancelled or expired invite and hand-over codes | 7 days after that moment |
| Sign-in sessions | Until they expire or you sign out |
| Records of account events | 12 months; after account deletion they no longer carry the account identifier |
| Server request logs (route and result only; no content, no address) | 14 days |
| Anonymous counts | Raw rows 30 days; daily totals kept |
| Accounts not used for a long time | [not decided; a 24-month rule is proposed but nothing is deleted automatically today] |
| Server backups | [no server backups exist today; state the backup retention here when they do] |
10. Your choices and rights
- Export. “Export my data” gives you your own profile and entries as text. “Export what my account holds” gives you everything the server keeps for your account. It does not include what other people share with you.
- Withdraw agreement. “Stop saving to my account” stops sending; you can then delete your entries from the server and keep them on your phone.
- Delete. “Delete account” removes your account and everything of it on our server and erases the phone. See how to delete your account and data, which also explains what is kept.
- Stop sharing with any person, or change what they see, at any time.
- Turn off the anonymous counts, reminders and Backup in Profile.
- You can also ask us by email at support@familyflowtracker.com.
[Rights under specific laws, how to appeal a refused request, and how to complain to a regulator: to be written after legal review]
11. Ages
The app is for people aged 13 or older, and that includes every person tracked in it. We do not knowingly collect data from children under 13. People aged 13 to 17 control their own sharing in the same way as adults: there is no parental override. If you believe a child under 13 has an account, write to support@familyflowtracker.com and we will delete it.
12. Changes
If this policy changes in a way that matters, we will say so in the app before the change applies. [effective date and version]
13. Contact
support@familyflowtracker.com
[operating entity name], [postal address]
For the lawyer: facts that must be settled before this is published
This list is part of the draft and must be removed before publication.
- The operating entity’s legal name and address, and who the data controller is.
- The jurisdictions the app launches in (the owner has not specified launch regions) and the governing law.
- Consumer health data laws: Washington’s My Health My Data Act and similar state laws (Nevada, Connecticut). Whether a separate consumer health data privacy policy and separate consent are needed, and their wording.
- Other US state privacy laws and whether “sensitive data” rules apply.
- GDPR and UK GDPR if offered in Europe: legal basis for special-category data, a representative, international transfers, data protection impact assessment, regulator contact.
- Brazil’s LGPD if offered in Brazil (the app has a Portuguese version), including its rules on teenagers’ data and age assurance.
- COPPA position: the app is for 13+, with a self-declared birth-year check. Whether that is sufficient, and what to do on learning of an under-13 user.
- Minors aged 13 to 17: whether consent by the teen is valid in each launch jurisdiction and whether parents have access rights.
- Whether an account holder can validly consent to storing another person’s health data (Backup of other people’s profiles, section 3.4).
- Names of the service providers (hosting, network edge, email, purchases) and their data-processing terms.
- Retention of inactive accounts, retention of server backups, and breach-notification duties and deadlines.
- The response time for requests by email, and how identity is confirmed.
- How legal demands for reproductive health data are handled.
- Apple and Google store privacy answers must match this policy.