End-to-end encryption and local-first storage both keep the content of your cycle data away from the app maker, in different ways. With end-to-end encryption, data is encrypted on your phone before it reaches the company's servers, so only you hold the key.
With local-first storage, there is no server copy at all. Neither is perfectly safe: the account, metadata, ads and your own phone matter as much as the encryption.
Three ways apps store cycle data
| Model | Where data lives | Who can read the content | Account needed | Main risks |
|---|---|---|---|---|
| Standard cloud | Company servers | The company and anyone it shares with | Usually | Breaches, sharing, requests to the company |
| End-to-end encrypted cloud | Company servers, encrypted | Only you, with your key | Yes | Metadata, lost keys, implementation flaws |
| Local-first | Your device | You | No | Lost or unlocked phone, copies you export |
Why cycle data needs extra care
Period dates, symptoms and sexual activity can reveal a pregnancy, a pregnancy loss or a health condition. Under the GDPR, health data is a special category with stricter rules, and services should protect data by design and by default. A company that holds your data can be breached, can change its policy or can receive a legal request. A company cannot hand over data it does not hold.
Myths and facts
- Myth: encrypted means private. Fact: most apps encrypt data in transit and on their servers, but the company can still read it. Only end-to-end encryption keeps the key with you.
- Myth: end-to-end encryption hides everything. Fact: the account, email address, timestamps and device details can still be visible to the company.
- Myth: local means no risk. Fact: anyone who can unlock your phone can open your apps, so the device lock matters.
- Myth: deleting the app deletes everything. Fact: exported files, backups and data you shared with other apps stay where you put them.
Seven questions to ask any tracker
- Does it need an account or an email address?
- What does the App Store privacy label say?
- Where is your data stored: on the device, on a server, or both?
- Does it show ads or include third-party analytics?
- Can you export your records in a standard format?
- Can you delete everything yourself, including copies?
- Can you lock the app with Face ID, Touch ID or a code?
Our article on ad-free period trackers explains how to read the privacy label.
A practical private setup on iPhone
- Use a strong device passcode: iOS encryption depends on it.
- Turn on the app lock if your phone is sometimes shared.
- Keep iOS updated.
- Store backups somewhere you control.
- Think before turning on health integrations: once data is in another app, that app's settings apply.
How Bloom Private does it
Bloom Private is local-first. There is no account and there are no servers: your records are stored on your iPhone and protected by iOS encryption, and you can add a Face ID or Touch ID lock for free.
The App Store label is "Data Not Collected". Backups are files encrypted with AES-256 that you keep where you choose. Apple Health is off by default; if you turn it on, the data written to Health follows your Health settings.
The trade-off is that nothing is copied anywhere automatically, so make a backup if you do not want to lose your history with your phone. Read how Bloom Private handles your data for each step.
Frequently Asked Questions
Both keep the content of your data away from the app maker. Local-first also avoids an account and a server copy, while end-to-end encryption still involves both. The device lock, ads and metadata matter in either case.
A company can only hand over data it holds. If records are stored only on your device, there is no server copy to request from the company.
It can be, unless you made a backup. With Bloom Private, create an encrypted backup and keep it somewhere you control.