femmli app privacy notice
This is the privacy notice for the femmli app. For The Inner Circle, see our main privacy notice.
What we collect
| What | Examples |
|---|---|
| Account | Email, first and last name, and — if you sign in with Google — the profile image and provider identifiers Google returns. |
| Symptoms | The moods, symptoms, flow and free-text notes you log, with the day you logged them for. |
| Your own symptom names | Anything you add under “Other”. |
| Medications | Name, dose, schedule, route, when you started and stopped, and which days you marked as taken. |
| Wearable and hormone measurements | If you connect a device: heart-rate variability, sleep, temperature and similar, as one measurement about one person at one moment — plus the partner's original payload. |
| Your sign-up answers | Age range, cycle status, what you want help with, symptoms you have noticed. |
| Insights and your feedback | The suggestions we showed you and whether you said they helped. |
| Consent decisions | What you agreed to, which wording you saw, when, and whether you withdrew. |
| Access records | Who read or changed which record, when, and why. No health values. |
| Technical | Session records, IP address, user agent. |
Why we use it
- To show you your own history and to draw your charts.
- To look for patterns in your own data and suggest what might help. The pattern-finding runs on your data alone, not on a population model.
- To keep the service running and secure, and to answer a privacy request.
- Only if you tick the box: to help improve and train the product, and to let a language model phrase a pattern we found into a readable sentence. Both are separate, optional, and default to off.
Who else sees it
We do not sell your personal information. We share it with these processors and nobody else:
| Recipient | What they get | Why |
|---|---|---|
| ForkLaunch / AWS | Everything, as the platform that runs the service. | Hosting, database, logs, secrets. |
| Junction (only if you connect a device) | Your femmli user id, so they can associate the device with you. They hold their own copy of the device data. | Wearable syncing. Not enabled in production today. |
| An AI provider (only if you tick the AI box) | An aggregate finding: a rule id and computed numbers such as “4 of the 4 nights under 6 hours”. Never your logs, your notes, your dates or any identifier. | Phrasing an insight. Not enabled today. |
| AWS SES | Your email address, for a password-reset or verification link. These messages contain no health information. | Account email. |
You can tell us not to share. Setting “Do not sell or share my personal information” (CCPA §1798.120) blocks the partner paths above: connecting a device and syncing one both refuse while it is set, and the refusal is enforced at the boundary where data would actually leave, not merely recorded as a preference.
How long we keep it
In summary: health records for seven years, sessions for ninety days, verification tokens for thirty days, and access records for six years because the law requires it.
Your rights
| Right | How to use it |
|---|---|
| Get a copy of your data | Settings → Download my data. You get one file containing everything femmli holds about you, from every part of the service. Your password and any connected-device credentials are deliberately left out of it. |
| Delete your data | Settings → Delete my account. If you have connected a wearable, we delete your data at that partner first and only then locally. We tell you it is done only when every part of it is done — if any part fails, you are told it is incomplete, never that it succeeded. |
| Check on a request | Settings → Privacy requests shows every request you have made and its current state. |
| Withdraw consent | Settings → Consent. Your data stops being used for anything optional from that point, including improving the product. |
| Tell us not to sell or share | Settings → Do not sell or share my personal information. While this is set, we will not connect or sync a wearable, because that is the only path by which your data would reach another company. |
| Ask a person | Write to the privacy contact below. We answer within the time the applicable law allows. |
Security
Health data and identifiers are encrypted at rest at the field level, on top of full-volume database encryption. Traffic is HTTPS only — there is no plain-HTTP listener. Every read and change of a sensitive record is recorded in an access log that contains no health values.
Contact
Who is responsible for your data (the controller)
femmli is operated by The Precisia Collective, Inc. The service is provided through the femmli apps for iOS and Android and at app.femmli.com. Our sending domain is femmli.com.
How to reach us about privacy
The Precisia Collective, Inc.
159 W 24th St, New York, NY 10011
team@femmli.com
Where this notice applies. femmli is offered in the United States only. If you are a California resident, the CCPA rights above — including telling us not to sell or share your personal information — apply to you.
Effective date: 19 September 2026