· Court ruling
Cooper v. Mount Sinai Health System, Inc.
U.S. District Court for the Southern District of New York, 742 F. Supp. 3d 369, No. 1:23-cv-09485-PAE
Primary source: Opinion and order. Checked on November 10, 2026.
A federal court let a Wiretap Act claim over a health system's Meta Pixel proceed, holding that alleged disclosure of identifiable patient health information for commercial ends plausibly invoked the crime-tort exception through HIPAA.
What happened
According to the amended complaint, Mount Sinai Health System, Inc. owns and operates eight hospitals and more than a dozen medical centers in the New York City area, and it controls mountsinai.org and a MyChart patient portal that it licenses from Epic. Four New York residents sued in the Southern District of New York in October 2023 on behalf of a proposed class. (ECF No. 28 at 1-2 & n.2, 10.)
The amended complaint alleged that Mount Sinai used the Facebook Tracking Pixel and Facebook's Conversions API to send patients' information to Facebook without their knowledge or consent. It alleged that Mount Sinai configured PageView, Microdata and SubscribedButtonClick events and a custom MyChart event, and disclosed search queries, MyChart app use, bill page views, appointment request clicks and views of care and treatment options, along with Facebook IDs, IP addresses or device IDs and other information such as names, email addresses or phone numbers. (ECF No. 28 at 2, 6-7, 17.)
The amended complaint also alleged that Meta's Business Tools Terms require website owners to represent that they will not share data they know or reasonably should know includes health information, and that a primary reason Mount Sinai used the tools was to improve its marketing and reduce its marketing costs. (ECF No. 28 at 3, 7.)
Each plaintiff alleged entering information about his or her conditions on Mount Sinai's web properties and then receiving targeted social media advertisements related to them; the court noted that the conditions included anxiety/depression, pregnancy and high cholesterol. The court took these allegations as true for the motion. (ECF No. 28 at 1 n.1, 8-10.)
What the court held
The court read the crime-tort exception narrowly, following Caro v. Weintraub and In re DoubleClick Inc. Privacy Litigation: the crime or tort must be the primary motivation or a determinative factor, the purpose must exist at the time of interception and be independent of the recording, and a lawful purpose does not excuse an interception also made for an unlawful one. (ECF No. 28 at 11-12)
That a defendant's conduct was criminal or tortious does not suffice.
ECF No. 28 at 12 Mount Sinai did not dispute, for the motion, that it intercepted the communications, and the plaintiffs did not dispute that it was a party, so the claim turned on the crime-tort exception. The court noted a division between the Ninth and Third Circuits on whether a defendant that receives communications through tracking code that duplicates and forwards a browser's requests counts as a party, but said the issue was not implicated because Mount Sinai, as alleged, controlled and maintained its own web properties. (ECF No. 28 at 12-13 & n.7)
The court held that a purpose of knowingly disclosing individually identifiable health information in violation of HIPAA may satisfy the exception, and that allegations of names, emails, IP addresses, device identifiers, URLs, treatment dates, selected services, patient status, conditions, treatments and provider and appointment information, followed by advertisements keyed to the plaintiffs' conditions, made it plausible that some of what was sent was such information. (ECF No. 28 at 14-17)
These allegations make plausible that at least some information transmitted was individually identifiable health information.
ECF No. 28 at 16 Taking the allegations as true, the court held that the amended complaint plausibly alleged that Mount Sinai disclosed that information knowingly and deliberately, for commercial ends, because it allegedly configured the Pixel events itself and had an economic motive to improve its marketing. (ECF No. 28 at 17-18)
they plausibly support the inference that Mount Sinai, for commercial ends, intentionally disclosed individually identifiable patient health information, and thus violated HIPAA
ECF No. 28 at 18 The court said Mount Sinai remained free to show in discovery, at summary judgment or at trial that it acted without the required knowledge and intent. (ECF No. 28 at 17-18)
Mount Sinai may be able to establish, at summary judgment or trial, that it acted without the requisite knowledge and intent.
ECF No. 28 at 17-18 The court rejected Mount Sinai's argument that acting for monetary gain negates a criminal or tortious purpose, noting that 42 U.S.C. § 1320d-6 itself raises the penalty for disclosures made for commercial advantage and that the cases Mount Sinai cited did not involve HIPAA or similar statutes. (ECF No. 28 at 19-20)
Mount Sinai's broad theory that the presence of a primary financial motive inoculates a defendant from liability under the ECPA is wrong.
ECF No. 28 at 19 The court also rejected the argument that intent cannot be inferred from conduct, because the inference rested not only on the interception but on Mount Sinai's alleged business arrangement with Facebook. (ECF No. 28 at 20)
These allegations supply an adequate basis on which to infer criminal intent.
ECF No. 28 at 20 The court set aside two other theories. It rejected a fraud theory based on a Meta cookie allegedly presented as a first-party cookie, because nothing in the statute makes the party exception inapplicable to fraudulently induced communications, and it held that invasion of privacy could not supply the tortious purpose because New York recognizes no common-law privacy tort. (ECF No. 28 at 13-14 n.8)
Under New York law, that is insufficient to trigger the crime-tort exception.
ECF No. 28 at 13 n.8 The court held that the patients stated a claim under New York General Business Law section 349. The amended complaint alleged that Mount Sinai's privacy policy and HIPAA privacy notice were false in saying patient data would not be shared, and a privacy injury from collecting confidential, individually identifiable information without knowledge or consent can support the claim. (ECF No. 28 at 20-22)
New York courts have held that a privacy injury can be the basis for a § 349 claim
ECF No. 28 at 21 The court let the negligence, breach of implied contract, breach of fiduciary duty, breach of confidence, constructive bailment and implied covenant claims proceed, rejecting arguments that negligence could not be pleaded alongside intentional conduct and that the other claims duplicated an unpleaded physician-patient confidentiality claim. (ECF No. 28 at 22-25)
Accordingly, the Court denies Mount Sinai's motion to dismiss the above common-law claims.
ECF No. 28 at 25 The court dismissed the unjust enrichment claim as duplicative of the contract and tort claims, and dismissed the invasion of privacy claim on consent after the plaintiffs withdrew it. (ECF No. 28 at 22 n.11, 25-27)
The Court accordingly dismisses this claim as duplicative.
ECF No. 28 at 27
What it did not decide
- Whether Mount Sinai in fact acted with the required knowledge and intent; the court said it could try to show otherwise at summary judgment or trial (ECF No. 28 at 17-18).
- Whether Mount Sinai intercepted the communications; it did not dispute interception for purposes of the motion (ECF No. 28 at 12-13).
- Whether a defendant that receives communications through tracking code that duplicates and forwards a browser's requests is a party; the court noted the division of authority but said the issue was not implicated (ECF No. 28 at 13 n.7).
- Whether Rule 9(b) applies to a fraud-based theory; the court said it was not clear and rejected the theory on other grounds (ECF No. 28 at 13 n.8).
- Article III standing, class certification and statutory damages; the opinion does not address them.
The tracking involved
Tools
- Facebook Tracking Pixel (Meta Pixel)
- Facebook Conversions API (sent from the website owner's servers)
Data
- PageView events with page URLs
- Microdata page metadata
- SubscribedButtonClick events with button text
- custom MyChart events
- search queries
- bill page views and appointment request clicks
- care and treatment option views
- Facebook IDs, IP addresses and device IDs
- names, email addresses and phone numbers
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: Party exception
Whether the website, as a party to the visit, could consent to the tracking under 18 U.S.C. § 2511(2)(d).
The plaintiffs did not dispute that Mount Sinai was a party to its patients' communications with its web properties, so the Wiretap Act claim depended on the crime-tort exception (ECF No. 28 at 12-13). The court noted a division between the Ninth and Third Circuits on whether a defendant that receives communications through code that duplicates and forwards a browser's requests is a party, but did not decide it (ECF No. 28 at 13 n.7). It also held that alleged deception, such as a Meta cookie presented as a first-party cookie, does not by itself remove the party exception (ECF No. 28 at 13 n.8).
Context: Interception
Whether a tracking tool acquired a communication as it was sent, who did it, and whether it was intentional.
Mount Sinai did not dispute interception for purposes of its motion, so the ruling decides nothing about whether the Pixel or the Conversions API intercepts communications (ECF No. 28 at 12-13). The opinion describes the plaintiffs' allegations that the Pixel duplicates the browser's requests to Facebook and that the Conversions API sends data from the website owner's servers (ECF No. 28 at 3-4).
Supports: Crime-tort exception
Whether a communication was intercepted for the purpose of a criminal or tortious act, which removes the party exception.
Applying a narrow reading of the exception, the court held that an alleged purpose of disclosing individually identifiable health information for commercial ends, in violation of 42 U.S.C. § 1320d-6, plausibly satisfies it (ECF No. 28 at 12, 14-18). It rejected the argument that a financial motive negates a criminal purpose where the predicate is a HIPAA disclosure, and it based the inference of intent on the operator's own configuration choices and its alleged business arrangement with Facebook (ECF No. 28 at 17-20). The holding rests on the HIPAA predicate, and the court left Mount Sinai free to disprove intent later (ECF No. 28 at 17-18).
Supports: HIPAA
How HIPAA, its criminal provision at 42 U.S.C. § 1320d-6 and HHS guidance bear on tracking.
The court described 42 U.S.C. § 1320d-6 as making it a crime for a covered entity, including a health care provider, to knowingly disclose individually identifiable health information without authorization, with enhanced penalties when done for commercial advantage or personal gain (ECF No. 28 at 14, 19). Under that statute, a commercial purpose aggravates the offense rather than excusing it, which is why the profit-motive defense failed (ECF No. 28 at 19). The theory therefore depends on the operator being a HIPAA covered entity and the information meeting HIPAA's definition.
Supports: Health information
What counts as individually identifiable health information when it is sent through tracking tools.
The court found it plausible that at least some transmitted information was individually identifiable health information, pointing to identifiers sent with conditions, treatments, patient status and appointment details, and to advertisements keyed to conditions the plaintiffs had entered (ECF No. 28 at 15-17). It cited, by contrast, decisions that found allegations about metadata or publicly accessible pages insufficient, so the result turned on specific allegations about each plaintiff (ECF No. 28 at 16).
Supports: Consumer protection
Deception and unfair practice claims, such as under the FTC Act and N.Y. General Business Law § 349.
The GBL § 349 claim survived because the privacy policy and HIPAA privacy notice allegedly promised that patient data would not be shared, and the court held that a privacy injury can satisfy section 349 when confidential, individually identifiable information is collected without knowledge or consent (ECF No. 28 at 20-22). It found causation adequately pleaded where the promises allegedly induced patients to submit their data and lose control of it (ECF No. 28 at 22).
Limits: State privacy laws
Other state privacy statutes and claims, such as medical information and health records acts and the CCPA.
The court held that invasion of privacy could not supply the tortious purpose for the crime-tort exception because New York has no common-law privacy tort, and the plaintiffs withdrew their invasion of privacy claim (ECF No. 28 at 13-14 n.8, 22 n.11). In New York, a crime-tort theory therefore needs a different predicate, here HIPAA. The court noted that invasion of privacy may satisfy the exception where state common law recognizes it, as Connecticut common law did in Caro (ECF No. 28 at 13-14 n.8).
Arguments it addresses
- The website was a party to the communication
- The plaintiffs did not dispute party status, and the court held the crime-tort exception plausibly pleaded, so party status did not defeat the claim at this stage (ECF No. 28 at 12-13, 20).
- A financial motive means no criminal or tortious purpose
- The court rejected this where the alleged predicate is a HIPAA disclosure, because section 1320d-6 punishes disclosures made for commercial advantage more severely (ECF No. 28 at 19).
- Criminal intent cannot be inferred from the tracking itself
- The court held that the inference rested not merely on the interception but also on the alleged business arrangement with Facebook, which supplied an adequate basis to infer criminal intent at the pleading stage (ECF No. 28 at 20).
- This is metadata, not health information
- The court held that identifiers sent with conditions, treatments and appointment details, followed by condition-specific advertisements, made it plausible that some information was individually identifiable health information (ECF No. 28 at 15-17).
- Privacy injuries are not cognizable under GBL § 349
- The court rejected this, holding that collecting confidential, individually identifiable information without knowledge or consent can be a section 349 injury (ECF No. 28 at 21-22).
- Negligence cannot be pleaded with intentional conduct
- The court held that a complaint may plead negligent and intentional conduct in the alternative (ECF No. 28 at 22-23).
For a company that received a letter
- This was a ruling on the pleadings: the court took the allegations as true and said Mount Sinai could try to show at summary judgment or trial that it lacked the required knowledge and intent.
- The Wiretap Act holding depends on HIPAA's criminal provision, so its reasoning applies most directly where the website operator is a HIPAA covered entity.
- The court relied on the operator's own choices, such as which Pixel events it configured, and on what its privacy policy and notice promised.
- The case later settled for $5,256,588 without any admission of liability, and Mount Sinai denied the allegations, including that any medical information was shared with Facebook.
What to check on your own site
- List the Meta Pixel events configured on your site, such as page views, button clicks and custom events, and check what page data and button text each one carries.
- Check whether any tracking code runs inside your patient portal or app, and what a server-side conversions connection forwards from your own servers.
- Compare your privacy policy and notice of privacy practices with what your tags actually send.
Later history
Mount Sinai moved to certify the crime-tort ruling for an interlocutory appeal under 28 U.S.C. § 1292(b), and the court denied the motion on September 6, 2024 (ECF No. 41). Mount Sinai later agreed to pay $5,256,588 into a non-reversionary settlement fund for a class of MyChart account holders who logged in through mychart.mountsinai.org between October 27, 2020 and October 27, 2023 (ECF No. 64-1). In the settlement documents Mount Sinai denied the allegations, including that any medical information from the portal or website was shared with Facebook, and the agreement called for it to give class counsel a declaration that no tracking technologies were embedded in the portal during that period. The court granted final approval on November 4, 2025, finding that the settlement resolved the claims of approximately 1,314,147 people, dismissed the released claims with prejudice and stated that the settlement is not an admission of liability (ECF No. 79). On September 3, 2026, the court directed $56,328.83 in unclaimed funds, plus interest, to Ronald McDonald House New York (ECF No. 84). No later docket entry appears on CourtListener as of November 10, 2026.
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.