Why Privacy Matters in Period Apps (After the Flo Lawsuit)

If you'd told someone a decade ago that a period tracker could become a public policy issue, they'd have laughed. Today it's normal. Cycle data has appeared in regulatory settlements, legal debates, insurance conversations and news headlines. This isn't paranoia — it's the world we now live in. And that world calls for a different kind of period app than the ones that dominated the last decade.

This article does three things: it walks through what the Flo lawsuit actually was (with the receipts), explains why cycle data is so sensitive, and lays out what "privacy-first" genuinely means in a period app — including the specific architectural choice that changes everything: on-device AI processing.

Full disclosure: we're the team behind Vyve, which is built privacy-first — so we have skin in the game. We're going to be honest and confident about that, without pretending our competitors are villains. The goal is to help you make an informed choice, and to understand why the choice matters.

What the Flo Health lawsuit actually was

Some context, plainly stated:

In January 2021, the US Federal Trade Commission announced a settlement with Flo Health over allegations that the company had shared sensitive health information from its users — including data indicating that a user was pregnant or trying to conceive — with third parties including Facebook and Google, despite the app's privacy policy stating that health information would not be shared. The FTC's complaint alleged that Flo integrated software development kits (SDKs) from these companies that received user event data.

Under the settlement, Flo was required to notify affected users, obtain consent for future data sharing, and improve its privacy practices. This is public record — you can read the FTC's press release yourself.

In 2024, Flo Health also agreed to a separate California settlement of approximately $2 million in a related privacy case. Again — public record.

Two things to hold at once: first, Flo is not uniquely evil; the FTC's action highlighted an industry-wide pattern of femtech apps sharing sensitive data in ways users didn't expect. Second, this is precisely why the pattern matters — because it's not a one-app problem. The whole business model of a lot of the femtech industry has historically depended on data collection.

The Flo case wasn't an outlier — it was the loudest public confirmation of what security researchers had been documenting for years about the femtech data economy.

Why cycle data is exceptionally sensitive

It's tempting to treat period tracking as "just calendar data." It isn't. What cycle data can reveal:

• Pregnancy. A skipped period, changes in symptoms, positive test entries all indicate pregnancy — often before the person has told anyone.
• Attempts to conceive. Logging ovulation, intercourse frequency, fertility signs is a very clear signal.
• Miscarriage or pregnancy loss. A pregnancy entry followed by a return to periods is a devastatingly identifiable pattern.
• Life stages. Perimenopause, menopause, postpartum are all readable from cycle data.
• Health conditions. Irregular cycles suggest PCOS or thyroid issues. Severe cyclical pain suggests endometriosis. Cyclical mood symptoms suggest PMDD.
• Sexual activity. Some apps log intercourse and protection use.
• Mental health. Many trackers include mood, anxiety, stress data.

In some jurisdictions, some of these data points have direct legal implications. Elsewhere, they can affect insurance, employment discussions, or reveal things a person hasn't chosen to share with anyone. This is not the same as knowing your favorite pizza topping.

The old femtech business model

To understand why privacy in period apps has been a problem, understand the money. The dominant model for consumer femtech has been:

1. Offer a free app to attract a huge user base.
2. Collect detailed personal health data as part of tracking.
3. Monetize through some combination of paid premium tiers, advertising, partnerships with pharmaceutical and consumer health companies, aggregate data licensing, and research partnerships.

Steps 1 and 2 are fine on their own. Step 3 is where privacy risk enters — because the more valuable your data is to the business, the harder it becomes to not use it. Even with good intentions, an ad SDK from a major platform included in the app can transmit event data that users don't expect. That was the technical mechanism at the heart of the Flo case.

The market has since improved somewhat — companies have tightened policies, some have added more granular consent, and regulatory scrutiny has increased. But the fundamental architecture, in most apps, is still cloud-based: your data is uploaded to a server for processing, storage and analysis. Wherever it lives, someone else has access to it.

On-device vs cloud: what actually changes

This is the technical heart of the article, and it matters.

Cloud-based apps send your data to a company server for processing, analysis and storage. The app on your phone is essentially a client that talks to remote systems. Your data lives on their infrastructure — subject to their access policies, employees, third-party integrations, security posture, subpoenas, and any changes to their business model or ownership.

On-device apps keep your data on your phone. The AI and analysis run locally, using your device's own processing power. The company you download from doesn't have your data — not "promises not to use it," but literally doesn't have it. There's nothing to sell, nothing to leak in a breach, nothing to hand over.

The distinction isn't a marketing gradient — it's an architectural fork. Once you understand it, "privacy-first" stops being vague copy and becomes a specific technical claim you can verify.

What "privacy-first" really means

The term is thrown around loosely. Our checklist for what it actually means, in a period app:

1. On-device processing. AI and analysis run on your phone, not in a cloud server.
2. No required account. No email, no phone number, no login required to use the app fully.
3. Local encryption. Data stored on your device is encrypted, so a lost or stolen phone doesn't expose it.
4. No third-party trackers or ad SDKs. This is what the Flo case was about — integrated SDKs sending event data. A truly private app doesn't include these.
5. No data sharing with third parties. Period.
6. User-controlled backup. If you want to sync across devices or back up, it should be your choice, encrypted, and something you can opt out of entirely.
7. Transparent documentation. Clear plain-English privacy policy, ideally with technical detail on architecture.
8. No dark patterns. No manipulative "share anonymously to help research" defaults, no burying opt-outs deep in menus.

If an app can't check all of these boxes, "privacy-first" is at best marketing shorthand and at worst misleading.

How Vyve is built

We built Vyve with a specific bet: that people who care about cycle privacy deserve an actually private option, and that AI-powered tracking can be excellent without shipping your body to a server.

Concretely, Vyve is:

• On-device AI. Prediction, pattern recognition, insights — all run on your phone. Your cycle data never needs to leave the device to be analyzed.
• Local-first storage. Your data lives on your device, encrypted. No cloud requirement.
• No required account. You don't need to give us an email to use it fully.
• No data brokers, no ad SDKs. We don't share your data with third parties because there's nothing to share.
• Multiple AI personas from your device. Vyve's built-in "personas" — a 30-year gynecologist, an endocrinologist, an OB, a geriatrician — run locally, so you can get expert-style perspectives on your cycle data without any of that data leaving your phone.
• Doctor-ready export you control. When you want to share with your clinician, you export a clean summary yourself — no automatic uploads.

We're not perfect and we don't pretend to be. But the architecture is fundamentally different from cloud-based competitors, and that difference is the whole point.

How to check if any app is actually private

Not just Vyve — any period app. Practical questions to ask before trusting one with your data:

• Does it require an account? If yes, your data is at least tied to an identifier.
• Does it work offline? If not, it's cloud-dependent.
• What does the privacy policy actually say about third parties? Read it. Ctrl-F "advertising," "analytics," "third parties," "share." Not the marketing page — the policy.
• Are there ad SDKs? App-store listings and privacy labels increasingly disclose this.
• What happens if you delete your account? Is your data actually deleted, or "retained for analytics"?
• Where is data stored? Country matters for legal exposure.
• Has the company had privacy incidents? Google the app name plus "FTC," "lawsuit," "privacy."

For a specific comparison of the major players, see our guide on Vyve vs Flo vs Clue.

Honest tradeoffs of on-device

To be fair — on-device processing does have real tradeoffs, and we should name them:

• No effortless cloud sync across devices by default. If you want data on multiple devices, you'll opt into encrypted backup rather than getting it automatically.
• Some population-level insights are harder. Cloud-based apps can compare you to their whole user base; on-device apps can't (which is a feature, not a bug, from a privacy standpoint).
• Requires a capable device. On-device AI needs modern-ish phone hardware.
• Losing your phone matters more. If it's not backed up, data is gone — which is why encrypted user-controlled backup matters.

These are real tradeoffs. In exchange, your body's data actually stays your body's data. For most people, that trade is worth making — especially now that we know how the alternative has played out.

Frequently asked questions

What was the Flo Health lawsuit about?

In 2021, the US FTC settled with Flo Health over allegations that the company shared sensitive user health data — including pregnancy indicators — with third parties like Facebook and Google, despite claims in its privacy policy that it wouldn't. In 2024, Flo agreed to a separate $2 million California settlement in a related privacy case. Both are public record.

Is my cycle data actually sensitive?

Yes — extremely. It can reveal pregnancy, fertility intentions, life stages, health conditions and, in some jurisdictions, has legal or insurance implications. It's some of the most personal data you generate.

What does "on-device processing" mean?

The app's AI and analysis run directly on your phone rather than a cloud server. Your data doesn't leave your device to be analyzed. Fundamentally different from cloud-based apps — with on-device, there's no data on someone else's server to leak, sell or subpoena.

Why is Vyve different from apps like Flo?

Vyve was built privacy-first from day one — AI processing on-device, data on your phone, no required account, no third-party sharing. It's an architectural difference, not a policy claim.

How do I check if a period app is actually private?

Look for on-device processing, no required account, encrypted local storage, no ad SDKs, no third-party sharing, transparent privacy documentation. Read the privacy policy, not the marketing page.

Are all popular period apps risky?

Not all — some have improved significantly. But the default architecture of most cloud-based femtech apps still means your data lives on servers you don't control. On-device architecture solves that at the root.

Educational content, not medical or legal advice. Facts about the Flo Health FTC settlement and the 2024 California settlement are drawn from public records; check current official sources for the latest.