Why Premom was fined $100,000: analytics events that disclosed health data, as alleged
An analytics event with a name like 'log_period' can share health data, according to a complaint brought for the US Federal Trade Commission, which alleges that event titles such as "Log period-save" were "descriptive titles that convey health information" (¶28). The complaint says Premom, a US fertility-tracking app, sent such events to Google and AppsFlyer with advertising or device identifiers, while its privacy policy promised never to share health data without consent or knowledge. Its maker, Easy Healthcare Corporation, agreed to a $100,000 civil penalty without admitting or denying the allegations.
The decision
- Who: a settlement in US federal court (N.D. Ill., No. 1:23-cv-3107). The Department of Justice sued for the FTC. The company, Easy Healthcare Corporation, maker of the fertility and ovulation-tracking app Premom, "neither admits nor denies any of the allegations in the Complaint" (order, ¶3), so everything below about the software is an allegation.
- When: complaint filed 17 May 2023; stipulated order filed 22 June 2023.
- Amount: a $100,000 civil penalty. The company also agreed to pay a total of $100,000 to Connecticut, the District of Columbia and Oregon, which worked with the FTC on the case [4].
- Status as of November 2026: not under appeal. Both sides "waive all rights to appeal or otherwise challenge or contest the validity of this Order" (order, ¶5). The FTC's case page still shows the status "Pending".
- Text: complaint [1] and order [2], linked from the FTC's case page [3].
What the complaint says the software did
The privacy policy dated 7 July 2020 said, "in a paragraph set off from other paragraphs" (complaint ¶19, p. 6):
"WE PROMISE WE WILL NEVER SHARE YOUR EXACT AGE OR ANY DATA RELATED TO YOUR HEALTH WITH ANY THIRD PARTIES WITHOUT YOUR CONSENT OR KNOWLEDGE."
According to the complaint, the app:
- built in SDKs from Google and AppsFlyer and "disclosed health information to them through 'Custom App Events'" (¶26, p. 8), "records of user-app interactions unique to [the app]" (¶27, p. 8);
- gave those events "descriptive titles that convey health information" (¶28, p. 8), for example "when a user logs and saves information related to her period, Defendant records the Custom App Event as 'Log period-save.'" Other titles included "Calendar/Report/LogFertility" and "Signup/Birth" (¶28, pp. 8–9);
- sent identifiers with them: "Through these SDKs, Defendant has also collected and shared [the app's] users' unique advertising or device identifiers", which "could allow these third parties to associate these fertility and pregnancy Custom App Events to a specific individual" (¶29, p. 9);
- sent the titles "in plain text" (¶90, p. 28).
What this looks like in code
The complaint does not say which Google SDK the app used. The reproduction uses Firebase Analytics beside AppsFlyer's Android SDK. Read it against the promise above.
This is not Premom's code. The complaint does not publish any code; this reproduces the behaviour it describes.
import android.content.Context
import com.appsflyer.AppsFlyerLib
import com.google.firebase.analytics.FirebaseAnalytics
// AppsFlyer sends data only after init(devKey, ...) and start(...) have run in
// Application.onCreate. That setup is not shown here.
class PeriodLogger(
private val context: Context,
private val repository: CycleRepository,
) {
private val firebase = FirebaseAnalytics.getInstance(context)
private val appsFlyer = AppsFlyerLib.getInstance()
fun onPeriodSaved(entry: PeriodEntry) {
repository.save(entry) // dates and symptoms go to our own backend
// product analytics: which features get used
firebase.logEvent("log_period_save", null)
appsFlyer.logEvent(context, "Log period-save", emptyMap())
}
fun onFertilityLogged(entry: FertilityEntry) {
repository.save(entry)
firebase.logEvent("calendar_report_log_fertility", null)
appsFlyer.logEvent(context, "Calendar/Report/LogFertility", emptyMap())
}
}
Neither call passes a parameter. Google and AppsFlyer receive the event's name, with the identifiers each SDK attaches on its own, and the complaint's point is that a name like "Log period-save" says what this user just did.
The complaint says such transfers "directly contradict" the privacy policy (¶30, p. 9). That promise sits in a policy page, outside the code base, and no review of PeriodLogger puts the two side by side.
Why it was a violation, according to the complaint
The court did not rule on the merits. The complaint's reasoning:
- Deception under FTC Act §5(a), 15 U.S.C. §45(a) (Count I, ¶¶67–69, p. 22). The policies said health information would not reach third parties without knowledge or consent. "In truth and fact," the company "did disclose consumers' health information to AppsFlyer and Google."
- Unfairness under §5(a) (Count VII, ¶86, p. 26). The company "failed to encrypt or label" the events "to prevent the transfer of users' personal health information to Google and AppsFlyer", so it went out "without users' knowledge" or their "affirmative express consent".
- The Health Breach Notification Rule, 16 C.F.R. Part 318 (Count VIII, ¶¶89–93, pp. 27–28). As a "vendor of personal health records", the company experienced "breaches of security" when the event titles reached Google and AppsFlyer "without the authorization of [the app's] users", and it sent none of the notices the Rule requires (¶91). Under §318.7 a violation of the Rule counts as a violation of §5(a) (¶92). The FTC's press release ties the $100,000 civil penalty to this Rule [4].
The fix
Send third-party SDKs only events whose names and parameters say nothing about the user's health. Then write the privacy policy so that it names every event your code sends them, and the events their SDKs log without being asked. One gateway with a fixed list, and a test that fails unless the policy names exactly the events on that list, keeps code and policy in step:
// Analytics.kt: the only place that calls third-party SDKs.
object Analytics {
val THIRD_PARTY_EVENTS = setOf("trial_started", "subscription_purchased")
fun track(context: Context, event: String) {
// BuildConfig needs buildFeatures { buildConfig = true } (AGP 8+)
if (event !in THIRD_PARTY_EVENTS) {
check(!BuildConfig.DEBUG) { "'$event' is not cleared for third-party SDKs" }
return // dropped in release builds, never sent
}
FirebaseAnalytics.getInstance(context).logEvent(event, null)
AppsFlyerLib.getInstance().logEvent(context, event, emptyMap())
}
}
// PeriodLogger.kt
fun onPeriodSaved(entry: PeriodEntry) {
repository.save(entry)
// No third-party event for anything the user logs about their body.
}
// PrivacyPolicyTest.kt: the policy names exactly the events the app sends.
class PrivacyPolicyTest {
@Test fun policyNamesExactlyTheEventsTheAppSends() {
val line = File("../PRIVACY.md").readLines().single { it.startsWith("Events our app sends them:") }
val named = Regex("`(\\w+)`").findAll(line).map { it.groupValues[1] }.toSet()
assertEquals(Analytics.THIRD_PARTY_EVENTS, named)
}
}
The policy file that test reads (our example, not the company's text; the automatic events are from Google's list [9], Firebase's screen-view page [5] and AppsFlyer's guide [10]):
## What our analytics providers receive
Google (Firebase Analytics) and AppsFlyer receive events from this app.
Events our app sends them: `trial_started` and `subscription_purchased`.
Their SDKs also log events on their own. Firebase logs, among others, `first_open`,
`session_start`, `user_engagement` and `screen_view`; a `screen_view` carries the class
name of the screen in focus, such as `CycleCalendarActivity`. AppsFlyer sends a message
each time the app is opened or brought to the foreground.
What you enter in the app goes only to our own servers.
For the order's own purposes, health information "includes, but is not limited to, information concerning fertility, menstruation, sexual activity, pregnancy, and childbirth", and "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)" (order, Definition M, p. 5). The order also bans the company from disclosing health information to third parties for advertising (Section I, p. 8) and requires affirmative express consent before disclosing it for other purposes (Section III, p. 10).
The vendors set limits of their own. AppsFlyer "contractually restricts customers from processing" categories such as protected health information [6]. Google's policy for Analytics advertising features says that if you collect "sensitive information about your visitors", you "may not use Google Analytics to collect data for the purpose of interest based advertising" [7].
Check your own code
- List every call into an analytics or attribution SDK. On Android:
grep -rnE 'logEvent|trackEvent|\.track\(|AppEventsLogger' app/src. In React Native, look foranalytics().logEventandappsFlyer.logEvent. - Read each event name and parameter as the vendor receives it. A name such as
log_period_saveorsymptom_addedreports a health fact by itself. - Look for names built at run time (
"log_" + entry.type) and for screen names. Firebase logs ascreen_viewevent at each screen transition and identifies the screen by the class name of the Activity in focus [5], so anOvulationTestActivitysends that name. Settinggoogle_analytics_automatic_screen_reporting_enabledtofalsein the manifest turns that automatic reporting off. - To see what Firebase receives, run
adb shell setprop debug.firebase.analytics.app your.package.name, open DebugView in the Firebase console [8], and use the app. - Compare the third-party part of your privacy policy with what steps 1 to 4 found. Every event a vendor receives should be named there, and every promise there should hold for every call.
Sources
- Complaint for Permanent Injunction, Civil Penalty Judgment, and Other Relief, No. 1:23-cv-3107 (N.D. Ill.), filed 17 May 2023 — https://www.ftc.gov/system/files/ftc_gov/pdf/2023186easyhealthcarecomplaint.pdf
- Stipulated Order for Permanent Injunction, Civil Penalty Judgment, and Other Relief, No. 1:23-cv-3107 (N.D. Ill.), ECF No. 5, filed 22 June 2023 — https://www.ftc.gov/system/files/ftc_gov/pdf/2023.06.22_easy_healthcare_signed_order_2023.pdf
- Federal Trade Commission, case page for matter 202-3186 — https://www.ftc.gov/legal-library/browse/cases-proceedings/202-3186-easy-healthcare-corporation-us-v
- Federal Trade Commission, press release, 17 May 2023 — https://www.ftc.gov/news-events/news/press-releases/2023/05/ovulation-tracking-app-premom-will-be-barred-sharing-health-data-advertising-under-proposed-ftc
- Firebase documentation on screen-view tracking for Google Analytics — https://firebase.google.com/docs/analytics/screenviews?platform=android
- AppsFlyer, legal page on processing customer data (updated 13 February 2024) — https://www.appsflyer.com/legal/processing-customer-data
- Google Analytics Help, "[GA4] Policy requirements for Google Analytics Advertising Features" — https://support.google.com/analytics/answer/2700409
- Firebase documentation, DebugView — https://firebase.google.com/docs/analytics/debugview
- Google Analytics Help, "Automatically collected events" — https://support.google.com/analytics/answer/9234069
- AppsFlyer, "Integrate SDK" (Android) — https://dev.appsflyer.com/hc/docs/integrate-android-sdk
Quotations were checked against these sources on 17 November 2026.
This is general information about a published US settlement, written by a software developer; it is not legal advice and does not say whether any law applies to your product.
This article was written with AI assistance and checked against the official sources listed above.
WolfBoy on GitHub: github.com/innit-llc/wolfboy