privacysecurity

California Just Changed the Rules on App Tracking Lawsuits

California's SB 690 removes the private right to sue under CIPA's tracking provisions. What it changes, what survives, and what it means for your app privacy.

On September 30, 2026, California Governor Gavin Newsom signed Senate Bill 690 into law. The bill makes a significant change to how California’s Invasion of Privacy Act — CIPA — can be enforced when apps and websites collect tracking data from users.

The short version: individuals can no longer file private civil lawsuits against companies for one category of CIPA violations involving website and app tracking. Enforcement of those claims moves exclusively to the California Attorney General.

The change takes effect January 1, 2027. But it’s already reshaping how privacy attorneys, consumer advocates, and technology companies are thinking about online tracking accountability in the state that’s had the most consequential privacy legislation in the country.


What CIPA Actually Is

The California Invasion of Privacy Act dates to 1967. It was written primarily to address wiretapping and the recording of confidential communications without consent — the kinds of eavesdropping that, in 1967, required physical equipment and deliberate effort.

Decades later, litigation attorneys started applying CIPA to digital tracking technology. The legal theory: tools like session replay scripts, tracking pixels, and behavioral analytics that capture your interactions with a website or app in real time are functionally similar to electronic wiretapping. If a company embeds a third-party tracker that intercepts your clicks, form entries, and navigation in real time, that might constitute the kind of electronic interception CIPA was designed to prohibit.

Under Section 638.51, CIPA prohibited the installation or use of a “pen register or trap and trace device” without prior consent. As privacy litigants began applying this provision to web and app analytics, it became the basis for a wave of class action lawsuits against companies using Google Analytics, Meta Pixel, and similar tracking tools.

The damages structure made CIPA claims attractive to plaintiffs’ attorneys: $2,500 per violation, with each individual user session potentially constituting a separate violation.

What SB 690 Changes

SB 690 removes the private right of action for Section 638.51 violations when the conduct occurs on a website, online application, or mobile application.

Before SB 690: an individual could file a civil lawsuit for these violations and seek $2,500 per incident.

After SB 690 takes effect: only the California Attorney General can bring enforcement actions for § 638.51 violations in the website and app context.

The bill also applies retroactively. It covers cases filed on or after January 1, 2025, which means pending lawsuits that were filed in that window may be affected — though courts will need to work through how the retroactivity clause applies to each case.

Governor Newsom’s signing statement made clear he sees this as a fix to what he characterized as abusive litigation. He also said explicitly that more reform was needed — that CIPA still contains other decades-old provisions that are susceptible to misuse — and that he expected the Legislature to continue this work.

What SB 690 Does Not Change

The change is narrower than it might appear. Several important privacy protections remain intact.

Section 631 (wiretapping) is untouched. CIPA’s core wiretapping provision, which covers the unauthorized interception of telephone and electronic communications, is not affected. Private lawsuits under Section 631 continue.

Section 632 (recording confidential communications) is untouched. California remains an all-party consent state for recording conversations. Lawsuits for recording someone without their knowledge or consent are unaffected.

Common law privacy claims are untouched. The California Constitution recognizes a right to privacy that supports tort claims independent of CIPA. Those continue.

The Attorney General still enforces § 638.51. The law hasn’t decriminalized web tracking or declared it acceptable. It’s moved enforcement from private attorneys to the state’s top law enforcement officer. Whether the AG’s office will pursue these cases actively — and with the same volume as the private litigation bar — remains to be seen.

Other state privacy laws are unaffected. California also has the California Consumer Privacy Act (CCPA) and the California Privacy Rights Act (CPRA), which provide separate rights and enforcement mechanisms for data privacy. GDPR applies to companies operating in Europe. SB 690 doesn’t touch any of these.

Why This Reform Was Controversial

Privacy advocates and litigation attorneys have pushed back on SB 690’s framing as anti-abuse legislation.

Their argument: CIPA lawsuits — including the tracking cases this bill targets — served as one of the few practical mechanisms for holding companies accountable for non-consensual user tracking. Class actions create financial incentives for law firms to investigate and pursue privacy violations that no individual consumer would pursue on their own. Removing that incentive doesn’t eliminate the privacy harm; it just eliminates the accountability mechanism.

The counterargument, which drove the bill’s passage: the litigation wave produced substantial settlements from companies that weren’t acting in bad faith — businesses running standard analytics that had no idea they were potentially violating a 1967 wiretapping law. The unpredictability of CIPA exposure under the old framework was creating legal risk for routine business practices without meaningful privacy benefit.

Governor Newsom’s signing statement walked a line between both positions: he framed the reform as necessary to stop abuse while acknowledging that deeper privacy reform was still needed.

What This Means for People Who Use Apps

If you’re an individual user rather than a business, SB 690’s most direct effect is on your enforcement options — not your privacy.

You still have rights. Your right under CCPA and CPRA to know what data companies collect about you, to request deletion, and to opt out of the sale of your personal data is unchanged.

Tracking hasn’t become legal. Companies that deploy tracking tools still face obligations under CCPA, GDPR (for users in Europe), and the still-intact portions of CIPA. What’s changed is who can sue them.

The AG’s enforcement posture matters. The California AG’s office has historically been proactive on privacy. Whether it will pursue the volume and variety of § 638.51 cases that private attorneys pursued is unclear. If enforcement activity drops substantially, the practical protection afforded by this section of CIPA may diminish even though the law technically still exists.

Consent flows still matter. Companies that obtain prior affirmative consent before enabling tracking — a practice required by GDPR-aligned designs and consistent with privacy-by-default principles — face no CIPA § 638.51 exposure regardless of SB 690.

What This Means for the Privacy Landscape

SB 690 is the most significant narrowing of California’s privacy enforcement mechanisms in recent memory. It comes in a period when state-level privacy law has been expanding, not contracting — with new comprehensive privacy statutes taking effect across multiple states, the CPRA’s 2023 implementation, and federal privacy legislation continuing to be debated.

The law reflects a specific tension in privacy policy: enforcement mechanisms designed to protect individuals can be weaponized by litigation firms seeking quick settlements from businesses that made technical compliance mistakes, even without bad faith or concrete harm to users. Fixing that problem without weakening legitimate privacy protection is a challenge lawmakers haven’t fully solved.

Newsom’s call for further CIPA reform signals that this won’t be the last change. Other provisions of CIPA — particularly those that apply to interception of communications in other contexts — may be revisited in future legislative sessions.

The Broader Question: Who Enforces Privacy?

The deeper issue SB 690 raises is about who should be responsible for enforcing privacy rights.

Private litigation has historically played a significant role in US privacy law because federal privacy legislation is weaker and more fragmented than in Europe. The absence of a federal privacy law equivalent to GDPR means that class action lawsuits under state statutes have been one of the primary mechanisms for financial accountability.

When state legislators remove private enforcement mechanisms, they’re making a bet that government agencies will fill the gap. That bet has a mixed track record. Government enforcement is resource-constrained, often responds to the highest-profile violations, and may not prioritize the kinds of systemic, low-harm-per-user violations that aggregate into significant collective harm.

For privacy to be meaningful at the product level, it has to be built in by default — not as a response to litigation risk. Companies that design for data minimization, apply encryption to stored data, avoid training third-party AI on user content, and default to privacy-preserving settings don’t need to rely on the litigation landscape being favorable to them.

SB 690 changes one corner of California privacy enforcement. It doesn’t change the question of whether any particular product actually respects the people who use it.


Sources: WilmerHale – CIPA Reform Signed Into Law, Crowell – California Governor Signs SB 690, TrueVault – SB 690 Is Now Law

Your memories deserve better than an ad platform.

Try daftei free →
← All posts