The federal Wiretap Act is a one-party consent statute, but the exception is narrower than the label suggests. This guide is for lawyers on either side of a website tracking claim. It works through who counts as a party to a visitor's exchange with a website, whose consent matters and when, who has to prove it, and why consent does not end the analysis on its own. For an overview of the statute, see Federal Wiretap Act for Websites.
What does one-party consent mean under the federal Wiretap Act?
It means an interception is not unlawful under the Act when the interceptor is a party to the communication or one party gave prior consent, unless the purpose was to commit a criminal or tortious act. The exception for private persons is 18 U.S.C. § 2511(2)(d):
It shall not be unlawful under this chapter for a person not acting under color of law to intercept a wire, oral, or electronic communication where such person is a party to the communication or where one of the parties to the communication has given prior consent to such interception unless such communication is intercepted for the purpose of committing any criminal or tortious act in violation of the Constitution or laws of the United States or of any State.
Section 2511(2)(c) states the same party and prior-consent rule for a person acting under color of law, without the purpose clause. In a website case the private-person version applies, and it raises three questions: who is a party, whether a party gave prior consent, and whether the purpose clause takes the interception back out of the exception. This guide covers the first two. The third has its own guide, The Wiretap Act's Crime-Tort Exception.
Who is a party to a website visit?
The visitor and the website operator are parties to their own exchange. The Act does not define "party," and an operator's own status is often not in dispute: in Doe v. Baystate Health System, Inc., No. 1:25-cv-10337-JEK, ECF No. 42, at 7 (D. Mass. Mar. 19, 2026), 2026 WL 776861, the court noted that "[a]ll agree that Baystate was a party to the communications at issue in this case."
The harder question is the vendor. Its code runs on the operator's page, and the visitor's browser sends the vendor a request carrying details of the visit. Whether that vendor is a "party" depends on which circuit's law applies.
Is the advertising or analytics vendor also a party?
It depends on the circuit. The Ninth Circuit holds that a vendor receiving a simultaneous, unknown duplicate of the visitor's communication is not exempt as a party as a matter of law; the Third Circuit treats a vendor the browser contacts directly as a party.
The Ninth Circuit. In In re Facebook, Inc. Internet Tracking Litigation, 956 F.3d 589, 607-08 (9th Cir. 2020), cert. denied sub nom. Facebook, Inc. v. Davis, No. 20-727 (U.S. Mar. 22, 2021), the court noted that the Act does not say who counts as a party for its liability exemption, and that other circuits have read the term in different ways. It adopted the First and Seventh Circuits' understanding that "simultaneous, unknown duplication and communication of GET requests do not exempt a defendant from liability under the party exception," and held that the defendant was not exempt as a matter of law. The ruling came at the pleading stage, and the court said it did not "opine whether the Plaintiffs adequately pleaded the other requisite elements of the statutes."
The Third Circuit. In In re Google Inc. Cookie Placement Consumer Privacy Litigation, 806 F.3d 125, 140-41 (3d Cir. 2015), the court reasoned that when users' browsers communicate directly with an advertising company about the pages they are visiting, that company has no need to acquire the information from transmissions to which it is not a party. The federal claims in that case were dismissed. In Cole v. Quest Diagnostics, Inc., No. 25-1449 (3d Cir. Nov. 13, 2025) (not precedential), the court applied the same reasoning to claims under California's Invasion of Privacy Act, writing that "[a]s the recipient of a direct communication from Plaintiffs' browsers, Facebook was a participant in Plaintiffs' transmissions." The reasoning in both cases rests on the visitor's browser sending its own message straight to the vendor.
Neither line of cases addressed a site that routes the visitor's events through its own server. Where the browser sends its requests to the site's own domain and a server the operator runs forwards the data to the vendor, the direct-communication premise of the Third Circuit cases is absent on the facts. Meta Conversions API and Server-Side Tagging explains how that routing works.
Whose consent counts, and when must it be given?
Consent must come from a party to the communication and must be given before the interception; the statute says one of the parties "has given prior consent to such interception." In a website case the vendor usually relies on the operator's consent, because the operator put the vendor's code on its pages. The visitor's consent is a separate question.
The First Circuit has said that consent "may be explicit or implied, but it must be actual consent rather than constructive consent." In re Pharmatrak, Inc., 329 F.3d 9, 19 (1st Cir. 2003), on remand, summary judgment granted, 292 F. Supp. 2d 263 (D. Mass. 2003) (interception not intentional). Whether a visitor actually consented turns on what the visitor saw and chose before the requests left the browser.
State law can demand more. California's Penal Code § 631(a) reaches a person who acts "willfully and without the consent of all parties to the communication." The Ninth Circuit, in an unpublished memorandum, concluded that the California Supreme Court would read § 631(a) "to require the prior consent of all parties to a communication," so consent given after the communication does not satisfy it. Javier v. Assurance IQ, LLC, No. 21-16351, 2022 WL 1744107, at *2 (9th Cir. May 31, 2022) (unpublished mem.), on remand, 649 F. Supp. 3d 891 (N.D. Cal. 2023) (dismissing the Section 631(a) claim as time-barred, with leave to amend), and No. 20-cv-02860-CRB, 2023 WL 3933070 (N.D. Cal. June 9, 2023) (dismissing without leave to amend; judgment entered for the defendants). The consent holding was not disturbed on remand.
Not every state follows either model. See State Privacy Laws and Website Tracking, and, for which state's rule applies to a given visit, Visitor Location in Website Wiretap Claims.
Who has to prove consent?
The party relying on consent bears the burden of showing it. A federal court in Illinois wrote in June 2026 that "consent under the Wiretap Act is an affirmative defense, and a plaintiff need not anticipate or refute potential affirmative defenses in his complaint." Baker v. Index Exchange, Inc., No. 25 C 10517, ECF No. 75, at 9 (N.D. Ill. June 16, 2026).
In practice the defendant has to show what the visitor saw and chose, when, and how the site's tags responded. Records the site holds, such as consent logs and tag manager versions, are usually the best evidence on either side; Checking a Case File Against Your Tag Manager explains how to read them against the record of a visit.
Does a party's consent end the case?
No. Section 2511(2)(d) withdraws the exception when the communication is intercepted for the purpose of committing a criminal or tortious act, so consent moves the question to purpose rather than ending it. The same Illinois court put it this way: "Even when consent is uncontested, as it is here, dismissal is inappropriate without considering whether Baker has plausibly pleaded that the crime/tort exception applies." Baker, ECF No. 75, at 10.
For a vendor that relies on the operator's consent, and for an operator that is itself a party, the analysis then turns to what the interception was for. The Wiretap Act's Crime-Tort Exception collects the decisions on that question, including where courts divide.
Does a cookie banner or privacy policy supply the visitor's consent?
Only to the extent it shows the visitor's actual consent before the interception; whether a banner or policy did that is a question about what the visitor saw, chose and was told. The line Pharmatrak draws between actual and constructive consent applies here.
A refusal points the other way. In reviving California privacy claims against an advertising company that had overridden browsers' cookie blockers, the Third Circuit wrote that "users are entitled to deny consent, and they are entitled to rely on the public promises of the companies they deal with." In re Google Inc. Cookie Placement, 806 F.3d at 151. That passage addresses the state privacy claims; the federal claims in that case were dismissed.
For a site that shows a banner, the practical evidence is the banner's words, the choice the visitor made, the time of each request relative to that choice, and whether the site's tags were set to wait for it. The five-minute Reject button test shows how a site behaves today. For HIPAA covered entities, HHS's position on banners and authorizations is summarized in HIPAA, Pixels and AHA v. Becerra.
What should counsel collect on the party and consent questions?
Collect the record of where each request went, what the visitor saw and chose, the site's consent and tag settings on the visit date, and the vendor terms the operator accepted. In particular:
- Destinations. For each request, whether the browser sent it to the vendor's own domain or to a domain the site controls. The answer matters to the party question in the Third Circuit.
- The banner and the choice. Screenshots of the banner, the words of each choice, the choice made, and the time it was made.
- Configuration on the visit date. The tag manager version and consent platform settings live that day, and any server container that forwarded data.
- The operator's own documents. The privacy policy and terms in force on the visit date, and how they were presented.
- The vendor's terms. What the operator agreed to when it installed the vendor's code. Some vendors' terms speak directly to sensitive data. Section 1.h of the Meta Business Tools Terms, for example, reads: "You represent and warrant that you will not share Business Tool Data with us that ... (iv) includes or is based on, directly or otherwise, health information, financial information, consumer report information, or other categories of sensitive information." Terms like these bear more on purpose than on consent.
What sources does this guide rely on?
This guide relies on the statute text and court decisions listed here, quoted from the copies linked. Checked on November 10, 2026.
- 18 U.S.C. § 2511 (Legal Information Institute)
- California Penal Code § 631
- In re Facebook, Inc. Internet Tracking Litigation, 956 F.3d 589 (9th Cir. 2020), cert. denied sub nom. Facebook, Inc. v. Davis, No. 20-727 (U.S. Mar. 22, 2021)
- In re Google Inc. Cookie Placement Consumer Privacy Litigation, 806 F.3d 125 (3d Cir. 2015)
- Cole v. Quest Diagnostics, Inc., No. 25-1449 (3d Cir. Nov. 13, 2025) (not precedential)
- In re Pharmatrak, Inc., 329 F.3d 9 (1st Cir. 2003), on remand, summary judgment granted, 292 F. Supp. 2d 263 (D. Mass. 2003) (interception not intentional)
- Javier v. Assurance IQ, LLC, No. 21-16351 (9th Cir. May 31, 2022) (unpublished mem.), on remand, 649 F. Supp. 3d 891 (N.D. Cal. 2023) (dismissing the Section 631(a) claim as time-barred, with leave to amend), and No. 20-cv-02860-CRB, 2023 WL 3933070 (N.D. Cal. June 9, 2023) (dismissing without leave to amend; judgment entered for the defendants)
- Baker v. Index Exchange, Inc., No. 25 C 10517, ECF No. 75 (N.D. Ill. June 16, 2026)
- Doe v. Baystate Health System, Inc., No. 1:25-cv-10337-JEK, ECF No. 42 (D. Mass. Mar. 19, 2026)
- Meta Business Tools Terms