Session Replay Lawsuits: When Watching the Visitor Becomes a Wiretap
Updated 2026-06-29 · 5 cases cited · 6 outbound resources
Session replay tools — FullStory, Hotjar, Microsoft Clarity, Quantum Metric, LogRocket, Smartlook — capture every mouse movement, keystroke, scroll, and form input a visitor makes, then play them back like a video. Plaintiffs argue this is a wiretap, and outcomes depend on the specific collection, consent, and parties’ roles.
TL;DR
- —Javier v. Assurance IQ is an unpublished 2022 memorandum on consent timing in a session-replay dispute, not binding precedent except as Ninth Circuit rules allow.
- —FullStory, Hotjar, Microsoft Clarity, and Quantum Metric are named in hundreds of CIPA complaints.
- —Form-field capture (keystrokes typed into checkout or signup forms) is the highest-risk feature.
- —Disabling 'capture all' and excluding sensitive selectors does not, by itself, satisfy CIPA's consent requirement.
Got a demand letter? Start by checking your Shopify or ecommerce page after Reject All. For checkout testing and help fixing consent and pixel issues, explore got pixels?.
What session replay actually captures
Session replay vendors inject a JavaScript agent that observes the DOM and the user's input events. The agent transmits a stream of DOM mutations, mouse positions, click coordinates, keystrokes, and (depending on configuration) form-field values to the vendor's servers, where they are reassembled into a playable video.
The default configuration for most vendors captures everything except fields explicitly marked as sensitive. Even when sensitive fields are masked, the surrounding context — page URLs, error messages, dropdown selections — is captured, which is often enough to identify a user and their actions.
Why courts treat this as a wiretap
Session replay sits squarely in CIPA § 631(a)(2)'s prohibition on reading the contents of a communication in transit. Unlike a pixel that fires on discrete events, session replay continuously intercepts the entire interaction. The interception is happening in real time, on a third-party domain, with no participation from the visitor.
Javier v. Assurance IQ (9th Cir. 2022) is an unpublished memorandum that reversed dismissal based on retroactive consent and left prior implied consent and other issues unresolved. It is not precedent except as Ninth Circuit Rule 36-3 allows. Claims may also invoke the federal Wiretap Act and state analogues such as WESCA, whose elements require separate review; our guide to the statutes behind pixel litigation covers how each one treats session replay.
The form-field capture problem
The single highest-risk session-replay configuration is capturing keystrokes as they are typed into form fields. Plaintiffs argue (and courts often accept) that a partially-typed but unsubmitted message is still 'in transit' and is a communication that the user did not consent to share.
Several vendors now offer 'opt-in only' modes that disable input capture by default; using these modes is a meaningful risk reduction step but does not eliminate exposure without proper consent gating.
Got a demand letter? Start by checking your Shopify or ecommerce page after Reject All. For checkout testing and help fixing consent and pixel issues, explore got pixels?.
Vendor-specific exposure
FullStory and Quantum Metric are the most expensive enterprise tools and are usually deployed with comprehensive capture. Hotjar is the most widely deployed mid-market tool; complaints often name Hotjar customers as a category. Microsoft Clarity is free and ubiquitous on SMB sites, which has produced a long tail of small-dollar cases. LogRocket is the standard tool for SaaS apps and has been named in several B2B cases.
The vendor's own privacy posture matters: vendors with strict 'controller, not processor' clauses in their DPAs are easier to add as co-defendants.
How to reduce exposure
1. Gate the session-replay agent behind opt-in consent — do not load it before the user opts in. 2. Disable input/keystroke capture by default. 3. Mask all form fields, not just the obvious ones (a 'comments' field can capture PII too). 4. Set short retention windows (30 days is a defensible default). 5. Sign a DPA that designates the vendor as a processor, not a controller. 6. Audit which pages run the agent — checkout, account, and medical pages should be excluded entirely.
Key cases
Javier v. Assurance IQ, LLC
9th Cir. 2022, No. 21-16351Reversed dismissal based on retroactive consent in a session-replay case. The memorandum interpreted § 631 to require prior consent, left prior implied consent and other issues unresolved, and is not precedent except as Ninth Circuit Rule 36-3 allows.
Read sourceYoon v. Lululemon Athletica, Inc.
C.D. Cal. 2023, 549 F. Supp. 3d 1073Allowed CIPA claim against Lululemon's use of Quantum Metric to proceed. Rejected the argument that the vendor was a 'tool' rather than a third party.
Saleh v. Nike, Inc.
C.D. Cal. 2023, No. 22-cv-08989Combined session-replay and chatbot claims; survived motion to dismiss on the session-replay theory under Javier.
Williams v. What If Holdings, LLC
N.D. Cal. 2022, No. 22-cv-03780Early post-Javier application; sustained CIPA claim against a site running ActiveProspect's session-replay tool.
Garcia v. Yeti Coolers, LLC
C.D. Cal. 2024Representative e-commerce session-replay case alleging FullStory captured checkout-flow interactions including form inputs.
FAQ
Is Microsoft Clarity safer because it's free?
No. Microsoft Clarity is subject to the same CIPA analysis as paid vendors. Several complaints have named Clarity-using sites specifically because it is so widely deployed without consent gating.
What if we mask all PII fields?
Masking reduces but does not eliminate exposure. Courts have held that the interception itself — not just the captured content — is the violation. Consent is still required.
Can we use session replay for product analytics only?
Internal-use justifications do not change the CIPA analysis. The visitor's consent (not the operator's purpose) is what determines liability.
Are heatmap-only tools safer than full replay?
Marginally. Heatmaps still capture mouse position and click data, which courts have generally treated as a communication's contents. Consent is still the bright-line requirement.
Further reading
- Javier v. Assurance IQ (9th Cir. opinion) — U.S. Court of Appeals for the Ninth Circuit
- EFF on session-replay scripts — Electronic Frontier Foundation
- Princeton session-replay research — Princeton CITP
- Session-replay CIPA litigation overview — Husch Blackwell
- Wiretap-based privacy lawsuits — IAPP
- Cal. Penal Code § 631 — California Legislative Information
Related reading
Understand the tracking behind your demand letter
Start with a free Reject All scan of your Shopify or ecommerce page. Enter your email to unlock detailed findings and reports for your team and lawyer. got pixels? goes deeper into checkout and other journeys, helps with remediation, and lets you retest changes. A scan cannot confirm or dismiss a legal claim.
This article is general information about California Invasion of Privacy Act litigation, not legal advice. Case citations are drawn from public dockets and law-firm commentaries; verify before relying on them. Consult qualified counsel for advice on your specific situation.