app-guides

Published by Floriva · Updated 2026-04-28 · How Floriva checks its guides

How Floriva Handles Data Deletion

Floriva keeps core records on your device. Delete the app to remove local data, and check sync settings if you enabled optional encrypted sync.

When you delete Floriva, local app data is removed from your device. Floriva has no readable central cycle database, and optional sync data is end-to-end encrypted. This is structurally different from cloud-based period trackers, where deleting the app leaves readable data intact on company servers.

The structural difference between on-device and cloud storage

Most period tracking apps work the same way: you log data on your phone, it uploads to the company's servers, and a copy lives there. When you delete the app, you remove it from your phone. The server copy stays. The company can still access it. It can appear in a data breach, be produced in response to a subpoena, and be retained for years.

This is not a policy failure or a company being careless. It is the default behavior of cloud-connected apps.

Floriva is architected differently. Core cycle data, symptom logs, and tracked information stay in your device's local storage. Optional sync is end-to-end encrypted. When you delete the app, local app data is gone.

This distinction is what makes "data deletion" a trivially simple action in Floriva and a multi-step legal process in cloud-based apps.

What deletion looks like in practice

Floriva: delete the app

On iOS: long-press the app icon, tap Remove App, then Delete App. The app is removed along with its local data container. Done.

On Android: Settings, Apps, Floriva, Uninstall. Same outcome.

No follow-up action is needed for core local records. They were on your device. You deleted them. Optional sync, billing, support, backups, and exports may need separate cleanup.

Flo (for comparison)

In 2025, Flo settled a class action for $59.5M over claims it shared period tracking data with Facebook, Google, and Flurry. That followed a 2021 FTC enforcement action documenting the same behavior. The underlying architecture that made that sharing possible is the same architecture that makes deletion complicated: Flo stores data on servers.

Deleting the Flo app does nothing to that server data. To actually remove your data from Flo:

1. Export your data (Settings, Privacy, Request My Data)

2. Delete your account in-app (Settings, Account, Delete Account)

3. File a CCPA/GDPR deletion request at [email protected]

4. Wait up to 45 days for CCPA compliance or 30 days for GDPR

5. Accept that Flo's privacy policy allows backups to retain data for up to 90 days after account deletion

6. Accept that data already shared with third parties before the FTC action cannot be recalled

Floriva's deletion is: uninstall.

Before you delete: export if you want your history

The one step that is relevant before deleting Floriva is exporting your data if you want to keep a record of your cycle history. Use Floriva's export function to save your data to a file you control, your device's files, an encrypted folder, or wherever you keep important documents.

If you are switching to a different app, your cycle start dates from the export can seed the new tracker's prediction algorithm. Enter the last 3-6 cycle start dates and the new app will have enough history to generate reasonable predictions after 2-3 recorded cycles.

If you are deleting because you no longer want a period tracking record of any kind, skip the export and simply uninstall.

Why this matters beyond convenience

The simplicity of Floriva's deletion is not just a UX benefit. It reflects an architectural choice with real privacy consequences.

Period tracker data is not covered by HIPAA. That means cloud-stored cycle data has far fewer legal protections than most users assume. A company holding that data on a server can receive legal requests for it, can experience breaches that expose it, and can change data retention policies over time.

Local-first storage reduces that exposure. Floriva has no readable central cycle database. Local deletion is complete because the local record is removed from your device.

Deletion as a feature, not an afterthought

Most privacy features in commercial apps are promises: a company collects data and commits to handling it carefully. That promise can be broken, updated, or overridden under legal compulsion.

Floriva's deletion works differently because the privacy property is architectural. There is no promise required not to share readable cycle data with advertisers, because Floriva has no readable central cycle database. When you delete the app, local app data is removed from your device.

This is the distinction that matters for people who have read about Flo's enforcement history, or who live in states where reproductive health data could carry legal risk, or who simply want to know that deleting an app actually means their data is gone. With Floriva, it does.

For a deeper look at how period tracker apps handle data, see our guide to how period tracker apps collect data and our on-device storage explainer.