Period data can reveal health patterns, sexual activity, pregnancy intentions, medication use, and intimate notes. “We care about privacy” is not enough information to understand where that data goes.
The useful questions are architectural: Does the app require an account? Is information stored on the device or a server? Are analytics SDKs present? What gets backed up? Can you export and truly delete it?
The short version
- Privacy depends on data flow, not branding.
- Health apps may not have the same legal protections as information shared with a doctor.
- Minimizing collection reduces the number of promises you have to trust.
Map where the data can travel
An account usually means some information reaches a server. Cloud sync creates another copy. Analytics and advertising tools may receive events or identifiers. Notifications can appear on a locked screen. Exports can remain in Files, email, or messages long after the original entry is deleted.
None of these features is automatically unacceptable. The point is to know which ones exist and decide whether their benefit is worth the exposure.
- Is an account required?
- Is data local, cloud-based, or both?
- Are analytics, crash reporting, or ad SDKs used?
- Is cloud backup optional and clearly explained?
- Can sensitive notifications be hidden?
Test control, not only collection
Look for clear export and deletion controls. Ask whether deleting the app deletes server data, whether account deletion is separate, and whether backups persist. A privacy policy should explain retention and third-party sharing in concrete terms.
If a partner has access, clarify whether that access can be revoked and whether old screenshots or exports remain outside the system.
- Can I export a readable copy?
- Can I delete one profile, one entry, or everything?
- Does deletion include server and backup copies?
- Can I lock the app separately from the phone?
Choose the smallest useful system
A local-only app reduces network exposure and eliminates the need for a remote account, but the phone itself still needs protection. A cloud service can offer convenience across devices, but then security, access control, retention, and company practices matter more.
There is no universal answer. There is only an informed tradeoff—and a good reason to be skeptical of vague claims.
Sources & further reading
Community discussions informed the questions; health and training claims are grounded in the professional guidance and research listed here.