Skip to main content
USA-Based Digital Agency

CIPA Website Tracking Lawsuits and SB 690: What Changed on September 30, 2026

On September 30, 2026, California’s governor signed SB 690. It ends private lawsuits under the pen-register section of the California Invasion of Privacy Act for tracking on websites and apps, operative January 1, 2027 and reaching cases filed since January 1, 2025. The wiretap section, which most pixel and session-replay suits use, is untouched. Tags that fire before a visitor answers the cookie banner are still the core exposure.

By George Shvaya · · Last checked against the signing message and bill text: October 28, 2026

What happened on September 30, 2026

Governor Gavin Newsom signed Senate Bill 690 on the last day of his signing window. His signing message to the Senate describes the bill in one sentence: it “eliminates the private right of action under the California Invasion of Privacy Act (CIPA) for violations of the pen register and trap-and-trace statute arising from conduct occurring on an internet website, online application, or mobile application.”

The message is unusually direct about why. The bill, he wrote, “addresses the vexatious use of CIPA lawsuits and demand letters to extract settlement money from small businesses that unwittingly install software on their websites that at times have tracked and shared the information of visitors to the site.” He then said the job is unfinished: “CIPA contains other decades-old statutes that are also susceptible to abuse by overly aggressive litigants. I urge the Legislature to take this on next year.”

The bill was authored by Senator Anna Caballero. It takes effect January 1, 2027, and law-firm summaries from Covington, Stinson and others agree on the retroactivity clause: it applies to any pending claim in an action commenced on or after January 1, 2025. The bill text is on the Legislature’s site.

What the lawsuits claim

The suits are brought under the California Invasion of Privacy Act, a 1967 wiretap statute. Plaintiffs’ firms argue that a third-party script on a web page is a listening device: when a visitor loads a page, the script sends what the visitor is doing to Meta, Google, TikTok or a session-recording vendor, and the visitor never agreed to that. Three fact patterns show up in current complaints, as described in a Loeb & Loeb analysis titled The Millisecond Problem:

  1. Tracking before consent. Tags fire on page load, before the visitor has answered the banner. Plaintiffs argue consent has to come before the interception, so consent collected afterward is irrelevant.
  2. The broken banner. The visitor clicks decline, the banner confirms it, and the tags keep running. This is the pattern courts treat most harshly, because the site made a promise and broke it.
  3. No consent mechanism at all. The site discloses tracking only in a footer-linked privacy policy, or not at all.

The money comes from Penal Code § 637.2, which lets a plaintiff recover $5,000 per violation or three times actual damages, whichever is greater, without proving any actual loss. Multiplied across a class of website visitors, that number is what makes a demand letter worth sending.

The four CIPA sections in play

Each section carries its own theory. SB 690 touches only the last one.

The four California Invasion of Privacy Act sections used in website tracking lawsuits, and the status of private lawsuits before and after SB 690
SectionTheory against a websitePrivate suit before SB 690After January 1, 2027
§ 631(a)WiretappingA third-party tag "reads" the contents of the visitor’s communication with the site while in transit.Private suit allowedUnchanged
§ 632Confidential communicationsRecording a confidential communication without all-party consent, pleaded against trackers and chat tools.Private suit allowedUnchanged
§ 632.7Cellular and cordless callsRecording calls that involve a cell or cordless phone, used against call-tracking and recorded sales lines.Private suit allowedUnchanged
§ 638.51Pen register / trap and traceA tag that captures IP addresses and device identifiers is a "pen register" installed without a court order.Private suit allowedAttorney General only, for websites and apps

What SB 690 changed, and what it did not

The enacted bill is much smaller than the one introduced in February 2025. According to a Shook, Hardy & Bacon summary of the Assembly Privacy and Consumer Protection Committee hearing, the original draft would have amended §§ 631, 632, 632.7 and 638.51 to exclude any technology used “in a manner consistent with a commercial business purpose.” That language would have ended most website-tracking suits outright. The committee amendments of July 1, 2026 dropped it. What survived is a single change to § 637.2: § 638.51 claims arising from websites and apps can be brought only by the Attorney General.

What SB 690 changed in the California Invasion of Privacy Act, before and after
ItemBeforeAfter SB 690
Private lawsuits under § 638.51 for website, online-app and mobile-app conductAllowed, $5,000 per violation under § 637.2Removed. Only the Attorney General may bring them.
Pending § 638.51 website claims filed on or after January 1, 2025ProceedingCovered by the amendment once it is operative; defendants are expected to move to dismiss.
Private lawsuits under §§ 631, 632 and 632.7AllowedUnchanged, including the $5,000-per-violation remedy.
Criminal penalties under § 638.51In forceUnchanged.
The "commercial business purpose" exemption in the original billProposed in early 2025 for §§ 631, 632, 632.7 and 638.51Removed by Assembly amendments on July 1, 2026. Not enacted.
Operative date—January 1, 2027

How much litigation this removes is disputed. Reported filing counts since early 2025 range from about 600 to more than 4,000, and as PPC Land notes, the sources disagree about whether they are counting pen-register claims or every CIPA website suit, and none of them publish docket data. Most complaints plead § 631 and § 638.51 together, so the practical effect is that a demand letter loses one of its two counts, not its reason to exist.

What courts have done so far

There is no controlling appellate decision on whether a 1967 wiretap statute covers a tracking pixel. Trial courts have split, and a Troutman Pepper Locke review of August 2026 decisions found most of them still let pixel claims past the pleading stage without deciding that threshold question. The decisions below are the ones that shape how these cases are argued.

Court decisions that shape California Invasion of Privacy Act website tracking cases
DateCourtWhat it held
May 31, 2022Ninth Circuit (unpublished)Javier v. Assurance IQ. Consent under § 631 has to come before the tracking, not after. Retroactive consent does not cure the interception.
Fall 2025Federal court, CaliforniaDoe v. Eating Recovery Center. Summary judgment for the site operator on a Meta Pixel claim: data that reached Meta about 0.2 seconds after the visitor’s action was not read "in transit." The court applied the rule of lenity and asked the Legislature to clarify the statute.
May 21, 2026N.D. Cal.Ortiz v. Foris Dax (Crypto.com). As reported, the pen-register claim survived while the wiretap claim was dismissed with leave to amend. The plaintiffs alleged trackers kept firing after they chose "Disable All."
August 3, 2026E.D. Cal. (magistrate findings)A magistrate judge concluded § 631(a) does not reach internet communications at all, and called the question open. Findings and recommendations, not a final ruling.
August 7, 2026N.D. Ill.A consent defense failed because the cookie banner did not say data would be shared with third parties. Pixels sent data to TikTok, Meta, Google and LinkedIn.

Two of those cut against plaintiffs. The Eating Recovery Center ruling found that a pixel delivering data a fifth of a second later is not reading it “in transit,” and the Eastern District magistrate questioned whether § 631 reaches the internet at all. Neither binds other courts, and the August decisions in Illinois and San Diego went the other way on consent. A site operator cannot plan around the split. What the operator controls is whether the tags fire before the visitor answers.

Which tags draw the suits

The exposure follows the data. A tag that receives what a visitor typed is a different legal object from one that counts page views. Meta’s own advanced-matching documentation lists email, phone, first name, last name, city, state, zip, birthdate and gender as the fields the pixel can send, hashed with SHA-256 before transmission. Hashing does not change the fact that the data left the site.

Common website tags, what each captures, and its relative exposure in CIPA litigation
TagWhat it capturesRelative exposure
Meta PixelPage URLs, button clicks and, with advanced matching, form fields such as email, phone, first and last name, sent to Meta as SHA-256 hashes.Highest. Named in most wiretap complaints because form data leaves the site.
Session replay and heatmapsMouse movement, scrolling, keystrokes and page snapshots.High. Pleaded as recording the communication itself.
Third-party chat widgetsThe full text of the conversation, stored by the vendor.High under §§ 631 and 632, with a separate line of suits over transcripts shared with vendors.
Call tracking with recordingDynamic phone numbers and recorded calls.High under § 632.7 when calls are recorded without an all-party notice.
Google Analytics 4Page views, events, client ID, IP address at collection, device and browser details.Lower. Appears in complaints, mostly as the pen-register theory SB 690 now limits.
Google Ads conversion tagClick identifiers, conversion events and, with enhanced conversions, hashed contact details.Moderate. Same pen-register theory, plus wiretap claims when form data is included.

The millisecond problem

Most sites that have a cookie banner still fire their tags on page load. The banner is a React component or a plugin that mounts after the page renders, and the analytics snippet is in the document head. By the time the banner is visible, Google and Meta have already received the first page view. The visitor’s later click on accept or decline changes nothing about that first request, and a decline that only hides the banner changes nothing about the next one either.

That is the whole case. Plaintiffs’ firms do not need to argue about what the privacy policy says. They open the network tab, load the page, and screenshot the requests to facebook.com and google-analytics.com that happen before any click. The 2022 Ninth Circuit memorandum in Javier is the authority they cite: consent obtained after the fact does not cover what was already intercepted.

Find out what your site sends before anyone clicks

The free audit records every third-party request your pages make on load, before the banner, and tells you which tags need gating.

How to load tags only after consent

The fix has three parts, and they have to be done in this order.

  1. Set the consent default to denied before any tag loads. Google’s consent mode documentation is explicit that the default command must run before any config or event command, or “consent defaults won’t work.” Put it inline in the head, not in a deferred bundle.
  2. Do not inject the tag container until the visitor accepts. This is what Google calls the basic implementation: no Google tag loads at all until consent is granted. The advanced implementation loads the tag immediately and sends cookieless pings while consent is denied. Google’s own description of those pings says they may include user agent, screen resolution and IP address. That is exactly the data a pen-register complaint describes, so for a California audience the basic implementation is the safer choice even though it gives up behavioral modeling.
  3. Make decline do something. Persist the choice, send a consent update of denied, set the tag’s documented opt-out flag, and delete the analytics cookies that exist. Then test it: decline, reload, and confirm the network tab shows no request to the tag vendors.

The minimum gtag pattern looks like this:

<!-- 1. Before any Google tag loads -->
<script>
  window.dataLayer = window.dataLayer || [];
  function gtag(){dataLayer.push(arguments);}
  gtag('consent', 'default', {
    'ad_storage': 'denied',
    'ad_user_data': 'denied',
    'ad_personalization': 'denied',
    'analytics_storage': 'denied',
    'wait_for_update': 500
  });
</script>

<!-- 2. Only after the visitor clicks Accept -->
<script>
  function onAccept() {
    gtag('consent', 'update', {
      'ad_storage': 'granted',
      'ad_user_data': 'granted',
      'ad_personalization': 'granted',
      'analytics_storage': 'granted'
    });
    loadTagManager(); // inject gtm.js or gtag.js here, not on page load
  }
</script>

Meta Pixel, TikTok, LinkedIn and session-replay tools do not read Google’s consent signals. Each one has to be wrapped in the same accept handler, or loaded through a Tag Manager trigger that waits for a consent event. If a third party installs tags for you, such as an ads agency or a call-tracking vendor, those need to go through the same gate; a tag pasted directly into the theme by someone else is the most common way a gated site becomes an ungated one. We build this into every site we develop and retrofit it during a redesign. Deferring heavy tag containers until after consent also helps Core Web Vitals, because a 300 KB container is no longer competing with the page for the main thread.

How this site handles it

Webvello.com runs one analytics tag, Google Analytics 4, and no advertising or session-replay tags. The site shows a banner on first visit; analytics defaults to granted for United States visitors and to denied for visitors in the European Economic Area, the United Kingdom and Switzerland, using consent mode’s region setting. A browser that sends the Global Privacy Control signal is treated as a decline. Declining sets GA’s documented opt-out flag, so the tag sends nothing rather than cookieless pings, and deletes the analytics cookies already set. Advertising storage is always denied. The full cookie table is in our privacy policy.

That is a United States notice-and-opt-out model, which is the common practice and carries the lowest-exposure tag. After reading the complaints described above, our recommendation for a site with mostly Californian traffic, or any advertising pixel, is to go one step further and default to denied for everyone until the visitor accepts.

A ten-minute self-check

You can see what a plaintiff’s firm would see without any tools beyond a browser.

  1. Open a private window so no earlier consent choice is stored.
  2. Open developer tools, select the Network tab, and tick “Preserve log.”
  3. Load your homepage. Do not click anything.
  4. Filter the request list for facebook, google-analytics, googletagmanager, doubleclick, clarity, hotjar, tiktok and linkedin. Anything listed fired before consent.
  5. Click decline on your banner, reload, and repeat the filter. Anything listed fired after a decline.
  6. Open your contact form, type into a field, and watch the request list. A request to facebook.com after typing means the pixel is capturing form input.
  7. Check who else has access to your tag container or theme. Every person who can add a tag can undo the gate.

A site with nothing listed in steps four, five and six has removed the fact pattern the complaints rely on. Sites that fail step four or five are the ones receiving demand letters. The same discipline applies to the other compliance obligation that reached websites this year; our guide to the ADA Title II web rule covers it, and the banner itself is a conversion element worth designing rather than defaulting.

Common questions

What did Governor Newsom sign on September 30, 2026?

Senate Bill 690, which amends the California Invasion of Privacy Act so that violations of the pen register and trap-and-trace statute (Penal Code § 638.51) arising from conduct on an internet website, online application or mobile application can be pursued only by the Attorney General. Private plaintiffs can no longer sue under that section for website tracking. The change is operative January 1, 2027.

Does SB 690 end cookie-consent and tracking-pixel lawsuits in California?

No. It removes one theory, the pen-register claim under § 638.51. The wiretap section (§ 631), the confidential-communication section (§ 632) and the cellular-call section (§ 632.7) still carry a private right of action and the $5,000-per-violation remedy. Most Meta Pixel, session-replay and chat-widget suits are brought under § 631.

Is SB 690 retroactive?

Yes, for pending claims. The amendment applies to any pending § 638.51 claim in an action commenced on or after January 1, 2025. Law-firm summaries expect defendants to move to dismiss those claims once the amendment is operative. Cases that were already settled or dismissed are not reopened.

Is a cookie banner enough?

Only if the site actually behaves the way the banner says. The current complaints target three patterns: tags that fire before the banner is answered, banners where "decline" does not stop the tags, and sites with no consent mechanism at all. A banner that shows after the tags have already fired is the first pattern.

Does Google Analytics alone put a site at risk?

Less than a Meta Pixel or a session recorder does. Google Analytics appears in complaints, mainly under the pen-register theory that SB 690 now limits to the Attorney General. The wiretap theory depends on a third party reading the contents of a communication, which is a harder argument to make about page-view analytics than about a pixel that receives form fields.

What does "consent mode" do when a visitor declines?

With Google consent mode, denying analytics_storage means no Analytics cookies are set or read. In the advanced implementation the tag still sends cookieless pings, which Google says may include user agent, screen resolution and IP address, and uses them for behavioral modeling. The basic implementation loads no Google tag at all until consent is granted, which is the stricter option.

How many of these lawsuits have been filed?

No one publishes the docket data. Reported estimates since early 2025 range from about 600 to more than 4,000 depending on who counted and whether they counted pen-register claims only or all CIPA website-tracking suits. Treat any single number as an estimate.

Gate your tags before someone else checks them

We will record what your site sends on load, gate every third-party tag behind consent, and verify the decline path actually stops them.

This page is general information about a technical problem, not legal advice, and case outcomes described from secondary reports are marked as such. Primary sources: Governor’s signing message (Sept. 30, 2026), SB 690 bill text, Penal Code § 637.2, § 638.51, § 631, Google consent mode, Meta advanced matching. Legal analysis: Covington, Stinson, Shook Hardy & Bacon, Loeb & Loeb, Troutman Pepper Locke, Privacy World. Talk to a California privacy lawyer before relying on any of it.