· Agency action
In the Matter of Flo Health, Inc.
Federal Trade Commission, FTC File No. 192 3133
Primary source: FTC announcement. Checked on November 10, 2026.
The FTC finalized an order requiring Flo Health to obtain users' affirmative express consent before sharing their health information, over charges its period-tracking app sent menstruation and pregnancy data to Facebook, Google and others.
What happened
Flo Health, Inc. makes the Flo Period & Ovulation Tracker app. The complaint alleged that more than 100 million people had downloaded it since 2016, including more than 16 million in the United States, and that users entered details such as menstrual cycle dates, pregnancies, symptoms, weight and temperature. (Compl. paras. 2, 9, 12.)
The complaint alleged that from June 2016 to February 2019, through software development kits from Facebook, Flurry, Fabric, AppsFlyer and Google, the app conveyed custom app events with descriptive titles such as R_PREGNANCY_WEEK_CHOSEN, along with advertising or device identifiers. It alleged that privacy policies in effect from 2017 to 2019 said cycle, pregnancy and symptom information would not be shared. (Compl. paras. 14, 16, 19-20.)
It alleged that Flo accepted the providers' standard terms, which let some of them use the data for their own purposes, that Facebook used the event data for its own research and development without knowing it included health information, and that Flo stopped after a February 2019 Wall Street Journal report. Four more counts alleged misrepresentations about compliance with the EU-U.S. and Swiss-U.S. Privacy Shield frameworks. (Compl. paras. 5, 22-24, 57-64.)
The Commission accepted the settlement for public comment by a 5-0 vote in January 2021 and finalized it by a 4-0-1 vote after five comments, with Chair Lina Khan not participating. The order required no payment. Commissioner Phillips wrote separately that the complaint did not challenge the use of third-party analytics services as such. (FTC releases, January 13 and June 22, 2021; Phillips statement at 1 n.1.)
What the agency did
Before disclosing any consumer's health information to a third party, Flo must clearly and conspicuously disclose, apart from any privacy policy or terms of use, the categories of information, the recipients and all purposes, and obtain the consumer's affirmative express consent. (Decision and Order at 4 (Provision IV))
separate and apart from any “privacy policy,” “terms of use” page, or other similar document
Decision and Order at 4 (Provision IV.A) The order defines Health Information to include reproductive health details. (Decision and Order at 3 (Definition E))
“Health Information” means individually identifiable information from or about an individual consumer relating to health, including but not limited to information concerning fertility, menstruation, sexual activity, pregnancy, and childbirth.
Decision and Order at 3 (Definition E) Flo had to instruct any third party that received health information of anyone who downloaded and used the app between June 30, 2016 and February 23, 2019 to destroy it. (Decision and Order at 3-4 (Definition B; Provision II))
Flo had to post and email users a prescribed notice. The notice says the app sent an identifying number and period and pregnancy information to the analytics divisions of Facebook, Flurry, Fabric and Google, and that names, addresses and birthdays were not shared. (Decision and Order at 4, 11 (Provision III; Exhibit A))
No information was shared with the social media divisions of these companies.
Decision and Order at 11 (Exhibit A) The order bars misrepresentations about the purposes of data collection and disclosure, consumers' control over their data, participation in privacy programs such as Privacy Shield, and how Flo handles and protects information, and it required an independent compliance review. (Decision and Order at 3-5 (Provisions I, V))
Commissioner Phillips, supporting the complaint and order, wrote that the case turned on descriptive event names, not on the use of third-party analytics. (Phillips statement at 1 n.1 (January 13, 2021))
The Complaint does not challenge the use of third-party analytics services, upon which developers routinely rely.
Phillips statement at 1 n.1 Commissioners Chopra and Slaughter, concurring in part and dissenting in part when the settlement was proposed, wrote that the FTC should also have charged a violation of the Health Breach Notification Rule, which it had never enforced. (Chopra and Slaughter statement at 2 (January 13, 2021))
In our view, the FTC should have charged Flo with violating the Health Breach Notification Rule.
Chopra and Slaughter statement at 2 Responding to public comments, the Commission said it was reviewing the Health Breach Notification Rule, including how it applies to mobile apps. (Letters to commenters at 1 (June 17, 2021))
The Commission is currently reviewing the Rule and is actively considering public comments regarding the application of the Rule to mobile applications and other direct-to-consumer technologies that handle consumers’ sensitive health information.
Letters to commenters at 1
What it did not decide
- Whether Flo in fact violated the FTC Act; it neither admitted nor denied the allegations, and the order's findings cover only the company's identity, jurisdiction and the public interest. (Decision and Order at 1-2.)
- Whether Flo violated the Health Breach Notification Rule; the complaint did not charge it, and Commissioner Phillips disagreed that the rule plainly covered Flo. (Phillips statement at 1 n.3.)
- Any claim against Facebook, Google or the other recipients; the FTC action named only Flo.
- The federal Wiretap Act and state wiretap or privacy statutes; the complaint charged only violations of Section 5 of the FTC Act.
- Consumer redress; the order required no payment, as the Commission noted in responding to a commenter. (Letters to commenters at 4.)
The tracking involved
Tools
- Facebook SDK (Facebook Analytics)
- Flurry SDK
- Fabric SDK
- AppsFlyer SDK
- Google SDK (Google Analytics)
Data
- Custom app events with titles about menstruation, fertility and pregnancy
- Unique advertising or device identifiers
How it bears on website tracking claims
Supports: strengthens a website tracking claim on this issue. Limits: narrows or defeats a website tracking claim on this issue. Context: bears on the issue without deciding it either way.
Context: Consumer protection
Deception and unfair practice claims, such as under the FTC Act and N.Y. General Business Law § 349.
The FTC charged that Flo's privacy promises were deceptive because the app conveyed health information to analytics and marketing firms (Compl. paras. 51-56). The order imposes a consent requirement, deletion instructions and user notice, but no money (Decision and Order at 3-5). It shows the FTC acting under the FTC Act against app data flows that contradicted privacy promises, without findings, and it does not decide any state consumer-protection statute.
Context: Health information
What counts as individually identifiable health information when it is sent through tracking tools.
The complaint alleged that event titles such as R_PREGNANCY_WEEK_CHOSEN conveyed menstruation, fertility and pregnancy information when sent with device identifiers (Compl. paras. 19-20). Commissioner Phillips wrote that the events conveyed health information because of their descriptive names rather than generic ones (Phillips statement at 1 n.1). These are statements in an app settlement without findings, not a ruling on what counts as health information under HIPAA or a wiretap statute.
Context: Consent
Whether visitors agreed to the tracking through banners, privacy policies or terms.
The order requires notice separate from the privacy policy and affirmative express consent before Flo discloses health information to any third party (Decision and Order at 4). The complaint alleged that a welcome screen telling European users that using the app meant consenting to the privacy policy did not give adequate notice or choice under Privacy Shield (Compl. paras. 36-43). Responding to a comment, the Commission said the consent screen the commenter showed did let users decline third-party disclosures, but shared the concern that it was confusing (Letters to commenters at 1-2). None of this decides consent under the Wiretap Act or state law.
Context: Health Breach Notification Rule
The FTC rule that can treat an unauthorized disclosure of health app data as a breach that requires notice.
The FTC did not charge a rule violation. Commissioners Chopra and Slaughter wrote that it should have, noting the FTC had never enforced the rule, while Commissioner Phillips said the rule's language was not plain and opposed announcing a novel interpretation in an enforcement action (Chopra and Slaughter statement at 2; Phillips statement at 1 n.3). The Commission said it was reviewing how the rule applies to apps (Letters to commenters at 1). The FTC later brought rule cases against GoodRx and Premom's developer in 2023 and amended the rule in 2024.
Arguments it addresses
- The app only uses standard analytics tools
- Commissioner Phillips wrote that the complaint did not challenge the use of third-party analytics as such; the charges rested on descriptive event names and contrary privacy promises (Phillips statement at 1 n.1; Compl. paras. 13-20).
- Event names are not health information
- The complaint alleged that titles such as R_PREGNANCY_WEEK_CHOSEN conveyed users' menstruation, fertility and pregnancy information to the recipients (Compl. para. 19).
- The data went to analytics services, not advertisers
- The order's required notice says the data went to the analytics divisions of Facebook, Flurry, Fabric and Google, and the FTC still charged deception because the privacy policies promised health data would not be shared and some recipients' terms let them use the data for their own purposes (Decision and Order at 11, Exhibit A; Compl. paras. 20-22).
- The vendor's terms banned health data, so the vendor was responsible
- The complaint alleged that Flo's disclosures violated Facebook's and AppsFlyer's own terms, and the FTC charged Flo, not the vendors (Compl. para. 21).
- A consent order is not a finding of liability
- That is correct here: Flo neither admitted nor denied the allegations, and the order's findings cover only the company's identity, jurisdiction and the public interest (Decision and Order at 1-2).
For a company that received a letter
- The Flo order is an FTC settlement over a mobile app's SDK data, without findings or money, so it shows the agency's position rather than a ruling on a website-tracking claim.
- Commissioner Phillips's statement marks the line he saw in the complaint: using analytics tools was not challenged, but sending descriptive health event names contrary to privacy promises was.
- The Commission's response to a comment shows that it looked at whether a consent screen let users decline third-party disclosures and whether it was confusing.
What to check on your own site
- Check the names and parameters of custom events your site or app sends to analytics and advertising vendors for words that describe a health condition, treatment, pregnancy or similar fact.
- Compare what each embedded SDK or tag sends with what the privacy policy says is shared and with whom.
- Check each vendor's terms for limits on sending health information and for the vendor's own use of the data it receives.
Later history
The FTC's case page, last updated June 22, 2021, lists the matter as closed and shows no later order or modification.
Sources
- FTC announcement of final order (June 22, 2021)
- FTC announcement of proposed settlement (January 13, 2021)
- Complaint (issued June 17, 2021)
- Decision and order (issued June 17, 2021)
- Letters to commenters (June 17, 2021)
- Joint statement of Commissioners Chopra and Slaughter (January 13, 2021)
- Separate statement of Commissioner Phillips (January 13, 2021)
- FTC case page
Related rulings
Published by Privacy Resolve from public records. It does not cover our own matters.
General information only, not legal advice, and not a substitute for the advice of an attorney. Laws, deadlines, defenses and outcomes vary by jurisdiction and facts.