Join our Newsletter — 33% off our NHI Course
Home› Guides› Tracking Pixel Litigation Guide: VPPA, CIPA Wiretap Claims…
Guide Privacy & Data Protection

Tracking Pixel Litigation Guide: VPPA, CIPA Wiretap Claims and Session Replay

PDF for newsletter subscribers · free to read online

← All guides
By NHI Mgmt Group, edited by Lalit Choda Updated 14 November 2026 14 min read
On this page

In the United States, a tracking pixel, chat widget or session replay script on a public website can be pleaded as illegal wiretapping or as an unlawful disclosure of video viewing history, with statutory damages counted per visitor. Large numbers of class actions have been filed under decades-old statutes: the federal Video Privacy Protection Act (VPPA) of 1988, the California Invasion of Privacy Act (CIPA), the federal Wiretap Act and similar state laws. The law moved quickly in 2025 and 2026: appeals courts narrowed what counts as identifying information and what injury is needed to sue, California removed private suits over online pen register claims, and the US Supreme Court heard argument on who counts as a VPPA consumer. This guide explains each theory, the elements and defences that decide cases, the current status of the key rulings, and the technical controls that privacy, security and marketing technology teams can put in place. It complements the Cookie and Tracking Technology Compliance Guide, which covers UK and EU consent rules.

Status as of 13 November 2026: Salazar v. Paramount Global (US Supreme Court No. 25-459) was argued on 14 October 2026 and is awaiting decision. Law firm reports (for example Nixon Peabody, 3 September 2026) say the legislature passed California SB 690; check its enactment status on the official legislature site. Check the sources below for later changes before relying on this page.

Key takeaways

  • Statutory damages drive the litigation. The VPPA provides liquidated damages of $2,500, CIPA section 637.2 allows $5,000 per violation, and the federal Wiretap Act allows the greater of $100 a day or $10,000, none of which requires proof of financial loss.
  • Video plus identifier is the VPPA risk. A page that plays video and sends the video title together with a user identifier to an advertising platform is the classic pleading; courts now split on whether the data must identify the viewer to an ordinary person.
  • Law firm summaries say section 631 wiretap claims are unaffected by SB 690. California removed private suits under the pen register section (638.51) for website and app conduct, but the interception claim under section 631 remains available to private plaintiffs.
  • Standing is now a real defence. The Ninth Circuit held in Popa v. Microsoft (2025) that session replay capturing ordinary browsing was not a concrete injury, so the content captured matters as much as the technology.
  • Prior consent and data minimisation are the controls. Load tags only after consent, keep video titles, chat text and form fields out of third-party requests, and document what every tag sends.
StatuteWhat plaintiffs allegeKey elementsDamages
Video Privacy Protection Act, 18 U.S.C. 2710A site that offers video disclosed a subscriber's viewing history to an advertising or analytics provider through a pixelDefendant is a video tape service provider; plaintiff is a consumer (renter, purchaser or subscriber); disclosure was knowing; information identifies a person as having requested or obtained specific video materialsActual damages but not less than $2,500 liquidated damages, plus punitive damages and fees
CIPA section 631(a), Cal. Penal CodeA third-party script read chat messages, searches or form entries in transit without all parties' consent, and the site operator aided itContents of a communication; read or learned while in transit; without consent of all parties; the third party is not merely the site's own toolCivil action under section 637.2: $5,000 per violation or three times actual damages, whichever is greater
CIPA section 638.51 (pen register)Tracking scripts captured addressing information such as IP address and device dataUse of a pen register or trap and trace device without a court order or user consentFor website and app conduct, private suits would be removed by SB 690 once in force (per law firm summaries); the Attorney General could still sue
Federal Wiretap Act, 18 U.S.C. 2511 and 2520Interception of communications by a third-party trackerInterception of contents; one-party consent defence in 2511(2)(d), lost if the interception is for a criminal or tortious purposeGreater of actual damages and profits or $100 a day or $10,000; two-year limitation period
Other state wiretap acts (for example Pennsylvania WESCA)Session replay or chat recording without all-party consentVaries by state; many require consent of all partiesVaries; standing limits still apply in federal court

VPPA: video, identifiers and who is a consumer

The VPPA defines a video tape service provider as anyone engaged in the business of rental, sale or delivery of prerecorded video cassette tapes or similar audiovisual materials, and courts have applied that to streaming and websites with embedded video. Personally identifiable information "includes information which identifies a person as having requested or obtained specific video materials or services". A provider may disclose with informed, written consent, which since the 2013 amendment can be given electronically, must be distinct and separate from other legal or financial terms, and can be given in advance for up to two years or until withdrawn.

Two questions now decide most cases

  • Is the plaintiff a consumer? Many plaintiffs are newsletter subscribers or account holders rather than paying video customers. The Sixth Circuit held in Salazar v. Paramount Global (3 April 2025) that "goods or services" means audiovisual goods or services, so a free newsletter subscription did not make the plaintiff a consumer, and acknowledged a circuit split. The Supreme Court granted review on 26 January 2026 on whether the phrase covers all of a provider's goods or services or only audiovisual ones, and heard argument on 14 October 2026. Until it rules, exposure depends on the circuit.
  • Is the data personally identifiable? The Second Circuit held in Solomon v. Flipps Media (1 May 2025) that a transmission of code containing a video URL and a social media user ID was not PII, because information qualifies only if it would readily permit an ordinary person to identify a specific individual's video-watching behaviour. That aligns the Second Circuit with the Third and Ninth Circuits; the First Circuit uses a broader reasonable foreseeability test. The Supreme Court denied review in Solomon on 8 December 2025.

The practical lesson is unchanged by either ruling: a page that plays video should not send the title or URL of the video together with any user identifier to a third party without VPPA-compliant consent.

CIPA and wiretap claims: chat, search and session replay

Section 631(a) of the California Penal Code covers anyone who taps or makes an unauthorised connection to a communication line, anyone who reads or attempts to learn the contents of a communication in transit without the consent of all parties, and anyone who aids, agrees with or employs another to do so. Plaintiffs plead that a chat, search or analytics vendor is an eavesdropping third party and the website operator aided it.

  • Contents versus record information: wiretap claims need the contents of a communication. Typed chat messages, search terms and form field values are the strongest facts for plaintiffs; page views and clicks are weaker.
  • The party exception: a website is a party to its own communications. Under the federal Act, one party's consent is enough unless the interception is for a criminal or tortious purpose, which plaintiffs try to plead by pointing to another law, for example disclosing health information. CIPA requires consent of all parties.
  • Third party or tool: courts ask whether the vendor merely records for the website, like a tape recorder, or can use the data for its own purposes. Contracts and configuration that prevent vendor reuse support the tool characterisation.
  • Timing of consent: consent must precede collection. A banner that tags fire before the visitor clicks does not supply consent for what was already captured.

SB 690 and the pen register wave

More recently plaintiffs added claims that tracking scripts were pen registers under section 638.51, which bars installing or using a pen register or trap and trace device except for listed service-provider purposes or with the user's consent. According to law firm summaries (Nixon Peabody, 3 September 2026), SB 690, passed by the California legislature, amends section 637.2 so that actions under section 638.51 arising from conduct on a website, online application or mobile application can be brought only by the Attorney General, and reportedly provides a defence for pending suits filed within the stated look-back period. Earlier drafts that would have exempted any "commercial business purpose" from sections 631 and 632 were dropped, so interception claims continue.

Session replay and standing

Session replay scripts record mouse movements, clicks, scrolling and keystrokes to recreate a visit. In Popa v. Microsoft (9th Cir., 26 August 2025) the plaintiff alleged that a pet supply retailer's session replay tool captured her browsing. Applying TransUnion v. Ramirez, the court held that she had not alleged a concrete injury: the data captured was not embarrassing, invasive or otherwise private, and a privacy statute alone does not make a harm concrete. The case was dismissed for lack of Article III standing.

Popa does not make session replay safe. Its reasoning turns on what was captured. Replay that records health searches, financial details, chat content or form fields without masking supplies exactly the private information the court found missing, and state courts are not bound by Article III.

Risk by page and tag type

Page or featureTypical tagMain theoryRisk driversControl
Video pages for logged-in or subscribed usersAdvertising pixel with video URLVPPATitle in URL or event, user ID or hashed email sent togetherSeparate VPPA consent, strip title from third-party events, server-side tagging with field allow-lists
Live chat and chatbotsThird-party chat or AI assistant scriptCIPA 631, state wiretapVendor stores and reuses transcripts; no notice before typingNotice and consent before the first message; contract limiting vendor use
Search boxes and formsAnalytics or ad pixels capturing query strings and form valuesCIPA 631, Wiretap ActSearch terms or form values in URLs and eventsRemove query strings and form values from tags; POST forms
Whole-site session replayReplay scriptState wiretap, intrusion upon seclusionKeystroke capture, unmasked fields, sensitive pagesMask all inputs by default; exclude sensitive pages; consent before loading
Health, finance and other sensitive pagesAny third-party tagWiretap crime-tort exception, state health privacy lawsConditions, appointments, account detailsNo third-party tags on authenticated or sensitive pages

For health sites see the Health Data Privacy Beyond HIPAA Guide, and for script supply chain risk the Client-Side Security Guide.

How to implement: a phased approach

  1. Inventory every tag and what it sends: crawl the site with a consent-rejected and a consent-accepted browser profile, record every third-party request and its payload (URL, query string, event parameters, identifiers), and map each to an owner and purpose. See the Data Mapping and ROPA Guide.
  2. Classify pages: mark video pages, chat, search, forms, authenticated areas and sensitive content. These are the pages the theories above target.
  3. Block before consent: configure the consent platform and tag manager so non-essential tags do not load until the visitor opts in, and test with the rejected profile that nothing fires. See the Consent Management Guide.
  4. Minimise payloads: remove video titles, search terms and form values from third-party events; turn off automatic form and URL capture in pixels; mask all inputs in session replay. See the Google Tag Manager Security Guide.
  5. Add specific notices: a chat notice before the first message, a VPPA consent that is separate from general terms, and a privacy notice that names the categories of tracking.
  6. Fix contracts: require vendors to act only on your instructions, prohibit reuse of captured data, and require deletion on termination.
  7. Test, monitor and roll back: stage tag changes, re-run the crawl after every release, and keep the previous tag container version ready to republish if a change leaks data.

Decision guidance

  • Remove or restrict: if a tag's business value on a sensitive or video page is marginal, remove it from that page. Litigation exposure scales with visitors, not with the tag's value.
  • Client-side or server-side tagging: server-side tagging lets you allow-list fields before data leaves your infrastructure, but it is still a disclosure; it reduces content leakage, not the need for consent.
  • Arbitration and terms: click-through terms with arbitration clauses can limit class actions but require assent and do not cover anonymous visitors; mass arbitration is its own cost.
  • Small organisations: start with the tag inventory, consent blocking and removal of tags from chat, search and sensitive pages; these remove most exposure without new tooling.
  • Large organisations: add a tag governance board, release gates on the tag manager and continuous monitoring of third-party requests.

Where identity fits

Pixel claims depend on identifiers. A hashed email, advertising ID, logged-in user ID or social media cookie is what turns a page view into a disclosure about a person. Keep customer identity attributes out of marketing tags by default, and treat the tag manager and advertising platform credentials as privileged non-human access, because whoever can publish a container can change what leaves the site. See the Identity Data Privacy and Consent Guide.

Detection, evidence and metrics

  • Pre-consent requests: number of third-party requests fired with consent rejected (target zero).
  • Sensitive payloads: count of third-party requests containing video titles, search terms, form values or email hashes, from automated crawls.
  • Tag inventory coverage: percentage of tags with a named owner, purpose and contract.
  • Replay masking: share of session replay projects with input masking on and sensitive pages excluded.
  • Change control: tag container versions published without review.

Keep dated crawl results, consent configuration exports and tag container versions. In litigation these are the evidence of what the site did on a given date.

Common failure patterns

  • Consent banner without blocking: tags load on page view and the banner only records a choice afterwards.
  • Video title in the URL: the page URL sent by every pixel already contains the film or episode name.
  • Chat vendor with reuse rights: the contract lets the vendor train or improve services on transcripts, supporting the third-party characterisation.
  • Replay with keystroke capture: default settings record unmasked fields on checkout or account pages.
  • Marketing publishes without review: a new pixel added through the tag manager reaches production without privacy or security sign-off.

Framework mapping

ControlPrivacy outcomeNIST SP 800-53 Rev 5ISO/IEC 27001:2022 Annex A
Tag inventory and data flow mappingData processing is inventoriedPM-5(1) Inventory of Personally Identifiable InformationA.5.9, A.5.34
Consent before collectionIndividuals' preferences are honouredPT-4 ConsentA.5.34
Payload minimisation and maskingData is minimisedSA-8(33) MinimizationA.8.11 Data masking
Vendor contractsThird parties are managedSA-9 External System ServicesA.5.19, A.5.20
Tag change controlChanges are managedCM-3 Configuration Change ControlA.8.32

Practitioner checklist

  • Crawl the site with consent rejected and confirm no third-party tag fires.
  • List every page that plays video and confirm no title plus identifier reaches a third party without VPPA consent.
  • Show a chat notice before the first message and restrict vendor reuse of transcripts by contract.
  • Strip search terms and form values from all third-party requests.
  • Mask all inputs in session replay and exclude sensitive and authenticated pages.
  • Remove third-party tags from health, finance and account pages.
  • Gate tag manager publishing behind privacy and security review.
  • Keep dated evidence of tag configuration and consent settings.
  • Track Salazar v. Paramount Global and SB 690 implementation with counsel.

Standards and references

Related NHI Mgmt Group resources: Cookie and Tracking Technology Compliance Guide · Email Tracking Pixels Guide · CCPA and CPRA · Consent Management Guide. This guide summarises US tracking pixel and wiretap litigation theories and is not legal advice.

PDF for subscribers

Take this guide with you

Every section, table and checklist in one PDF, with links to the sources and related guides. Subscribe to our weekly NHI & AI Identity Journal and we’ll email you a download link.

Free weekly newsletter

Subscribe to the NHI & AI Identity Journal

The latest on NHI and Agentic AI security – articles, research, breaches, news and events every week.

Bonus 33% off our NHI Course when you subscribe.

NHIMG Editorial Note
Researched and written by the NHI Mgmt Group editorial team using AI tools, under the editorial direction of Lalit Choda. Facts are drawn from the sources listed on this page and checked by our automated quality process. Last updated 14 November 2026. Spotted an error? Use our contact page.
NHI Mgmt Group, the independent authority on Non-Human Identity, IAM and Agentic AI security. nhimg.org

PDF Downloads for Newsletter Subscribers

Get the guide

Enter your details and we’ll email you a download link.

The full guide is free to read online. The PDF is a thank you for subscribing.

Fill in all fields marked * and tick the PDF box to continue.