comparisons

Published by Floriva · Updated 2026-03-31 · How Floriva checks its guides

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 keeps core cycle records local-first. Here is what that means.

Flo stores your cycle data on its servers and shared reproductive health data with Facebook and Google before the FTC intervened. Floriva keeps core cycle records local-first. The practical difference: Flo can be compelled to produce server-held readable data. Floriva has no readable central cycle database to produce.

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 what SDKs do.

This structural reality applies to any app that collects data on a server and embeds third-party analytics code. The company's privacy policy governs what it intentionally does with data. The embedded SDKs operate on their own terms.

How Floriva's Architecture Is Different

Floriva does not send your data to a server. There are no Floriva servers holding your cycle information. There are no embedded analytics SDKs transmitting your behavior data to third parties.

This is not a policy decision; it is an architectural one. We built Floriva around the premise that the most private health app is one that never has your health data. We cannot share what we do not have.

The practical consequence is that a Flo-style enforcement action is technically impossible with Floriva's architecture. There are no Floriva servers to audit, no SDK data sharing to discover, and no data in Floriva's possession to be involved in a class action.

The Feature Trade-Off

Flo's feature set is more extensive than Floriva's. The AI health chat, community forums, detailed health reports, and partner tracking that Flo offers are all enabled by the cloud infrastructure that also created the data exposure. These features require aggregating data from millions of users to provide meaningful insights.

Floriva covers cycle prediction, symptom logging, reminders, and the core tracking functions that most users use regularly. Users who relied heavily on Flo's community or AI features will notice the difference. Users who primarily track their cycle and log symptoms will find the core functionality comparable.