Article
What is the difference between CIPA pen-register and wiretap theories for website tracking?
Plain-English map of CIPA pen-register and wiretap website theories, what SB 690 covers, and which storefront checks to keep. Not legal advice.
In brief
In website-tracking lawsuits under California's Invasion of Privacy Act, plaintiffs often plead two theories. Pen-register and trap-and-trace claims, often discussed under section 638.51, focus on addressing, routing, or signaling information. Wiretap and eavesdropping claims, often discussed under sections 631 and 632, focus on communications content. SB 690, signed September 30, 2026 and operative January 1, 2027, moves private section 638.51 website and app claims to the Attorney General. It does not amend sections 631 or 632. Operators still need evidence of what loads before consent and after Reject. This page is a high-level map, not legal advice.
Not legal advice
This page maps two CIPA website-tracking theories in plain English. It is not legal advice, not a case prediction, not counsel on a demand letter or complaint, and not a reading of how any court will rule.
Section numbers below are names people use in alerts, not pasted statutory text. Open the code or the SB 690 chaptered text. Readers with California exposure should talk to their own counsel. A ConsentProbe report is not a CIPA legal opinion.
Updated October 9, 2026: SB 690 was signed on September 30, 2026 (Chapter 976). This page now cites the chaptered text. Earlier versions described the bill as pending with the Governor.
Short answer
The same pixel or session tool can show up under more than one label. Pen-register and trap-and-trace style claims, commonly discussed under section 638.51, focus on alleged recording of routing, addressing, or signaling information. Wiretap and eavesdropping style claims, commonly discussed under sections 631 and 632, focus on alleged interception of communications content.
SB 690 changes who may bring certain pen-register website claims. It does not amend the wiretap and eavesdropping sections. The SB 690 guide holds the timeline. Operators still need a record of what loads before Accept and after Reject.
Two theories, one storefront
An alert often uses one of these labels and assumes you already know which theory is in play. Pixels, click IDs, chat widgets, and session replay can appear under either label. The label is the pleading. The browser record is separate: a cookie, a request, a script, a screenshot of the banner state.
The pre-consent audit checklist is the pass order: a fresh load, storage, Reject All plus one navigation, and an accept baseline.
Pen-register and trap-and-trace theory
In plain English, this style of claim is about capturing addressing, routing, or signaling information: how traffic is directed, which identifiers travel with a request, which hosts it touches. Public chatter describes pixels, analytics IDs, and URL metadata as the things plaintiffs try to call a pen-register-style device. That is a description of the chatter, not a case holding.
The section people name is Penal Code section 638.51. Read it on the Legislature's site. This page does not paste the section or invent a quotation.
From January 1, 2027, only the Attorney General may bring a section 637.2 action against a private actor for a section 638.51 claim about website or app conduct. The SB 690 guide has the details. This page only needs the split: that news slice is about one theory, not the whole Act.
Wiretap and eavesdropping theory
In plain English, this style of claim is about intercepting or recording the content of a communication: what was said, what was typed, what a session-replay or chat tool is alleged to have captured as content. People often name sections 631 and 632. Those are names. The elements live in the code and in counsel's reading.
Session replay, chat transcripts, and form contents are the examples alerts use when they contrast this theory with pen-register talk. The same tool can be discussed under either label, depending on the pleading. The label helps you read the alert. It does not list the scripts your theme loaded.
SB 690 does not amend sections 631, 632, or 632.7. Private wiretap and eavesdropping claims are unchanged, and a pen-register change is not a reason to tell a team that wiretap claims ended.
Side-by-side, for operators
Use the table to keep the two conversations apart. It is descriptive. It is not a list of defenses, and it does not state fines, damages, or outcomes.
Swipe to see more
| Angle | Pen-register / trap-and-trace (often section 638.51 talk) | Wiretap / eavesdropping (often section 631 / 632 talk) |
|---|---|---|
| Rough focus | Addressing, routing, or signaling-style information | Content of a communication |
| How it shows up in website-tracking chatter | Pixels, IDs, and URL or routing metadata alleged as pen-register-like | Session replay, chat, or form contents alleged as interception |
| SB 690, per the chaptered text | From January 1, 2027, private actors face only the Attorney General on website and app pen-register claims | Not amended. Private claims remain |
| What operators can still measure | Which third parties load, which cookies or storage they set, and when they fire | The same runtime surfaces. A labeled evidence pack stays useful |
What SB 690 does and does not settle
SB 690 is one enforcement slice. It was signed on September 30, 2026 (Chapter 976, Statutes of 2026) and becomes operative on January 1, 2027.
- The Legislature passed SB 690 on August 28, 2026, and the Governor approved it on September 30, 2026.
- Subdivision (d)(2) also reaches pending claims in actions commenced within two years before January 1, 2027.
- The chaptered text amends only section 637.2. Subdivision (d) names section 638.51 and no other section.
- With that private pen-register path narrowed, storefront testing remains an operations task. A change in who may file one kind of claim does not turn tags off.
What to still measure
The pre-consent audit checklist has the full pass table. Use a clean profile, the same URL, and a note of region. Label every file by state.
- Fresh visit: do not click Accept. Record cookies, storage, third-party ad and analytics requests, and a screenshot of the banner.
- Reject All, or the closest control (Decline, Essential only): click it, navigate once, and record the same surfaces. Compare that run with Accept.
- Accept All, in a new clean profile: record the same surfaces so you have a baseline for what the tags do after a choice.
- Optional California path: if you claim to honor Global Privacy Control, compare GPC off with GPC on. The GPC test guide shows how to confirm
Sec-GPC: 1. SB 690 does not perform that comparison. - Strip query values that carry identifiers before you share the pack.
Evidence pack fields
A usable pack names the URL, the timestamp, browser and profile notes, the consent-state label, a cookie table, key request URLs, screenshots, and an optional HAR snippet with secrets removed. A banner photo shows that a control existed. It does not show whether a marketing host still loaded after Reject.
ConsentProbe maps findings to a request, a cookie, or a screenshot after a saved run. A free US-baseline visit stores one non-California technical record so you can learn the report shape. It is not a California legal conclusion and not a CIPA risk score. Paid California scenarios compare GPC off with GPC on. Paid EU scenarios are a different pack. Read the free versus paid guide before you quote a region.
FAQ
What is a CIPA pen-register theory for websites, in one sentence?
A claim style that treats certain website tracking as capturing dialing, routing, addressing, or signaling-type information under CIPA pen-register and trap-and-trace provisions. The elements belong to counsel and to the code.
How is that different from a wiretap theory?
Wiretap and eavesdropping-style claims focus on alleged interception or recording of communications content. People name different sections, and the elements differ.
Did SB 690 end all CIPA website lawsuits?
No. From January 1, 2027, it moves private section 638.51 pen-register claims about website or app conduct to the Attorney General. It does not amend sections 631 or 632, so wiretap claims remain. Read the SB 690 guide and talk to counsel.
If the litigation theory changes, should I still audit cookies?
Yes. Operations still need evidence of pre-consent and post-reject behavior. The pre-consent audit checklist is the pass order.
Does ConsentProbe decide if I am liable under CIPA?
No. ConsentProbe records technical browser evidence. Legal conclusions need your counsel. A report is not a CIPA opinion.
What should I send counsel after an alert?
State-labeled cookie tables, request lists, screenshots, and timestamps. A banner photo without those layers leaves the handoff thin.
Limits of this page
This article explains, at a high level, how public commentary and lawsuit pleadings have framed website-tracking claims under California's Invasion of Privacy Act, especially pen-register and trap-and-trace theories versus wiretap and eavesdropping theories. It is not legal advice, not a case prediction, not counsel on any demand letter or complaint, and not a reading of how any court will rule.
A ConsentProbe report is not a CIPA legal opinion. Free US-baseline output is not a California conclusion. Readers with California exposure should talk to their own counsel, and they should read the SB 690 chaptered text with counsel.
Related guides
Read the SB 690 guide for the timeline and the FAQ for whether every website suit ends.
Sources
These links cover the platform and regulatory context used in this guide. Applicability still depends on the organization and jurisdiction.
- California Legislative Information — Penal Code section 638.51
- California Legislative Information — Penal Code section 631
- California Legislative Information — SB 690 bill history
- California Legislative Information — SB 690 chaptered text (Chapter 976)
- CapitolTrack — SB 690 chaptered bill, Chapter 976, Statutes of 2026 (PDF)
- California Legislative Information — California Constitution, Article IV, section 8
- Sidley Austin — SB 690 clears the Legislature, September 2026 (written before signing)
- ConsentProbe methodology
Save a US-baseline technical record
After a DIY check, run a free US-baseline scan: one browser visit outside California, with cookies, requests, and screenshots stored as evidence. That visit does not run EU reject/accept or California GPC. EU, California, and Global 2 audits can be purchased from Billing after sign-in.