· Court ruling
Nichols v. PeaceHealth Networks on Demand LLC
U.S. District Court for the Western District of Washington, No. 2:25-cv-01831-JHC, ECF No. 16
Primary source: Order. Checked on November 10, 2026.
A Washington federal court dismissed a Wiretap Act claim over Google Analytics on a care provider's appointment website, finding no pleaded facts showing a criminal or tortious purpose separate from the disclosure.
What happened
A Washington resident with a Gmail account, who had booked medical appointments on zoomcare.com, brought a proposed class action for people who scheduled appointments on the site. The site belongs to PeaceHealth Networks on Demand LLC, doing business as ZoomCare, which operates a national network of primary and urgent care facilities. The complaint pleaded a single federal Wiretap Act claim and sought statutory damages, injunctive relief and attorney fees; the court took its allegations as true.
The complaint alleged that the operator embedded Google Analytics on the website for targeted advertising, and that the code intercepted users' interactions with the site and disclosed them to Google, including 'Custom Events', page addresses that disclosed scheduled medical appointments, and information related to medical conditions. It alleged that the disclosures violated users' reasonable expectations of privacy and the operator's obligations under HIPAA.
The complaint did not say how many appointments the plaintiff scheduled, when, or for what conditions; it stated that the specific appointments had been omitted to protect her privacy.
What the court held
Because the Wiretap Act is a one-party consent statute, a party to a communication generally cannot intercept it unless the crime-tort exception applies, and following Sussman v. American Broadcasting Cos. the focus is on the intended use of the interception, not whether the interception itself violated another law; the court added that an interception for the purpose of injuring a plaintiff tortiously triggers the exception if that purpose is pleaded. (ECF No. 16 at 5)
Thus, an “interception” of PHI for the purpose of financial gain is often not enough to trigger the crime-tort exception.
ECF No. 16 at 5 Following Nienaber v. Overlake Hospital Medical Center and B.K. v. Eisenhower Medical Center, the court required facts showing an interception for an unlawful act independent of the interception itself. (ECF No. 16 at 6)
a plaintiff must plead an unlawful act that is separate and secondary to the acquisition of the information, such as a tortious or criminal use of the intercepted materials, rather than solely pleading a disclosure.
ECF No. 16 at 6 The court read the decisions the parties cited on each side (Castillo v. Costco Wholesale Corp. and I.T. v. ChoicePoint LLC against Nienaber and B.K.) as turning on the pleadings in each case rather than on whether the exception can ever apply to website disclosures of health information. (ECF No. 16 at 6-7 & n.2)
the cases' divergent outcomes are based on differences in the parties' actual pleadings, particularly with respect to whether the complaint pleads a HIPAA violation
ECF No. 16 at 7 The plaintiff's assertions that the operator intended to violate HIPAA were conclusory and unsupported by facts in the complaint, which repeatedly alleged that the information was intercepted for targeted advertising and never alleged a disclosure for an unlawful purpose. Because the exception did not apply and the operator was undisputedly a party, the complaint did not plead an interception, and the claim was dismissed. (ECF No. 16 at 8)
The Complaint also does not specify what HIPAA-protected information was allegedly disclosed, nor whether such information was criminally and tortiously used, accessed, or otherwise implicated after the initial disclosure.
ECF No. 16 at 8 The court found that the complaint did not rest on a theory that the operator procured Google's interception, so it refused to dismiss on that ground, but it said any claim resting purely on procurement must be dismissed, noting that most courts have rejected procurement and aiding-and-abetting liability and that the Ninth Circuit has rejected secondary liability under the Act. (ECF No. 16 at 8-9 & nn.3-5)
the majority have rejected the notion that a defendant may be held liable for “aiding and abetting” or “procuring” an interception.
ECF No. 16 at 9 The court did not decide whether the data sent to Google were contents of communications, but encouraged the plaintiff to consider the operator's contents arguments in amending. (ECF No. 16 at 9-10)
The court refused to dismiss with prejudice and granted leave to amend by March 25, 2026, adding that if the plaintiff had privacy concerns she could seek to file the amended pleading under seal. (ECF No. 16 at 10-11)
because Plaintiff's ECPA claim fails as a matter of alleged facts, Plaintiff should be given an opportunity to cure the factual deficiencies identified in this Order before her claims are dismissed with prejudice.
ECF No. 16 at 10
What it did not decide
- Whether the information sent to Google was the contents of a communication; the court declined to reach that element.
- Whether a complaint that identifies the HIPAA-protected information disclosed, and its later use, would satisfy the crime-tort exception; the court described other decisions but decided only the complaint before it.
- Class certification, liability and damages.
The tracking involved
Tools
- Google Analytics
Data
- Custom events
- Page addresses disclosing scheduled appointments
- Information related to medical conditions (as alleged, not specified)
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.
Limits: Crime-tort exception
Whether a communication was intercepted for the purpose of a criminal or tortious act, which removes the party exception.
The court required facts showing the operator intercepted health-related information for the purpose of committing a criminal or tortious act separate from the disclosure, and found the complaint pleaded none: the plaintiff's assertions of intent to violate HIPAA were conclusory, and the complaint repeatedly alleged that the purpose was targeted advertising. It said an interception for financial gain is often not enough. The dismissal was without prejudice, and the court read conflicting decisions as turning on how well each complaint pleaded a HIPAA violation, not on a rule that the exception never applies to website disclosures.
Limits: Party exception
Whether the website, as a party to the visit, could consent to the tracking under 18 U.S.C. § 2511(2)(d).
Because the operator was undisputedly a party to the communications and the crime-tort exception was not adequately pleaded, the court held that the complaint did not plead an interception at all. Party status ended this version of the claim.
Limits: HIPAA
How HIPAA, its criminal provision at 42 U.S.C. § 1320d-6 and HHS guidance bear on tracking.
The court found that the complaint did not specify what HIPAA-protected information was disclosed or whether it was used after the disclosure. It cited decisions that applied the exception where a complaint plausibly alleged a HIPAA violation, so the ruling turns on the specificity of the pleading rather than rejecting HIPAA as a predicate.
Context: Health information
What counts as individually identifiable health information when it is sent through tracking tools.
The complaint withheld which appointments the plaintiff booked to protect her privacy, and the court faulted it for not specifying what HIPAA-protected information was disclosed. It did not decide whether appointment booking data or page addresses are health information, and it said the plaintiff could seek to file an amended complaint under seal if she had privacy concerns.
Limits: Interception
Whether a tracking tool acquired a communication as it was sent, who did it, and whether it was intentional.
The court said a claim resting purely on the operator procuring a vendor's interception must be dismissed, noting that most courts reject procurement and aiding-and-abetting liability and that the Ninth Circuit has rejected secondary liability under the Act. It found this complaint did not rely on that theory, and it treated the interception element as unmet because the operator was a party and the crime-tort exception was not adequately pleaded.
Arguments it addresses
- The website was a party to the communication
- The court agreed that, with the crime-tort exception not adequately pleaded, the operator's undisputed party status meant no interception was alleged.
- The purpose was advertising, not a crime
- The court said an interception for financial gain is often not enough and that repeated allegations of a targeted-advertising purpose did not plead an unlawful one.
- Calling it a HIPAA violation is not enough
- The court agreed where the complaint did not say what HIPAA-protected information was disclosed or how it was used afterward.
- The operator cannot be liable for procuring the vendor's interception
- The court said a pure procurement theory fails, but found that this complaint did not rest on one.
- The claim should be dismissed with prejudice
- The court refused, because the claim failed on the facts alleged rather than as a matter of law.
For a company that received a letter
- The dismissal rested on facts this complaint did not plead, and the court granted leave to amend rather than holding that such claims fail as a matter of law.
- The court treated the specifics of the health information disclosed, and what happened to it after disclosure, as central to pleading the crime-tort exception.
- The order said a claim resting only on the operator procuring a vendor's interception must be dismissed, relying on decisions rejecting procurement liability and on the Ninth Circuit's rejection of secondary liability under the Act.
- An amended complaint and a renewed motion to dismiss followed, and no ruling on that motion appears on the docket as read November 10, 2026.
What to check on your own site
- Check which custom events your analytics setup sends during appointment booking, and whether event names or parameters describe the visit type, clinic or reason for the visit.
- Check whether the page addresses of booking and confirmation pages reveal the appointment type or reason, since those addresses travel with ordinary page views.
Later history
The plaintiff filed a first amended complaint on March 25, 2026 (ECF No. 17). The operator moved to dismiss it on April 24, 2026 (ECF No. 25), discovery was stayed by stipulation on May 6, 2026 (ECF No. 27), and briefing closed on June 17, 2026 (ECF No. 29), followed by notices of supplemental authority filed through October 6, 2026 (ECF Nos. 30-33). The docket on CourtListener, read November 10, 2026, shows no ruling on that motion.
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.