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

In re Meta Pixel Healthcare Litigation (Doe v. Meta Platforms, Inc.)

U.S. District Court for the Northern District of California, 690 F. Supp. 3d 1064, No. 3:22-cv-03580-WHO, ECF No. 316

Mixed rulingMeta's motion to dismiss the consolidated complaint granted in part and denied in part, with leave to amend

Primary source: Order on motion to dismiss. Checked on November 10, 2026.

Patients' 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.

What happened

Five Facebook users, proceeding anonymously, sued Meta Platforms, Inc. They alleged that their health care providers, MedStar Health System, Rush University System for Health, WakeMed Health & Hospitals, Ohio State University Wexner Medical Center and North Kansas City Hospital, installed the Meta Pixel on their patient portals, and that when the plaintiffs logged in, the pixel sent Meta information revealing their status as patients, which Meta monetized through targeted advertising (ECF No. 316 at 1-2).

In 2022 the court had denied a preliminary injunction, while finding that the plaintiffs made a strong showing that log-in buttons and descriptive URLs with full paths and query strings are contents (at 2, 5). On this motion, Meta argued that web developers, not Meta, decide whether to install the pixel and what it sends, that Meta's terms forbid developers from sending sensitive health information, and that Meta filters out sensitive data it detects (at 4).

The consolidated complaint pleaded 13 claims, including the federal Wiretap Act, the California Invasion of Privacy Act (CIPA), invasion of privacy, contract, consumer protection, computer access and larceny claims (at 2). The order was issued by Judge William H. Orrick on September 7, 2023 (at 26).

What the court held

  1. Intent to intercept was adequately alleged despite Meta's contractual ban on developers sending sensitive data and its filtering, because the complaint plausibly alleged that Meta's tools and filters were ineffective. The court said Meta's true intent, the steps it took and how well its filters worked are questions for the evidence. (ECF No. 316 at 3-5)

    all turn on disputed questions of fact that need development on a full evidentiary record.

    ECF No. 316 at 4
  2. Covered content was adequately alleged. The court repeated its earlier view that log-in buttons and descriptive URLs are contents and left the boundaries of what is content to a full evidentiary record. (ECF No. 316 at 5-6)

    At this juncture, plaintiffs have adequately alleged covered content is transferred. The boundaries of what transferred information is content under the Act is better determined on a full evidentiary record.

    ECF No. 316 at 6
  3. The one-party consent exemption did not defeat the claim on the pleadings. Meta bears the burden on consent, and whether the health care providers actually consented to sending sensitive health information depends on what Meta disclosed to them, how it described and trained them on the pixel, and how they understood it. The motion to dismiss the Wiretap Act claim was denied. (ECF No. 316 at 6-8)

    These evidence-bound determinations are inappropriate to reach on this motion.

    ECF No. 316 at 8
  4. The CIPA claim survived. The court declined to dismiss it on extraterritoriality grounds because the alleged conduct occurred in and emanated from California and Meta's terms select California law, accepted the allegation that Meta designed and carried out the tracking from California as sufficient on where the communications were sent or received, held intent adequately alleged, and treated the pixel software as a device. (ECF No. 316 at 8-11)

    absent contrary authority under section 632(a), I agree that the Pixel software is a device under section 632(a).

    ECF No. 316 at 11
  5. The California constitutional privacy and intrusion upon seclusion claims were dismissed with leave to amend, because the named plaintiffs had not identified the types of sensitive health information they gave their providers that Meta allegedly received. (ECF No. 316 at 11-12)

    plaintiffs are required to amend to describe the types or categories of sensitive health information that they provided through their devices to their healthcare providers.

    ECF No. 316 at 12
  6. The breach of contract and good faith claims survived. Meta's limitation of liability clause did not bar them at this stage, and the terms in which Meta said it requires partners to have the right to share information and uses teams and systems to detect misuse were definite enough to support a breach claim. (ECF No. 316 at 15-18)

  7. The unjust enrichment claim survived as an alternative claim. (ECF No. 316 at 19)

  8. The claims under California's Comprehensive Computer Data Access and Fraud Act (CDAFA), Unfair Competition Law (UCL) and Consumers Legal Remedies Act (CLRA), and the negligence per se, trespass to chattels and larceny claims, were dismissed with leave to amend. The negligence per se claim failed because, following most courts, HIPAA could not supply the duty, and the UCL claim failed for lack of lost money or property. (ECF No. 316 at 12-15, 19-26)

What it did not decide

  • Where the line falls between content and other data the pixel transmits (ECF No. 316 at 6).
  • Whether the health care providers actually consented to sending their patients' sensitive information to Meta (at 7-8).
  • Meta's actual intent and how well its filters worked, which the court left to the evidence (at 4, 9).
  • Choice of law; the court said it was not determining or foreclosing any choice-of-law issue (at 9).
  • Whether the crime-tort exception applies; with consent unresolved, the order did not reach it.
  • Any claim against the health care providers whose portals carried the pixel; the order decides Meta's motion only.

The tracking involved

Tools

  • Meta Pixel
  • Meta _fbp cookie

Data

  • Patient portal log-in activity revealing patient status
  • Log-in button clicks
  • Descriptive URLs with paths and query strings
  • Other health information patients communicated through providers' websites, which the named plaintiffs did not specify

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: Interception

    Whether a tracking tool acquired a communication as it was sent, who did it, and whether it was intentional.

    The court held that a vendor's contractual instruction not to send health data, and its back-end filters, did not defeat intent to intercept on the pleadings, because what the vendor actually intended and how well the filters worked are fact questions. The ruling concerns the vendor's intent, not a website operator's. In a later order the court noted that another judge in the district had found intent not adequately alleged against Google on different allegations (ECF No. 659 at 2).

    All tracker entries on this issue

  • Supports: Contents

    Whether what was sent, such as page addresses, searches and clicks, counts as the contents of a communication.

    The court held that the complaint adequately alleged the transfer of covered content, building on its earlier finding that portal log-in buttons and descriptive URLs with full paths and query strings concern the substance of a communication. It expressly left the line between content and other data to the evidence, so Meta's argument that much of the transmitted data is not content remained open.

    All tracker entries on this issue

  • Context: Consent

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

    Meta argued that the health care providers consented by installing the pixel on their sites. The court held that actual consent depends on what Meta disclosed to the providers, how it described and trained them on the pixel, and how they understood what it collected, which could not be decided on the pleadings. The ruling addresses the vendor's consent defense and does not decide any claim against the providers.

    All tracker entries on this issue

  • Supports: State wiretap laws

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

    The CIPA claim survived against a California-based vendor even though no named plaintiff lived in California, because the alleged conduct occurred in and emanated from California and Meta's terms select California law. The court treated the pixel software as a device under section 632(a). These rulings rest on Meta's California location and conduct, and the court left choice of law open.

    All tracker entries on this issue

  • Limits: State privacy laws

    Other state privacy statutes and claims, such as medical information and health records acts and the CCPA.

    The California constitutional privacy and intrusion claims were dismissed with leave to amend because the named plaintiffs had not said what kinds of sensitive health information they shared, given that the pixel also collects information that is not sensitive. The court required only a general description of the categories. The amended claims later survived a second motion to dismiss (ECF No. 417).

    All tracker entries on this issue

  • Limits: Consumer protection

    Deception and unfair practice claims, such as under the FTC Act and N.Y. General Business Law § 349.

    The UCL claim failed because the plaintiffs did not allege lost money or property, and the court found their theory that health data has market value inconsistent with allegations that they did not want anyone but their providers to have it. The CLRA claim failed because no plaintiff alleged seeing and relying on Meta's statements. Both were dismissed with leave to amend.

    All tracker entries on this issue

  • Limits: HIPAA

    How HIPAA, its criminal provision at 42 U.S.C. § 1320d-6 and HHS guidance bear on tracking.

    Following what it described as the majority of cases, the order held that HIPAA could not supply the duty of care for a negligence per se claim and gave the plaintiffs leave to identify a state-law source of the duty. The order noted contrary authority, In re Ambry Genetics Data Breach Litigation. The order does not cite HHS's guidance on tracking technologies.

    All tracker entries on this issue

Arguments it addresses

Meta's contracts forbid partners from sending health data
The court held that Meta's terms and filters did not defeat intent on the pleadings, because whether they reflected its true intent and worked in practice are fact questions (ECF No. 316 at 4-5).
The website operator consented, so the one-party consent rule applies
The court held that whether the providers actually consented to sending sensitive health information depends on evidence about what Meta told them and how they understood the pixel (at 6-8).
Most of the transmitted data is not content
The court held covered content adequately alleged and left the line between content and other data to the evidence (at 5-6).
CIPA does not protect people outside California
The court declined to dismiss on that ground at the pleading stage because the alleged conduct occurred in and emanated from California, without deciding choice of law (at 8-9).
Software is not a device
Absent contrary authority under section 632(a), the court held that the pixel software is a device under that section (at 10-11).
HIPAA has no private right of action
The court agreed that HIPAA could not supply the duty for negligence per se, following most courts, and allowed amendment to identify a state-law duty (at 19-20).
No lost money or property
That argument defeated the UCL claim, with leave to amend; the Wiretap Act, CIPA, contract and unjust enrichment claims survived the same motion (at 15-19, 22-26).

For a company that received a letter

  • This order decided claims against Meta as the pixel's vendor, not against the health care providers whose portals carried it.
  • The court said actual consent turns on what Meta disclosed to providers about the pixel and how they understood it, and it left those facts to the evidence.
  • Meta's contractual ban on sending health data and its filtering did not end the case at the pleading stage; the court left their effect to the evidence.
  • Later rulings in the same case let amended privacy claims proceed in January 2024 and certified classes in part on October 30, 2026.

What to check on your own site

  • Check whether advertising tags load on patient portal log-in pages and what a log-in button click sends.
  • Check whether full page addresses, including paths and query strings, reach advertising vendors from health-related pages.

Later history

The case remains pending. On January 29, 2024, the court denied Meta's motion to dismiss the amended privacy, computer access and trespass claims, except a Consumers Legal Remedies Act claim the plaintiffs abandoned (ECF No. 417). On October 2, 2024, it refused to certify this order's intent ruling for interlocutory appeal (ECF No. 659). On October 30, 2026, it granted class certification, except that the CIPA section 631 class was limited to patients who communicated from California or with a California-based health care provider and the class for the Comprehensive Computer Data Access and Fraud Act claim was to be redefined (ECF No. 1425 at 16-17, 37).

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.July 24, 2023 · Court rulingKurowski v. Rush System for Health (N.D. Ill. 2023)Mixed rulingPatients' Wiretap Act claim was dismissed because the complaint plausibly alleged only metadata, not health information, but their Illinois Eavesdropping Act claim proceeded against the health system as a principal benefiting from third-party cookies.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.August 1, 2025 · Court rulingFrasco v. Flo Health (N.D. Cal. 2025)For plaintiffsA 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.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.