All Blog Posts

California Invasion of Privacy Act (CIPA) Website Compliance: How to Review and Reduce Your Risk

Close
Read time
12 mins
Published
Nov 3, 2026
Share

  • The California Invasion of Privacy Act (CIPA) protects against certain forms of wiretapping, interception, and eavesdropping without consent.
  • CIPA lawsuits have targeted websites that use third-party technologies to collect or receive visitor information.
  • CIPA Section 631 wiretapping claims remain available to private plaintiffs, including after SB 690.
  • CIPA Section 638.51 pen-register claims have targeted website trackers. SB 690 limits those claims to the California Attorney General starting January 1, 2027.
  • Session replay, advertising pixels, chat widgets, and analytics tools can attract CIPA claims depending on how they collect and share data.
  • CIPA compliance starts with knowing what runs on your website, when tracking begins, and whether visitors’ consent choices are respected.

The California Invasion of Privacy Act (CIPA) was written decades before cookies, pixels, and session replay tools existed. Today, it’s being used in lawsuits over how websites collect and share visitor data. Here’s what that means for your website and what you can do about it.

A session replay tool, advertising pixel, or chat widget might seem like a routine part of running a website. But these technologies are also at the center of a growing number of lawsuits under the California Invasion of Privacy Act (CIPA), with claims focusing on how they collect and share information about website visitors.

So if your business has visitors or customers in California, it’s important to understand what these technologies are doing on your website. Your cookie banner configuration may not be enough if tracking starts before visitors have made a choice or data is shared with third parties without their knowledge.

This guide explains where CIPA risk can arise on websites and gives you a checklist for reviewing your own setup, so you can identify potential issues and decide what needs attention.

What Is the California Invasion of Privacy Act (CIPA)?

The California Invasion of Privacy Act (CIPA) is a state law designed to protect people from certain forms of interception, recording, and eavesdropping without consent. When it was enacted in 1967, those concerns largely centered on telephone calls and other private communications.

More recently, CIPA has been applied in lawsuits involving online activity. Some plaintiffs have argued that website technologies can capture information about how visitors interact with a site and share it with third parties without the required consent.

As a result, common tools such as session replay, advertising pixels, analytics, and online chat have come under greater scrutiny. But using these technologies doesn't automatically mean a website violates CIPA. What matters is how they're used, including what data they collect, when collection begins, and who receives that data.

Does CIPA Apply to Websites?

It can, as CIPA claims have been brought against businesses over the way their websites use third-party tracking and communication technologies.

For example, a website might use a third-party tool to record how visitors interact with a page, track their activity, or provide a live chat feature. CIPA claims may arise if that tool collects or receives information about a visitor’s interactions without the required consent.

However, CIPA’s application to website technologies is still evolving, and courts have reached different conclusions depending on the circumstances. For website operators, the key question isn’t simply whether a particular tool is installed, but what data it collects, when it collects it, and where that data goes.

Why Are Websites Facing CIPA Lawsuits?

Many CIPA lawsuits focus on the use of third-party technologies that collect information as visitors interact with a website. For example, a tool might capture activity while someone browses a page, fills out a form, or uses a chat feature, and sends that information to another company.

It’s this collection and sharing of visitor information that has become the basis of many CIPA claims. Plaintiffs have argued that, depending on how the technology works, a third party’s involvement can amount to unlawful interception or tracking.

These arguments have brought common marketing, analytics, and website tools into CIPA litigation, with claims generally centered on two provisions of the law: Section 631 and Section 638.51.

CIPA Section 631 and Wiretapping Claims

Section 631 is the basis for what are often described as CIPA wiretapping claims. In website cases, plaintiffs have argued that a third-party technology intercepted information they were communicating to a website without their consent.

For example, a session replay tool may capture a visitor’s clicks, page activity, or information entered into forms and send that data to the technology provider while the visitor is still using the site. 

This can create greater risk under Section 631 because the tool may capture what the visitor is communicating, such as keystrokes or form entries, rather than simply recording that the visitor viewed a particular page. Section 631(a) claims generally require that the information be the contents of a communication and that a third party reads or attempts to read it while it’s in transit.

The timing of consent can matter too. In an unpublished 2022 decision, Javier v. Assurance IQ, the Ninth Circuit held that Section 631(a) requires consent before recording begins, and that consent given afterward did not cure the alleged violation.In other words, if a technology starts collecting or transmitting data before a visitor consents, asking for consent afterward may be too late for data that has already been collected.

CIPA Section 638.51 and Pen Register Claims

Section 638.51 has been the basis for a separate type of CIPA claim involving pen registers and trap-and-trace devices. In website cases, plaintiffs have argued that tracking technologies act like these devices when they collect information that identifies a visitor or their online activity and send it to a third party without the required authorization.

A pen register traditionally recorded information about telephone calls, such as the numbers dialed, rather than what was said during the call. The argument in website cases is that some trackers perform a similar function when they collect this type of information and send it to a third party.

What SB 690 Changes for Website Operators

SB 690 removes private lawsuits under Section 638.51 over website and app tracking, leaving enforcement to the California Attorney General. Governor Gavin Newsom signed the bill on September 30, 2026, and it takes effect on January 1, 2027. It applies retroactively to pending claims filed within the two years before that date.

The law reduces one major source of lawsuits, but it doesn't make website tracking risk-free. Section 638.51 itself remains in place, so the Attorney General can still enforce it, and the law doesn't change Section 631. Plaintiffs have already brought similar claims under Section 631, and the timing and handling of consent matter there too.

Which Website Technologies Can Attract CIPA Claims?

CIPA claims can involve a range of website technologies, especially when information about a visitor’s activity is shared with a third party. What matters most isn’t necessarily the type of tool being used, but what data it collects, who receives it, and how that data is used.

TechnologyWhat It Typically DoesWhere CIPA Questions Can Arise
Session ReplayRecords how visitors interact with a page, including clicks, scrolling, and sometimes typing or form activityThese tools can give a third party access to detailed visitor interactions. The concern can be greater when they capture what someone types into a search bar or form, rather than only clicks or page movements.
Chat WidgetsEnable visitors to communicate with a business through the websiteA third-party provider may receive the contents of a visitor’s messages as the conversation takes place, making the actual communication available to another party.
Advertising PixelsSend information about page visits and visitor actions to advertising platformsPixels can transmit visitor activity and identifiers to a third party. What is transmitted, when it is sent, and how the third party can use it can all matter.
Analytics TagsMeasure how visitors find and use a websiteBasic usage data may raise different questions from an implementation that sends search terms, form information, or other details about what a visitor communicates.
Other Third-Party TrackersCollect information such as IP addresses, cookies, or device informationIdentifying and routing information has been at the center of Section 638.51 pen-register claims. Private plaintiffs will no longer be able to bring those claims over website conduct once SB 690 takes effect, though the Attorney General still can.

CIPA Compliance Checklist: How to Reduce Risk on Your Website

Reducing CIPA risk starts with understanding what happens when someone visits your website. It isn’t enough to know that you have a cookie banner or that a particular tool is categorized for analytics. Instead, it’s important to know what technologies are running, what data they collect, and whether they start collecting it before the visitor has had a chance to make a choice.

The following steps can help you review your website and identify areas that may need closer attention.

1. Inventory Your Cookies, Trackers, Pixels, and Scripts

Start by identifying the technologies running across your website. This includes cookies and trackers as well as advertising pixels, analytics tags, session replay tools, chat widgets, and other third-party scripts.

A cookie scanner helps you find the cookies and trackers that are active on your site, including ones you may not be aware of. You can use your browser’s developer tools to inspect cookies and network requests as you move through the site. You can also review the tools and integrations your teams have added directly or through a tag manager.

Don’t limit the review to your homepage. Different technologies may load on product pages, forms, checkout pages, account areas, or other parts of the site. The aim is to build a picture of what’s running, rather than relying only on a list of tools your team remembers installing.

2. Identify What Data Your Third-Party Technologies Collect

Next, take a closer look at what information each third-party technology receives when someone uses your website.

Depending on the tool, this might include an IP address, the pages someone visits, what they click, information they enter into a form, or their interactions with a chat feature. The key question isn’t simply whether a third party is involved. It’s what information is being shared with that third party, when it is shared, and for what purpose.

A good place to start is the provider’s documentation, along with the settings you have configured for the tool. If you want to see what data is actually leaving your site, your browser’s developer tools also enable you to inspect the requests being sent to third parties.

Pay particular attention to technologies that receive information in real time as someone interacts with the site. As we saw with Section 631, real-time collection has been central to some CIPA wiretapping claims.

Once you know which technologies your website uses, the next step is to check when they are activated. Open your site as a new visitor, but don’t interact with the cookie banner yet.

Using your browser’s developer tools, check whether requests are already being sent to any of the third-party services you identified earlier. If an analytics tag, advertising pixel, or session replay tool is already transmitting data, data collection has started before the visitor has made a choice.

If you find technologies running before consent, review how your cookie banner and the controls behind it are configured. Check whether those technologies are connected to the appropriate consent choices and whether they can be blocked until the visitor makes a choice.

That distinction matters, because consent given after a tool is activated may not cover data that was collected beforehand. In other words, “no non-essential tag fires before consent” should reflect what actually happens on the website, not just how the consent banner is configured.

4. Test What Happens When a Visitor Rejects Tracking

Don’t stop at checking what happens before someone interacts with the banner. Test the rejection path as well.

Reject non-essential tracking, then use your browser’s developer tools to check whether the relevant technologies remain blocked. For example, if you reject advertising cookies but an advertising pixel continues sending data, the website isn’t reflecting the choice you just made.

Repeat the test on pages where different technologies are active, particularly forms, checkout flows, account areas, and pages with chat or session replay tools.

5. Check How Your Website Responds to Global Privacy Control (GPC)

Global Privacy Control (GPC) enables people to set their privacy preferences once, via a built-in browser setting or plugin, which will then send an automated request to every website they visit to opt out of the sale or sharing of their personal information. 

California's Opt Me Out Act, operative January 1, 2027, requires browser developers to include an easy-to-find setting that lets people send an opt-out preference signal, such as GPC, to every website they visit. 

Businesses subject to the CCPA must already recognize qualifying signals as valid opt-out requests. Since January 1, 2026, they must also display on their website whether the signal has been processed, for example with an "Opt-Out Preference Signal Honored" message or a toggle showing that the opt-out is active. 

A built-in browser setting will likely increase the volume of automated opt-out requests, so now is a sensible time to test how your site detects, honors, and visibly confirms the signal, and to check that your vendors act on it too.

Although GPC is required under the CCPA regulations rather than CIPA, it belongs in this review because it tests the same underlying question: does your website respect a visitor’s privacy choice?

To test this, enable GPC in a supported browser, visit your website, and check how it responds. Confirm that the signal is recognized and that any sale or sharing of personal information covered by the request is stopped.

6. Document and Regularly Review Your Setup

Keep a record of the technologies you identified, including what data they collect, when they run, and how they respond to visitors’ choices. This gives the teams responsible for your website and privacy practices a clear record to work from when technologies are added, removed, or reconfigured.

Lastly, a CIPA compliance checklist shouldn’t be a one-time exercise. Website technologies and their configurations change, so repeat these checks periodically to make sure the behavior you originally reviewed is still the behavior visitors experience.

What Should You Do if You Receive a CIPA Demand Letter?

Receiving a CIPA demand letter doesn’t mean your business has violated the law, but it is something to take seriously. Before responding or making changes to your website, speak with qualified legal counsel who can assess the specific allegations and advise you on what to do next.

If the letter relies on Section 638.51, ask counsel how SB 690 may affect the claim, including its retroactivity provision. Claims under Section 631 are not affected by the law.

Preserve a record of your website as it existed when you received the letter, including the tracking technologies in use, your cookie banner and privacy notices, and relevant configurations or consent records. This can help establish what visitors would have experienced at the time of the alleged activity.

The review you carried out using the checklist above can also help you understand which technologies are involved and what data they collect. This will help you have a clearer picture of your website setup when discussing the claim with counsel.

CIPA was written long before websites started using pixels, session replay, analytics, and other tracking technologies. As courts continue to consider how the law applies online, businesses need a clear understanding of how these technologies handle visitor data. That includes what they collect, when they start collecting it, and whether they respect visitors’ consent choices.

A consent management platform (CMP) like Cookiebot™ CMP can make this easier to manage. Cookiebot™ regularly scans your website to identify and categorize active cookies and trackers, including new ones that appear as your site changes. It can also block them until consent is received, and then apply their choices to tracking technologies. Visitors can also update their consent choices at any time.

This gives you a way to manage the tracking and consent issues that can create CIPA risk, and helps keep your website’s tracking aligned with visitors’ consent choices as your site changes.

Frequently asked questions

The California Invasion of Privacy Act (CIPA) is a California law that protects against certain forms of wiretapping, eavesdropping, and interception of communications without consent. Enacted in 1967, the law is now also being used in lawsuits involving website tracking technologies.

CIPA can apply to certain activities involving websites. Lawsuits have alleged that technologies such as session replay tools, tracking pixels, and chat services can violate CIPA when third parties receive visitor communications or other covered information without the required consent.

CIPA compliant generally means operating in a way that meets the requirements of the California Invasion of Privacy Act. For websites, this can involve reviewing what data third-party technologies collect, when collection begins, and whether appropriate consent is obtained prior to data collection and processing.

CIPA wiretapping generally refers to the interception or unauthorized access to communications covered by the law. In website cases, plaintiffs have alleged that third-party technologies can act as wiretappers when they receive visitor communications as they happen without the required consent.

A CIPA lawsuit is a legal claim alleging a violation of the California Invasion of Privacy Act. Website-related cases have focused on practices such as session replay, tracking pixels, and other third-party technologies that collect or receive information about visitor interactions.

Yes, analytics tools can be involved in CIPA claims depending on how they work and what information they receive. However, simply using analytics does not automatically violate CIPA.

A cookie banner can help with CIPA compliance, but displaying one doesn’t ensure it if it’s not configured to block non-essential tracking before visitors consent to it. What matters is whether relevant technologies are blocked until consent is received.

No. SB 690 removes private lawsuits under Section 638.51 over website and app tracking, but claims under Section 631 remain available. The California Attorney General can still enforce Section 638.51.