Executive Summary
California Invasion of Privacy Act (CIPA) litigation has emerged as one of the most active and financially significant fronts in privacy class action practice. Driven by the proliferation of third-party tracking technologies embedded across commercial websites, CIPA § 631 and § 632.7 claims have created a robust and expanding docket of cases targeting some of the largest enterprises in the United States.
Key takeaway for plaintiff attorneys: The Ninth Circuit's 2025 ruling in Mikulsky v. Bloomingdale's LLC revived session replay CIPA claims on an aiding-and-abetting theory, while Torres v. Prudential Financial, Inc. clarified the limits of the "in transit" requirement. Meanwhile, SB 690 — the bill that would have carved out "commercial business purpose" from CIPA liability — stalled in the California Assembly and is now a two-year bill with uncertain prospects. The window for filing remains open, but the legislative landscape bears close monitoring.
This analysis examines the current state of CIPA litigation, identifies the strongest filing strategies, evaluates motion-to-dismiss risks with reference to specific recent holdings, and provides a forward-looking assessment of where this practice area is heading.
Definition
CIPA § 631 Definition
The California Invasion of Privacy Act (CIPA), California Penal Code § 631, prohibits the intentional wiretapping, eavesdropping upon, or recording of confidential communications without the consent of all parties. In digital privacy litigation, CIPA § 631 is applied to third-party website tracking technologies — such as pixels, session replay tools, and advertising scripts — that intercept user communications and transmit them to third parties. Violations carry statutory damages of $5,000 per violation under § 637.2, injunctive relief, and attorney's fees.
Legal Background: CIPA § 631 and the Wiretap Framework
Key InsightCIPA liability requires a third-party interception — the website operator's own data collection is not actionable. The winning theory frames the operator as aiding a third party's independent wiretap.
CIPA § 631 prohibits the intentional wiretapping or eavesdropping on confidential communications. Originally enacted in 1967 to address telephonic surveillance, the statute has been successfully adapted by plaintiff attorneys to challenge the deployment of third-party tracking technologies on websites — arguing that these tools intercept visitor communications in real time and transmit them to third parties without adequate consent.
The critical statutory element for plaintiff strategy is the third-party interception requirement. CIPA does not prohibit a website operator from collecting its own visitor data. Rather, it targets scenarios where a third party — such as Meta, Google, a session replay vendor, or an advertising network — receives the communication contemporaneously with its transmission. This distinction is what makes the presence of third-party JavaScript tags, pixels, and SDKs on defendant websites the factual foundation of nearly every CIPA digital privacy claim.
Section 632.7, which addresses the interception of cellular and cordless telephone communications, has also seen increased application in the context of voice assistant and chatbot interactions on mobile devices. Additionally, sections 638.50–638.51 — the pen register and trap-and-trace provisions — represent a newer litigation theory alleging that certain tracking tools capture routing or signaling information. Courts remain divided on this theory, but several complaints filed in late 2025 included pen register claims alongside traditional § 631 allegations.
Violations of CIPA carry statutory damages of $5,000 per violation under § 637.2, injunctive relief, and reasonable attorney's fees. In a class context, the per-violation calculation can generate aggregate exposure in the hundreds of millions of dollars — a damages framework that has made CIPA one of the most economically significant privacy statutes for plaintiff-side litigation.
Litigation Trends: The 2025–2026 Landscape
Key InsightMikulsky v. Bloomingdale's (9th Cir. 2025) revived session replay claims on an aiding-and-abetting theory. Torres v. Prudential (N.D. Cal. 2025) established limits: data must be readable in transit, not just after storage.
CIPA filings accelerated significantly through 2025 and into early 2026. Hundreds of cases have been filed over the past three years, and the pace shows no sign of slowing.
The Meta Pixel litigation wave established a viable and replicable claim template. Dozens of cases filed against healthcare providers, financial institutions, and e-commerce platforms alleged that the Meta Pixel transmitted sensitive browsing data — including page URLs indicating health conditions, financial activity, and purchase history — to Meta without user consent. Several of these cases produced eight-figure settlements, signaling to the plaintiff bar that CIPA claims carry meaningful economic value.
The session replay and keystroke logging theory has matured into a distinct sub-practice. The Ninth Circuit's July 2025 ruling in Mikulsky v. Bloomingdale's LLC was a watershed: the court reversed the district court's dismissal and held that the complaint stated sufficient facts to allege that Bloomingdale's aided and conspired with session replay code providers to intercept communications in violation of § 631(a). The court specifically found that the plaintiff alleged real-time capture of the contents of communications — not merely information about the characteristics of those communications. Companies deploying tools like FullStory, Hotjar, Microsoft Clarity, and Mouseflow now face heightened CIPA exposure.
However, the landscape is not uniformly favorable. In Torres v. Prudential Financial, Inc. (N.D. Cal., April 2025), the court granted summary judgment for defendants on a session replay claim, holding that the data captured by ActiveProspect's software did not become readable content until after storage and reassembly — failing the "in transit" requirement of § 631. And in Thomas v. Papa John's International Inc., the Ninth Circuit affirmed dismissal, ruling that Papa John's, as a party to the communications, could not be liable for eavesdropping on its own conversation — underscoring the importance of properly pleading the aiding-and-abetting theory rather than a direct liability claim.
Settlement economics remain favorable for plaintiffs. Defendants face statutory damages of $5,000 per violation under § 637.2, and the per-violation calculation in a class context has driven pre-certification settlements in the $5M–$50M range. The volume of pre-litigation demand letters — many of which resolve before filing — suggests the total economic impact of CIPA claims significantly exceeds what is visible on public dockets.
Plaintiff Strategy: Building Strong CIPA Section 631 Claims
The strongest CIPA § 631 class action claims share four characteristics that plaintiff firms should prioritize during case evaluation and selection.
Identifiable Third-Party Recipients
Claims are strongest where the intercepting third party is clearly identifiable — Meta, Google, TikTok, a named session replay vendor — and the data flow can be technically demonstrated. After Thomas v. Papa John's, it is critical to frame the claim as aiding-and-abetting (the website operator aiding a third party's interception) rather than direct wiretapping by the website operator itself.
Sensitivity of Intercepted Data
While CIPA does not require the communication to be sensitive, claims involving health-related browsing (hospital and telehealth sites), financial data (banking portals, insurance applications), and employment information consistently produce stronger settlement outcomes. Targeting defendants in healthcare, financial services, and insurance creates favorable factual profiles.
Technical Evidence as a Differentiator
Firms that invest in forensic analysis of defendant websites — network traffic captures showing HTTP requests to third-party domains, JavaScript source analysis revealing data collection scope, and cookie/local storage analysis — develop stronger evidentiary foundations than those relying solely on privacy policies and cookie disclosures.
Anticipate Consent Defenses at Filing
Defendants consistently argue that visitors consented through cookie banners, privacy policies, or terms of service. The strongest plaintiff position identifies specific deficiencies: banners that appear after tracking has already initiated, opt-out mechanisms that fail to disable third-party scripts, and privacy policies that do not specifically disclose the third-party interception at issue. Post-Mikulsky, the argument that a vendor's "masking" of text fields prevents interception has been substantially weakened.
Motion-to-Dismiss Risks and Defense Strategies
Key InsightPlead aiding-and-abetting, not direct liability. File in California state court to avoid Article III standing disputes. Evaluate arbitration clauses during case selection.
Plaintiff firms should anticipate several recurring defense arguments at the motion-to-dismiss stage.
Standing remains contested in federal court. While the Ninth Circuit has moved toward recognizing CIPA violations as concrete injuries sufficient for Article III standing, defendants continue to argue that mere data collection without downstream harm is insufficient. The Supreme Court's evolving standing jurisprudence following TransUnion v. Ramirez continues to create uncertainty in the federal forum. State court filings avoid this issue entirely and remain the preferred venue for most CIPA claims.
The party exception is the most significant substantive defense. CIPA § 631(a) contains an exception for parties to the communication. Thomas v. Papa John's established clearly that a website operator, as a party to the communication, cannot be directly liable for eavesdropping. The winning plaintiff theory — confirmed by Mikulsky v. Bloomingdale's — is the aiding-and-abetting theory: the operator aided a distinct third party's independent interception. Complaints must be pleaded accordingly.
The "in transit" requirement presents a technical defense. Torres v. Prudential demonstrates that defendants can win on the argument that session replay data is not "read" in transit but only becomes readable after storage and reassembly. Plaintiff firms must develop evidence showing that the third-party tool reads or accesses communication contents during transmission, not merely after the fact.
Arbitration clauses in website terms of service present a practical risk. Defendants increasingly move to compel arbitration based on browsable terms or clickwrap agreements. A successful arbitration motion effectively defeats class treatment. Firms should evaluate the enforceability of the defendant's arbitration clause during case selection, and consider whether mass arbitration (see our analysis of mass arbitration versus class actions in privacy cases) may be an alternative strategy where class treatment is unavailable.
Evidence Considerations: What Matters Most
Key InsightCollect network traffic evidence before filing. Defendants frequently modify tracking implementations after litigation is initiated. Pre-filing forensic analysis is a practical necessity.
CIPA litigation is fundamentally a technical-evidence practice. The factual core of every case is the demonstration that a specific third-party technology intercepted a specific category of user data and transmitted it to a third-party server.
Network traffic captures showing HTTP requests from the defendant's website to third-party domains — with payload data visible — are the gold standard. These captures should be collected under controlled conditions, documented with timestamps and methodology, and replicated across multiple sessions to demonstrate consistency. After Torres v. Prudential, firms should specifically document evidence of real-time data reading during transmission, not merely post-transmission storage.
JavaScript source analysis of tracking scripts deployed on defendant websites can reveal the specific data fields collected, the triggering events, and the destinations of transmitted data. Many session replay vendors — FullStory, Hotjar, Microsoft Clarity, Mouseflow — have well-documented data collection practices that can be corroborated through their own technical documentation and marketing materials.
Cookie and local storage analysis supplements network traffic evidence by demonstrating the persistence of tracking across sessions and the identifiers used to link user activity to third-party profiles.
Critically, evidence should be collected before filing when possible. Defendants frequently modify their tracking implementations after litigation is initiated. Pre-filing forensic analysis is both a strategic advantage and a practical necessity for building the strongest possible evidentiary record.
Filing and Venue Strategy
California state courts remain the preferred venue for CIPA claims. State court filings avoid Article III standing challenges, benefit from California's generally plaintiff-favorable procedural rules, and access a judiciary familiar with the statutory framework.
Within California, Los Angeles and San Francisco superior courts have developed the most substantial CIPA dockets, and judicial familiarity with the tracking-as-wiretapping theory reduces the risk of adverse rulings based on unfamiliarity with the underlying technology.
Federal court filings may be appropriate where the plaintiff firm seeks to consolidate related claims or where diversity jurisdiction offers strategic advantages, but the standing risk should be carefully weighed. After Augustine v. Great Wolf Resorts, Inc. (S.D. Cal. 2024) — where the court held that keystrokes and mouse clicks do not constitute protected communications — firms filing in federal court should be prepared to distinguish their factual allegations from the Augustine holding.
Multi-defendant strategies — filing against both the website operator and the third-party tracking vendor — have gained traction and can create additional settlement leverage by dividing defense interests. The FullStory and ActiveProspect litigation demonstrates that naming the vendor as a co-defendant forces the vendor to defend its own product, often creating divergent defense strategies that benefit the plaintiff class.
Legislative Risk: SB 690 and CIPA Reform
The most significant non-litigation risk to CIPA privacy claims is legislative reform. SB 690, introduced in the California Senate in 2025, would have introduced a "commercial business purpose" carve-out that would substantially narrow CIPA's application to website tracking. The bill passed the California Senate unanimously but stalled in the Assembly and is now a two-year bill with potential review in 2026.
If enacted as drafted, SB 690 would exempt from CIPA liability personal information processed for common commercial purposes — potentially immunizing the exact tracking practices that current CIPA litigation targets. Plaintiff firms with active CIPA practices should monitor this bill closely, as its passage could materially affect both pending and future claims.
The stalling of SB 690 is itself a strategic data point: the bill's failure to advance suggests that the California legislature has not yet reached consensus on narrowing CIPA protections. For plaintiff firms, this extends the window of opportunity for filing under the current statutory framework.
Future Outlook: Where CIPA Litigation Is Heading
Several trends suggest that CIPA litigation will continue to expand and evolve through 2026 and beyond.
AI-powered chatbots and conversational interfaces are creating new interception surfaces. As companies deploy AI assistants on their websites — many powered by third-party LLM providers — the transmission of user inputs to third-party AI servers may give rise to a new generation of CIPA claims. The Ninth Circuit has already indicated receptiveness to applying CIPA to modern tracking technologies, and the chatbot theory extends that logic to conversational AI.
Cross-statute claims combining CIPA with the Video Privacy Protection Act (VPPA), the Computer Fraud and Abuse Act (CFAA), and state consumer protection statutes are becoming more common. For analysis of the VPPA landscape, see our coverage of VPPA claims against streaming platforms. Multi-count complaints increase settlement leverage and reduce the risk of complete dismissal on any single theory.
Regulatory enforcement by the California Attorney General's office, while separate from private litigation, creates additional pressure on defendants to modify their tracking practices — generating evidence of prior non-compliance that plaintiff firms can leverage in existing cases.
The pen register and trap-and-trace theory under CIPA §§ 638.50–638.51 remains an open frontier. While courts are divided, several 2025 complaints successfully included pen register claims alongside traditional § 631 allegations, and no appellate court has definitively foreclosed this theory.
The Koladin Perspective: Technology-Driven Detection at Scale
The scale of CIPA litigation opportunity is directly proportional to the scale of third-party tracking deployment across the commercial internet. Millions of websites deploy the scripts and pixels that give rise to CIPA claims, but identifying which deployments present the strongest combination of clear interception, sensitive data, weak consent mechanisms, and meaningful financial exposure requires systematic analysis that exceeds the capacity of manual review.
Koladin's detection infrastructure continuously analyzes website tracking deployments, consent mechanism implementations, and third-party data flows across industries and jurisdictions — identifying patterns of non-compliance that are not visible to attorneys reviewing individual websites. This includes widespread deployments of specific session replay tools with known interception characteristics, consent banner implementations that fail to prevent pre-consent data transmission, and industry-specific concentrations of vulnerable targets in healthcare, financial services, and insurance.
For plaintiff firms with established or emerging CIPA practices, systematic, technology-driven case detection represents a structural advantage: the ability to identify and evaluate litigation opportunities at scale, prioritize the highest-value matters, and move to filing with a stronger evidentiary foundation than traditional case origination methods provide.
Conclusion
CIPA litigation occupies a unique position in the privacy class action landscape: a mature statutory framework, favorable damages provisions, an expanding definition of protected communications, and a virtually unlimited supply of potential defendants deploying third-party tracking technologies. For plaintiff firms with the technical sophistication to prosecute these cases effectively, CIPA remains one of the most consistent and economically significant practice areas in contemporary class action work.
The firms that will capture the greatest value in this space are those that combine legal expertise with technological capability — identifying vulnerable tracking deployments at scale, building strong technical evidence before filing, properly pleading the aiding-and-abetting theory established by Mikulsky v. Bloomingdale's, and anticipating the defense strategies that Torres v. Prudential and Thomas v. Papa John's have made more predictable.
CIPA vs. Federal Wiretap Act: Comparison for Plaintiff Attorneys
Understanding the differences between California's CIPA and the federal Wiretap Act is critical for jurisdictional and claim strategy decisions.
| Factor | CIPA (Cal. Penal Code § 631) | Federal Wiretap Act (18 U.S.C. § 2511) |
|---|---|---|
| Statutory Damages | $5,000 per violation (§ 637.2) | Statutory damages or actual damages, whichever is greater |
| Intent Standard | Lower — no specific intent requirement for aiding-and-abetting claims | Requires intentional interception |
| Private Right of Action | Yes (§ 637.2) | Yes (18 U.S.C. § 2520) |
| Application to Digital Tracking | Broad — California courts have applied CIPA to pixels, session replay, chatbots | Narrower — federal courts more cautious about applying to website tracking |
| Party Exception | Yes — website operators as parties cannot be directly liable (Thomas v. Papa John's) | Yes — one-party consent exception under § 2511(2)(d) |
| Class Certification | Favorable in California state courts for tracking claims | More challenging due to standing and individualized consent issues |
| Preferred Venue | California state court (avoids Article III standing) | Federal court required for federal claims |
| Statute of Limitations | 1 year (CCP § 340(a)) with discovery rule | 2 years from date of violation or discovery (§ 2520(e)) |
Frequently Asked Questions
What is the statute of limitations for CIPA § 631 claims?
CIPA claims are subject to a one-year statute of limitations under California Code of Civil Procedure § 340(a). However, courts have applied the discovery rule in certain digital privacy contexts, potentially extending the filing window where the interception was not reasonably discoverable by the plaintiff.
Can CIPA claims be brought as class actions?
Yes. CIPA § 637.2 provides a private right of action with statutory damages of $5,000 per violation. Courts have certified classes in CIPA tracking cases where common questions — such as the deployment of a specific third-party script across all website visitors — predominate over individual issues.
What damages are available under CIPA?
CIPA § 637.2 provides statutory damages of $5,000 per violation, injunctive relief, and reasonable attorney's fees. In a class context, the per-violation calculation can produce exposure in the hundreds of millions of dollars, which drives significant settlement leverage.
What is the party exception defense under CIPA § 631?
CIPA § 631(a) contains an exception for parties to a communication. As the Ninth Circuit confirmed in Thomas v. Papa John's, a website operator that is a party to the communication cannot be directly liable for eavesdropping on it. The prevailing plaintiff theory is aiding-and-abetting: the operator aided a distinct third party's independent interception of the communication.
Does CIPA apply to session replay software?
Courts are split but the trend favors plaintiffs. In Mikulsky v. Bloomingdale's (9th Cir. 2025), the Ninth Circuit reversed dismissal and found sufficient allegations that session replay code captured the real-time contents of communications. However, in Torres v. Prudential (N.D. Cal. 2025), the court granted summary judgment where the data was not readable until after storage. The key factual question is whether the tool reads data in transit.
Can CIPA claims survive a motion to dismiss?
Yes, when properly pleaded. Post-Mikulsky, claims alleging that a website operator aided a third party's real-time interception of communication contents have survived motions to dismiss. Claims are most vulnerable when they allege direct liability by the website operator (foreclosed by Thomas) or fail to demonstrate that data was read in transit (as in Torres).
Does CIPA apply to AI chatbots on websites?
This is an emerging theory with significant potential. Where a website deploys a chatbot powered by a third-party AI provider, user inputs transmitted to the third party's servers may constitute interceptions under § 631. No appellate court has ruled on this theory, but the Ninth Circuit's willingness to apply CIPA to modern tracking technologies suggests receptiveness.
How does CIPA differ from the federal Wiretap Act?
CIPA provides broader protections. Unlike the federal Wiretap Act, CIPA does not require the same level of intentionality, California courts have been more receptive to applying wiretap concepts to digital tracking, and CIPA's $5,000 statutory damages provision provides a more favorable economic framework for class litigation than the federal statute.
What is SB 690 and how could it affect CIPA litigation?
SB 690 is a California bill that would introduce a 'commercial business purpose' exemption to CIPA, potentially immunizing common website tracking practices. The bill passed the Senate unanimously in 2025 but stalled in the Assembly. It is now a two-year bill that may be reviewed in 2026. If enacted, it could substantially narrow the scope of CIPA privacy claims.
What evidence is needed for a CIPA wiretapping claim?
The strongest evidence includes network traffic captures showing HTTP requests to third-party domains with payload data, JavaScript source analysis of tracking scripts, and cookie/storage analysis. Evidence should be collected before filing when possible, as defendants frequently modify tracking implementations after litigation begins. Pre-filing forensic analysis is both a strategic advantage and practical necessity.
Related Search Topics
Detect violations at scale
Koladin's detection engine identifies CIPA, ADA, VPPA, and other privacy violations across thousands of websites. Request a complimentary intelligence brief.
Request Case Intelligence →Get articles like this in your inbox
Litigation intelligence and case detection insights for plaintiff attorneys and funders. One email per week.
Continue Reading
ADA Website Accessibility Lawsuits: What Plaintiff Firms Should Know in 2026
Accessibility Litigation • 11 min read
Tracking After Opt-Out: An Emerging Privacy Litigation Theory
Privacy Litigation • 10 min read
VPPA Claims Against Streaming Platforms: Litigation Update
Privacy Litigation • 11 min read
Disclaimer: This article is provided for informational and analytical purposes only and does not constitute legal advice. The content reflects the views of Koladin's research team and should not be relied upon as a substitute for consultation with qualified legal counsel.