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
← Back to Resources
Case notes·November 10, 2026·6 min read

Doe v. Baystate Health: A Patient's Hospital Searches, Meta, Google and the Wiretap Act

A Massachusetts federal court let a patient's claims proceed over Meta Pixel and Google Analytics on a hospital website. What it held and why it matters.

PR
Privacy Resolve
Last reviewed November 10, 2026

A patient goes to her hospital's website to read about breast cancer screening, looks up doctors, schedules a mammogram and signs in to the patient portal. She later learns that code on the site reported those steps, along with her Facebook ID, to Meta and Google. Doe v. Baystate Health System, Inc. is a federal court's answer to whether that patient can sue, and the answer at the pleading stage was yes on every claim she brought.

The case at a glance

Doe v. Baystate Health System, Inc., 2026 WL 776861 (D. Mass. Mar. 19, 2026), No. 1:25-cv-10337-JEK, ECF No. 42. Decided March 19, 2026, by the United States District Court for the District of Massachusetts (Judge Kobick), which denied the hospital's motion to dismiss in full.

A patient's searches and a mammogram appointment

The hospital's website lets people research conditions and doctors, request appointments, register for support groups and sign in to a patient portal, and it has search bars for conditions, procedures and physicians. According to the complaint, the hospital added the Meta Pixel and Google Analytics to the site in January 2021. Its privacy policy said, until May 2023, that identifiable information would be used only to support the patient relationship and would be disclosed only when the law required it or with specific written consent.

The plaintiff had been a patient for more than ten years. She alleged that the site sent Meta and Google her searches about breast cancer screening and providers, her mammogram scheduling, her status as a patient, her Facebook ID and other identifiers. She used Meta's own activity report, which lists what other businesses have shared with Meta, to identify communications from the hospital's site, and she found Meta and Google cookies on the device she used. She sued for violation of the federal Wiretap Act, invasion of privacy under the Massachusetts privacy statute (M.G.L. c. 214, § 1B), breach of implied contract and breach of fiduciary duty.

What the court held

The information was intimate medical information. "Doe's communications about cancer screenings and medical providers, her status as a patient, and her scheduling of a mammogram constitute medical information of a highly intimate or personal nature under Section 1B."

The crime-tort exception applied. The court noted that "All agree that Baystate was a party to the communications at issue in this case." A party is protected by the Wiretap Act's one-party consent rule unless it intercepted for the purpose of committing a crime or tort. Here: "Doe plausibly alleges that Baystate intentionally intercepted her communications on its website for the purpose of committing a tortious act in violation of M.G.L. c. 214, § 1B." The court described the theory this way: "Doe's theory is that Baystate decided, based on a cost-benefit analysis, not to tell patients the truth in its Privacy Policy and Notice of Privacy Practices in order to encourage them to submit their private health information, which, in turn, it disclosed to third parties for commercial gain."

The tort was separate from the interception. "Unlike a claim for intrusion upon seclusion, Doe's invasion of privacy claim is premised on Baystate's intent to disclose confidential medical information to Meta and Google without her consent, not merely its intent to intercept her communications." The court concluded: "Since Doe's factual allegations support the plausible inference that Baystate intercepted her communications for the purpose of committing a tortious act separate from the interception itself, the crime-tort exception under 18 U.S.C. § 2511(2)(d) applies."

What was sent counted as "contents." "These factual allegations are sufficient to treat Doe's intercepted private health information and personal identifiers as 'contents' for purposes of the ECPA."

The contract and fiduciary claims survived too. The implied contract claim rested on the allegation that the patient entered her information on the hospital's website as part of her care, relying on the privacy policy's promise that it would not be shared without her consent (ECF No. 42 at 13-14). On the fiduciary claim, the court wrote: "As part of 'the medical profession,' however, hospitals have a 'professional duty' not to disclose patients' private health information without their consent." The motion was denied on all four counts.

Why it matters for patients whose hospital searches were shared

This decision tracks an ordinary patient's experience closely. The communications at issue were not a portal record or a lab result; they were searches about a screening, the names of providers, an appointment request and a sign-in, the kinds of things people do on a hospital website every day. The court treated them, once paired with a Facebook ID, as both the substance of the patient's communications and medical information of a highly intimate nature.

It also shows how a state privacy law can carry a federal claim. The Massachusetts statute forbids unreasonable, substantial or serious interference with privacy, and the court located the wrong in the disclosure to Meta and Google rather than in the act of recording. Many states have privacy statutes or common-law claims built around disclosure, which is why the reasoning can matter outside Massachusetts.

The privacy policy mattered, but not in the way websites usually hope. The hospital's promises about how identifiable information would be used supported the inference that it acted for an improper purpose when the site did something else. For a patient, that means the privacy policy and notice of privacy practices are worth reading closely: what they promised can become part of the claim.

And the case shows a practical step. The plaintiff used Meta's report of activity that other businesses share with it to identify what the hospital's site had sent. Anyone with a Meta account can review the same kind of report in the account's settings.

What the hospital argued, and how the court answered

Party status. The hospital was a party to the communications, and the court said so. But being a party only triggers the one-party consent rule, and the rule has an exception for interceptions made to commit a crime or tort. The disclosure to third parties, alleged to violate the state privacy statute, satisfied it at this stage.

Marketing, analytics and financial gain. The court held that the complaint's allegations that the hospital installed the tools "for marketing and/or analytics purposes" and "for financial gain" did not change the result, because "the existence of a lawful purpose does not mean that the interception is not also for a tortious or unlawful purpose." Which purpose was primary is "a question of fact not fit for resolution at the pleading stage." On the state claim, the court likewise held that whether marketing and analytics are legitimate interests that outweigh a patient's privacy is "a question of fact not suitable for resolution on a motion to dismiss."

Independence. The court distinguished intrusion upon seclusion, which happens through the act of interception, from the Massachusetts claim, which rests on the plan to disclose: "Put otherwise, Baystate's alleged intent to intercept Doe's communications was, as alleged, independent of its plan to disclose those communications to third parties."

Identification. The hospital argued that browsing its public website could not identify an individual or her health information, relying on the 2024 Texas ruling that vacated part of federal tracking guidance. The court held that the argument ignored the plaintiff's specific allegations about what was sent, including her Facebook ID, her patient status and her searches (ECF No. 42 at 11-12).

What that Texas ruling did and did not decide is covered in our guide to AHA v. Becerra and tracking guidance.

Subsequent history

No later order disturbs the ruling. The case has continued in the district court since March 2026, and none of the later docket entries is a ruling that changes it. The decision accepts the complaint's allegations as true at the pleading stage and makes no finding that they are true; the hospital has not been found liable.

Read the opinion

Related case notes: M.C. 1 v. Curriculum Associates, which relied on this decision, and Garcia v. Truist.

Checked on November 10, 2026.

Privacy Resolve is not a law firm, and this is not legal advice.

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.