Public pages use no advertising trackers. The secure portal uses an essential session cookie and the service providers described in our privacy policy.

Skip to main content

· Court ruling

Frasco v. Flo Health, Inc.

U.S. District Court for the Northern District of California, No. 3:21-cv-00757-JD

For plaintiffsJury verdict for a California class against Meta under Penal Code section 632; Meta's motions for decertification, judgment as a matter of law and a new trial denied; no final judgment as of November 10, 2026

Primary source: Order denying post-trial motions. Checked on November 10, 2026.

A federal jury found Meta violated California Penal Code section 632 by eavesdropping on or recording Flo app users' menstrual and ovulation answers through its software development kit, and the court denied post-trial motions.

What happened

Users of the Flo Period and Ovulation Tracker app sued Flo Health, Meta, Google and other companies, alleging among other things that Meta and Google obtained users' personal information through software development kits (SDKs) that each provided to Flo for integration into the app. Google and Flurry settled before trial, Flo settled during trial, and Meta Platforms was the only defendant left when the case went to the jury. (ECF No. 776 at 1-4.)

The court had certified a class of Flo app users who entered menstruation or pregnancy information into the app while residing in California between November 1, 2016 and February 28, 2019, for the section 632 claim against Meta and Google and a California constitutional privacy claim against Flo. It denied certification of a section 631(a) claim, which was not tried. (ECF No. 776 at 3, 7.)

At trial, the plaintiffs' expert testified that each answer a user gave in the app's mandatory onboarding survey, such as whether she wanted to get pregnant or to track her cycle, was logged as an event that triggered code written by Meta. That code recorded the event name and value and sent them to Meta's servers along with device and advertising identifiers that could link the data to a particular device or Facebook profile. (ECF No. 776 at 8-13.)

After about two weeks of trial, the jury deliberated for about three hours and returned a unanimous verdict on August 1, 2025. It answered that Meta intentionally eavesdropped on or recorded the plaintiffs' conversation by using an electronic device, that they reasonably expected the conversation was not being overheard or recorded, and that Meta did not have the consent of all parties. (ECF No. 776 at 1, 4-5; ECF No. 756.)

What the court held

  1. The jury answered yes to whether Meta intentionally eavesdropped on or recorded the plaintiffs' conversation by using an electronic device, yes to whether they had a reasonable expectation that it was not being overheard or recorded, and no to whether Meta had the consent of all parties. (ECF No. 756, Questions No. 1-3)

    Did Meta have the consent of all parties to the conversation to eavesdrop on and/or record it?

    ECF No. 756, Question No. 3
  2. The court refused to decertify or narrow the California class. It treated Meta's request as an improper attempt at reconsideration and held that the trial evidence confirmed that the privacy disclosures, the SDK's operation, consent and class members' expectations could be decided on common proof. (ECF No. 776 at 2, 5-25)

    Nothing in the evidence adduced at trial or the record as a whole justifies disturbing the California class or the jury’s unanimous verdict.

    ECF No. 776 at 2
  3. The court rejected Meta's argument that the SDK's transmissions were secondhand repetitions of separate communications between the app and Meta. Citing testimony that code written by Meta recorded the user's selections as the app logged and processed them, it held that the jury could find that Meta acquired the content of the users' communications in real time. (ECF No. 776 at 26-28)

    The evidence at trial amply supported the conclusion that Meta was directly acquiring the content of the user’s communications with the Flo App in real time.

    ECF No. 776 at 26
  4. Section 632 is not tied to a particular technology, and even if a physical device were required, the jury could find that a user's phone running the app and the SDK was the electronic recording device. (ECF No. 776 at 28-29)

    Even spotting Meta an assumption that a physical device is required, there was sufficient evidence for the jury to reasonably conclude that a Flo App user’s phone fit the bill.

    ECF No. 776 at 28
  5. The evidence supported a finding that Meta used the SDK intentionally, meaning with the purpose of recording confidential communications or with knowledge to a substantial certainty that its use would record them. The court pointed to evidence that Meta built and promoted the SDK, used the data in its advertising business, knew it was receiving personal health information through the SDK and did not restrict that data until after the class period; its terms telling developers not to send health information did not require a different result. (ECF No. 776 at 29-33)

    there was sufficient evidence at trial that Meta knew it was getting data it shouldn’t be getting, and it did not implement its own measures to stop that

    ECF No. 776 at 33
  6. The evidence supported the jury's finding that Meta lacked consent. Applying Calhoun v. Google, the court held that a reasonable user could find Meta's disclosures too ambiguous to notify users of the conduct at issue, and it noted that Flo's own policy excluded cycle and pregnancy information from the personal data it might share with third-party vendors. (ECF No. 776 at 33-35)

    Overall, Meta’s own policy cites undercut the notion that its users were given fair notice of the conduct at issue in this case.

    ECF No. 776 at 34
  7. The court rejected Meta's argument that the answers were not confidential because users knew Flo stored them. Read as a whole, the court said, the exclusion in section 632(c) covers circumstances where the parties expect to be overheard or recorded by someone outside the communication, not the app's own storage of the answers. (ECF No. 776 at 35-36)

    Construing Section 632 as a whole, it is plain that subsection (c) refers to communications in circumstances where the parties reasonably expect to be overheard or recorded by a non-party to the communication.

    ECF No. 776 at 35
  8. Unlike section 631, section 632 has no language limiting it to communications sent from or received in California, and in any event the evidence allowed the inference that the named plaintiffs were in California when they completed the onboarding survey. (ECF No. 776 at 17, 36-37)

  9. Statutory damages under California Penal Code section 637.2 require no injury beyond the privacy injury of an unconsented recording and no proof of actual damages, and they are not subject to a discretionary multi-factor test. The court contrasted the federal Wiretap Act, whose damages provision, 18 U.S.C. § 2520, it read as giving district courts discretion. (ECF No. 776 at 19-23)

    A plaintiff who suffers a privacy injury from the recording of her communications in violation of Section 632 need not demonstrate a further injury of some sort to be entitled to statutory damages under Section 637.2.

    ECF No. 776 at 20
  10. A new trial was denied: the verdict was not against the clear weight of the evidence, the intent instruction correctly stated California law, and Meta showed no evidentiary error or juror bias warranting a new trial. (ECF No. 776 at 38-44)

What it did not decide

  • The section 631(a) claim: certification was denied for it and it was not submitted to the jury (ECF No. 776 at 7, 17).
  • Any federal Wiretap Act claim; none was presented to the jury (ECF No. 776 at 39).
  • The remaining claims against Flo, Google and Flurry, which settled; before trial the court had granted Google summary judgment on the plaintiffs' California Unfair Competition Law and aiding-and-abetting claims (ECF No. 776 at 3). Before Flo settled during trial, the court said the plaintiffs appeared to have an insurmountable problem showing that the evidence met the California Confidentiality of Medical Information Act's definitions of patients, provider of health care and medical information, but it made no ruling (ECF No. 776 at 4).
  • Final judgment, and the notice plan and claims procedure for paying class members, which remained open as of the October 29, 2026 hearing (ECF No. 870).

The tracking involved

Tools

  • Facebook SDK (Meta's software development kit) built into the Flo mobile app

Data

  • onboarding survey answers logged as app events, such as the goal of getting pregnant, tracking a cycle or tracking a pregnancy
  • whether the user knew when her last period started and how long her period and cycle last, and her age
  • the app's calculation of her cycle day and phase, such as a fertility window or pregnancy
  • device and advertising 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.

  • Supports: State wiretap laws

    State interception statutes, such as California Penal Code § 631 and the Washington Privacy Act.

    This is a jury verdict under section 632 of the California Invasion of Privacy Act, left in place after post-trial motions, against a company whose code inside an app recorded users' answers. The court rejected arguments that the transmissions were secondhand repetitions, that code cannot be a recording device, that the answers were not confidential because the app itself stored them, and that intent requires more than knowledge to a substantial certainty that confidential communications would be recorded. The limits are real: the claim was under section 632 only, the section 631(a) class was not certified, the case involved a mobile app rather than a website, and the defendant was the code's supplier, not the app operator.

    All tracker entries on this issue

  • Supports: Consent

    Whether visitors agreed to the tracking through banners, privacy policies or terms.

    The jury found that Meta lacked the consent of all parties, and the court held the evidence supported that finding. Applying Calhoun v. Google, it asked whether a reasonable user reading the disclosures would think she was consenting to the data collection, and held that Meta's general statement that partners send information about how people use their services did not clearly identify the conduct. It also pointed to Flo's own privacy policy, which excluded cycle and pregnancy information from the personal data it might share with third-party vendors.

    All tracker entries on this issue

  • Supports: Damages

    What must be shown to recover money, including statutory damages and proof of actual loss.

    The court read California Penal Code section 637.2 to provide $5,000 per violation without proof of actual damages and without a discretionary multi-factor test, rejecting Meta's reliance on Campbell v. Facebook. It contrasted the federal Wiretap Act, whose damages provision, 18 U.S.C. § 2520, uses permissive language that the court read as granting district courts discretion in fashioning an award.

    All tracker entries on this issue

  • Supports: Class certification

    Whether claims can go forward on behalf of a whole class of website or app users.

    The court kept the California class certified after trial, holding that uniform privacy disclosures and the code's uniform operation were common proof, and that Meta offered no evidence of individual issues about consent, expectations of privacy, timing or location. It noted that Meta could challenge individual claims in a claims process and had not shown why questions about where class members were could not be handled there. The ruling rests on this trial record and on a class limited to California residents.

    All tracker entries on this issue

  • Supports: Standing and injury

    Whether the people suing were harmed in a way that lets a federal court hear the claim.

    The court recalled its certification finding that the record showed a concrete injury to class members' right to control access to their private information, whether or not the data was later anonymized. It also held that a section 632 violation occurs when the recording is made and that no further injury is needed for statutory damages under section 637.2 (ECF No. 776 at 6-7, 20).

    All tracker entries on this issue

  • Context: Health information

    What counts as individually identifiable health information when it is sent through tracking tools.

    The court described the recorded data as information about users' personal reproductive health and distinguished Smith v. Facebook, which involved viewing publicly available health information. The verdict did not turn on a statutory definition of health information, because section 632 asks whether a communication was confidential. Before Flo settled, the court said the plaintiffs appeared to have an insurmountable problem meeting the definitions in California's medical-information statute, but it made no ruling.

    All tracker entries on this issue

Arguments it addresses

The vendor received a separate transmission from the app, not the user's communication
The court held the jury could find that Meta's code recorded the user's own selections firsthand and in real time, not a secondhand repetition (ECF No. 776 at 26-28).
The vendor told developers not to send health information
The court held a rational jury could credit evidence that Meta knew it was receiving such data and did not stop it over Meta's statements to developers (ECF No. 776 at 32-33).
The user agreed to the privacy policy
The court held a reasonable user could find Meta's disclosures too ambiguous to give notice of the conduct, so the jury's finding of no consent stood (ECF No. 776 at 33-35).
The communication was not confidential because the app stored it
The court read section 632(c) to exclude only communications that the parties reasonably expect a non-party to overhear or record (ECF No. 776 at 35-36).
Computer code is not a recording device
The court held that section 632 is not tied to a particular technology and that, in any event, the jury could find a user's phone was the device (ECF No. 776 at 28-29).
No concrete injury, and damages need individual proof
For section 632, the court held that the privacy injury occurs when the recording is made and that statutory damages under section 637.2 need no proof of actual damages or individual factors (ECF No. 776 at 19-23).

For a company that received a letter

  • The verdict was against the company whose software development kit recorded the answers, not the app maker, which settled during trial, so the jury decided no claim against the app operator.
  • The claim tried was section 632 of the California Invasion of Privacy Act; certification of the section 631(a) claim was denied, and no federal Wiretap Act claim went to the jury.
  • The case involved answers users gave in a mobile app's mandatory onboarding survey, proved at trial with captures of network traffic, the app's code and testimony about what Meta knew, not page visits on a public website.
  • No final judgment had been entered as of November 10, 2026, and at an October 29, 2026 hearing the court said it expects one by January 2027 at the latest.

What to check on your own site

  • Check which events and parameters your site or app passes to third-party code, including answers to intake or onboarding questions.
  • Check whether the event names and values you log reveal what a user selected, such as a health goal or condition.
  • Check whether your privacy policy's statements about sharing match what third-party code on your site or app actually receives.

Later history

The jury returned its verdict on August 1, 2025, the last day of trial (ECF Nos. 755, 756). The court denied Meta's post-trial motions by order of September 15, 2025 (ECF No. 775) and issued an amended order on September 17, 2025 that corrected two typos and clarified two details without changing the substance (ECF No. 776 at 1 n.1). At an October 29, 2026 hearing it took under submission the motions for final approval of the Flurry, Google and Flo Health settlements, which total $59.5 million, and for fees; denied four other pending motions, among them the plaintiffs' motion for entry of judgment (ECF No. 846) and Meta's emergency motion to terminate and retract a class notice it called unauthorized (ECF No. 844), saying they indicated a breakdown in the parties' ability to work together; noted that the parties agree class members should receive $5,000 each under California Penal Code section 637.2; set a November 23, 2026 conference on the notice plan and claims procedure; and said it expects to enter final judgment on the class claim against Meta by January 2027 at the latest (ECF Nos. 860, 870). Later docket entries, through November 9, 2026, concern hearing records, and no final approval order or judgment had been entered as of November 10, 2026.

June 22, 2021 · Agency actionIn the Matter of Flo Health (FTC 2021)Agency actionThe 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.September 7, 2023 · Court rulingDoe v. Meta Platforms (N.D. Cal. 2023)Mixed rulingPatients' Wiretap Act and CIPA claims against Meta over its pixel on health care providers' patient portals survived dismissal, with the scope of covered content, Meta's intent and the providers' consent left to evidence.October 30, 2026 · Court rulingIn re Meta Pixel Healthcare Litigation (N.D. Cal. 2026)For plaintiffsA federal court certified classes of Facebook users suing Meta over health information allegedly obtained from provider websites and apps, holding that consent, intent and whether the data is contents are common questions.May 9, 2024 · Court rulingR.C. v. Walgreen (C.D. Cal. 2024)Mixed rulingFederal and California wiretap claims over a pharmacy site's alleged sharing of shoppers' health product selections with Meta survived dismissal because a viable state-law privacy claim supplied the tortious purpose.October 17, 2025 · Court rulingDoe v. Eating Recovery Center (N.D. Cal. 2025)For defendantsA federal court held Meta Pixel data from an eating disorder provider's site were contents of communications but rejected the California wiretap claim because Meta did not read or try to learn them in transit.November 14, 2024 · Court rulingCastillo v. Costco Wholesale (W.D. Wash. 2024)Mixed rulingRuling on the pleadings, a Seattle federal court held pharmacy customers' prescription searches sent to Meta were contents and a financial motive does not defeat the crime-tort exception, but dismissed the Washington Privacy Act claim.

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.