· Agency action
United States v. Easy Healthcare Corporation
Federal Trade Commission, through the Department of Justice; U.S. District Court for the Northern District of Illinois, No. 1:23-cv-03107
Primary source: Stipulated order. Checked on November 10, 2026.
In the FTC's second Health Breach Notification Rule case, Premom's developer agreed to a $100,000 civil penalty and an advertising ban over charges its app sent users' fertility and pregnancy information to Google and AppsFlyer.
What happened
Easy Healthcare Corporation develops the Premom Ovulation Tracker, an app in which users log periods, fertility and pregnancy information, upload pictures of ovulation tests and import data such as body temperature from other apps and devices. The Department of Justice filed the complaint for the FTC on May 17, 2023, after a 3-0 Commission vote to refer it. (Compl. paras. 2, 12-17; FTC release, May 17, 2023.)
The complaint alleged that between 2017 and 2020 the company's privacy policies promised it would not share health information without users' knowledge or consent and that any data it shared was non-identifiable. It alleged that software development kits (SDKs) from Google and AppsFlyer in the app received custom app events with descriptive titles, such as Calendar/Report/LogFertility, Log period-save and Guarantee/signup, sent in plain text along with advertising or device identifiers. (Compl. paras. 3, 18-21, 25-29, 60.)
The complaint also alleged that SDKs from Jiguang and Umeng, which it described as Chinese analytics providers, collected social media account information, device identifiers including non-resettable ones, Wi-Fi network details and precise location; that one of them used a non-standard encryption method and sent the decryption key with the data; and that the company accepted these providers' standard terms, which let them use the data for their own purposes. (Compl. paras. 5, 33-35, 41, 48.)
The company neither admitted nor denied the allegations. The notice the order requires it to give users states that it did not share users' names, birth dates or addresses with these companies. The FTC also announced that, in a related action under the laws of Connecticut, the District of Columbia and Oregon, the company agreed to pay those jurisdictions a total of $100,000. (ECF No. 5 at 2, 35-36; FTC release, May 17, 2023.)
What the agency did
The order enters a $100,000 civil penalty judgment against the company. (ECF No. 5 at 27 (Section XII))
Judgment in the amount of one hundred thousand Dollars ($100,000) is entered in favor of Plaintiff against Defendant, jointly and severally, as a civil penalty.
ECF No. 5 at 27 (Section XII.A) The order permanently bans the company from disclosing health information to third parties for advertising. (ECF No. 5 at 8 (Section I.A))
permanently restrained and enjoined from disclosing Health Information to Third Parties for Advertising Purposes
ECF No. 5 at 8 (Section I.A) The ban's exclusion for advertising reporting and analytics applies only if the analytics provider is restricted to using the data to provide those services to the company. (ECF No. 5 at 8 (Section I.B))
provided that any Third Party reporting or analytics service is restricted from using any Covered Information received from or provided to Defendant for any purpose other than to provide the reporting and analytics services to Defendant
ECF No. 5 at 8 (Section I.B) For any purpose other than advertising, the company must obtain affirmative express consent before disclosing health information to third parties, after a clear and conspicuous notice stating the categories of information, the recipients, the purposes, what each recipient may do with the information and whether laws such as HIPAA protect it. (ECF No. 5 at 10-11 (Section III))
The order defines Health Information to include fertility, menstruation, sexual activity, pregnancy and childbirth information, and information about health derived or inferred from non-health data. (ECF No. 5 at 5 (Definition M))
It also includes any individually identifiable information relating to health that is derived or extrapolated from non-health information (e.g., proxy, derivative, inferred, emergent, or algorithmic data).
ECF No. 5 at 5 (Definition M) Within 45 days the company had to instruct Jiguang and Umeng to delete covered information, and AppsFlyer and Google to delete health information collected through their SDKs, and demand written confirmation. (ECF No. 5 at 15-16 (Section VI))
The order requires a privacy and information security program, including audits, reviews or testing of the SDKs the company uses and their associated third parties, with independent assessments. (ECF No. 5 at 17-22 (Sections VII, VIII))
audits, assessments, reviews, or testing of Software Development Kits, and their associated Third Parties
ECF No. 5 at 20 (Section VII.E.8) In its statement of reasons for the settlement, the Commission said the penalty and injunctive relief were an appropriate settlement that would promote compliance and deter others. (Statement of Reasons, ECF No. 3-2, at 1)
are effective means to ensure Defendant’s future compliance and to deter others who might violate these laws
Statement of Reasons, ECF No. 3-2, at 1
What it did not decide
- Whether the company in fact violated the FTC Act or the Health Breach Notification Rule; it neither admitted nor denied the allegations, and the order makes no findings on the merits. (ECF No. 5 at 1-2.)
- The federal Wiretap Act and state wiretap or privacy statutes; the complaint charged only the FTC Act and the Health Breach Notification Rule, and the order decides no claim under any other law.
- Website tracking; the case concerned a mobile app and the SDKs built into it.
- Which Connecticut, District of Columbia and Oregon laws the related state settlement involved; the FTC's release does not say.
The tracking involved
Tools
- Google Analytics for Firebase SDK
- AppsFlyer SDK
- Umeng U-Share SDK
- Jiguang JPush SDK
Data
- Custom app event titles about fertility, periods, pregnancy and sign-ups
- Advertising and device identifiers, including non-resettable hardware IDs and IMEI numbers
- Social media account information
- Wi-Fi and router identifiers and network names
- Precise geolocation
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: Health Breach Notification Rule
The FTC rule that can treat an unauthorized disclosure of health app data as a breach that requires notice.
The complaint alleged that Premom was a personal health record because it drew health information from user entries and from other apps and devices, and that sending custom app event titles in plain text to Google and AppsFlyer without authorization was a breach of security requiring notice to users, the FTC and the media (Compl. paras. 59-61, 89-91). The FTC called it its second action under the rule, after GoodRx (FTC release, May 17, 2023). The rule applies to vendors of personal health records other than HIPAA covered entities and their business associates (Compl. para. 57), so it can reach health apps and similar services outside HIPAA.
Context: Agency penalties and orders
Civil penalties, payments and conduct terms that regulators obtained.
The order enters a $100,000 civil penalty judgment, and the FTC announced a separate payment totaling $100,000 to Connecticut, the District of Columbia and Oregon (ECF No. 5 at 27; FTC release, May 17, 2023). The complaint cited authority for civil penalties of up to $46,517 for each knowing violation of the rule (Compl. para. 62). The amount was agreed in a stipulated order, so it does not show how a court would set a penalty.
Context: Consumer protection
Deception and unfair practice claims, such as under the FTC Act and N.Y. General Business Law § 349.
The complaint charged deception and unfairness under Section 5 of the FTC Act, including a count for sharing health information for advertising without affirmative express consent, and the order bans disclosing health information for advertising (Compl. paras. 67-88; ECF No. 5 at 8). It shows the FTC acting against an app's SDK data flows that contradicted its privacy policy, without findings. 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 Calendar/Report/LogFertility conveyed fertility and pregnancy information when sent with device identifiers that third parties could link to a person (Compl. paras. 28-29, 36-38). The order's definition of Health Information includes information inferred from non-health data (ECF No. 5 at 5). These are allegations and a negotiated definition for one company, not a court ruling on what counts as health information under HIPAA or a wiretap statute, and they concern an app rather than a website.
Context: Consent
Whether visitors agreed to the tracking through banners, privacy policies or terms.
The order requires affirmative express consent, after a disclosure given apart from any privacy policy or terms of use, before health information is disclosed for purposes other than advertising, and it says that accepting general terms of use and agreement obtained through interfaces designed to subvert user choice do not count (ECF No. 5 at 2-3, 10-11). This is a remedy binding the company under the FTC Act, not a ruling on consent under the Wiretap Act or state law.
Context: Standing and injury
Whether the people suing were harmed in a way that lets a federal court hear the claim.
The complaint alleged that sharing users' custom app events and identifiers revealed details about their sexual and reproductive health and pregnancy status, was likely to cause stigma, embarrassment or emotional distress, and exposed identifiers to interception because of inadequate encryption (Compl. para. 49). These are the FTC's unfairness allegations; the case did not involve Article III standing or any individual user's claim.
Arguments it addresses
- Analytics tools receive app events, not health data
- The complaint alleged that custom event titles such as Calendar/Report/LogFertility and Log period-save themselves conveyed users' fertility and pregnancy information to Google and AppsFlyer (Compl. paras. 26-28).
- The app shares only non-identifiable data or IP addresses
- The complaint alleged that, despite policy statements about non-identifiable data and identification solely by IP address, the SDKs sent device identifiers, including non-resettable ones, and precise location that third parties could link to individuals (Compl. paras. 21, 32-39, 43).
- Analytics is not advertising
- The order excludes analytics from the advertising ban only where the analytics provider is restricted to providing those services, and it requires affirmative express consent before health information is disclosed for any purpose other than advertising (ECF No. 5 at 8, 10).
- The data the app sends is not health data on its face
- The order's definition of Health Information includes information about health derived or extrapolated from non-health information (ECF No. 5 at 5).
- The company relied on the SDK providers' standard terms
- The complaint alleged that accepting the providers' standard terms, which let them use the data for their own purposes including advertising, contradicted the company's privacy promises (Compl. paras. 5, 41, 45).
For a company that received a letter
- This was an app case built on SDK event titles and device identifiers, so its facts differ from a website pixel case, although the FTC made a similar point about descriptive event names in its GoodRx case.
- The order is a negotiated settlement without findings; it shows the FTC's position and remedies, not a court's ruling on liability.
- The Health Breach Notification Rule applies to vendors of personal health records and related entities outside HIPAA, so its relevance depends on whether a business is one of them.
What to check on your own site
- Check whether custom event names or parameters sent to analytics or advertising vendors state a health condition, treatment, test or similar fact.
- Check which device identifiers and location data each embedded SDK or tag collects, and whether the privacy policy describes them accurately.
- Check the terms for each SDK or tag to see whether the vendor may use the data it receives for its own purposes.
Later history
The court's docket on CourtListener shows no entry after June 22, 2023, when the stipulated order was entered (ECF Nos. 4, 5), and the FTC's case page, last updated June 26, 2023, lists no later order.
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.