Can I switch from Flo to Floriva without losing my cycle history?

Yes, with manual data entry. Export your Flo data via Settings, Privacy, Request My Data. Then enter your recent cycle start dates in Floriva. The prediction algorithm stabilizes after 2-3 cycles. You will not have an automatic import because connecting to Flo's servers would create a data transfer event that contradicts Floriva's on-device design.

Does Floriva have the same features as Flo?

Floriva covers cycle prediction, symptom logging, and reminders, which are the core features most Flo users rely on. Flo has additional features including AI health chat, community forums, detailed health reports, and partner tracking. These features depend on aggregated data and cloud infrastructure that Floriva's architecture does not support.

Is Floriva private by default or do I have to pay for privacy?

Floriva is private by default. On-device storage is not a paid feature. All users, regardless of subscription tier, have the same on-device-only architecture. This differs from Flo's Anonymous Mode, which requires the paid Premium subscription.

comparisons

Flo vs Floriva: What Happens to Your Period Data

Flo stores your data on its servers and has a documented history of sharing it. Floriva stores data on your device only. Here is what that means.

What the FTC Found In January 2021, the Federal Trade Commission took enforcement action against Flo Health. The FTC found that Flo had shared sensitive user health data, including menstrual cycle dates, pregnancy status, and health symptoms, with Facebook, Google, and Flurry through embedded analytics SDKs. This data sharing occurred despite Flo's privacy policy stating it would not share health information with third parties. The FTC's enforcement action required Flo to get user consent before sharing data, notify affected users, and implement a privacy review program. Flo launched Anonymous Mode as a result. In September 2025, a combined $59.5M class action settlement resolved claims from users affected by the data sharing. The settlement covered a class of millions of Flo users. How Cloud Based Architecture Made This Possible The Flo enforcement action was not primarily about a policy decision to share data. It was about the consequences of embedding third party analytics SDKs in an app that collected sensitive health data. Analytics SDKs transmit device and behavior data to the SDK provider's servers by design. Flo's privacy policy promised not to share data, but the SDKs did