Website Management and CRO Services

{ Website Privacy }

An Attorney’s Guide to the California Invasion of Privacy Act

Businesses of every size are getting demand letters under the California Invasion of Privacy Act (CIPA) over routine tools like the Meta Pixel and Google Analytics. Created with data privacy attorney Karen Batcher of Alliance Data Privacy Solutions, Inc., this guide explains what changed, why a cookie banner alone may not protect you, and how to find out what your website is sending.

Website Privacy Hub

Three Ways to Get Up to Speed

Start with what your website needs, get the quick background on the legal risk, or read the attorney’s complete answers.

The Short Version

Three facts from the questions and answers below, in the attorney’s own words.

Statutory damages in a typical demand letter

$5,000

per violation under § 631; and $5,000 per violation under § 638.51

Claims filed in California alone last year

over 800

a wave of class-action lawsuits and demand letters targeting business websites

What serial plaintiffs are sending

thousands

of templated CIPA demand letters involving routine analytics and marketing technologies

About These Answers

The questions below were put to Karen Batcher, an attorney with Alliance Data Privacy Solutions, Inc., who is licensed to practice law in California and works extensively on data privacy counseling and risk management. KWSM built this hub in collaboration with her so business owners can read the legal picture and the website fix side by side. Her answers appear exactly as she wrote them; the section headings, graphics and surrounding notes are KWSM’s.

Part 1

Why Businesses Are Getting California Invasion of Privacy Act (CIPA) Demand Letters

Four questions on how decades-old wiretapping and video-privacy statutes became the basis for claims over everyday marketing tools.

We are seeing a surge in demand letters regarding website tracking. From a legal perspective, what exactly shifted in the law (or how the law is interpreted) that caused this flood of litigation?

The biggest change was not a newly enacted California wiretapping statute. It was a change in how plaintiffs and some courts began applying existing statutes to modern web technology.

CIPA dates to 1967. Plaintiffs historically associated it with telephone interception and recording. More recently, plaintiffs have argued that when a website embeds a third-party pixel, session-replay script, analytics tool, chat technology, or SDK, that third party may be “intercepting” an electronic communication between the visitor and website.

Two appellate developments helped accelerate the theory. In Javier v. Assurance IQ, the Ninth Circuit Court of Appeals held that consent obtained after interception cannot retroactively authorize an interception that has already occurred. Separately, the Third Circuit Court of Appeals interpreting Pennsylvania’s wiretap statute in Popa v. Harriet Carter Gifts, strengthened plaintiffs’ arguments concerning third-party website interception. After these decisions, class-action filings increased substantially. Courts subsequently allowed various session-replay claims to proceed, including claims involving life-insurance and retail websites.

A second wave came from an even more aggressive CIPA theory: pen registers and trap-and-trace devices. In Greenley v. Kochava, the District Court for the Southern District of California interpreted “pen register” broadly enough to encompass certain software-based online tracking technology. That decision reportedly generated more than 120 lawsuits from one firm alone.

The practical consequence has been an industrialized demand-letter environment. By September 2026, reporting described a relatively small number of serial plaintiffs sending thousands of templated CIPA demand letters involving routine analytics and marketing technologies and targeting businesses in varying industries and of every size.

So the short answer is: the technology did not suddenly become unlawful. Plaintiffs developed new statutory theories, several important decisions allowed enough of those theories to survive early dismissal, and statutory damages plus inexpensive automated website scanning created economic incentives for high-volume claims.

Plaintiffs started to focus on what happens technically when a web page loads. Suppose a visitor opens a webpage containing a Meta Pixel. The browser may simultaneously communicate information to Meta: IP address, cookie or device identifiers, page URL, events, button clicks and potentially information concerning what the visitor viewed or entered.

The CIPA theory essentially reframes that transaction as:

Visitor → Website + Third-Party Tracker

rather than simply:

Visitor → Website

Plaintiffs argue that the tracker is therefore a third party acquiring a communication contemporaneously with its transmission. Session-replay software presents a similar theory because it can capture clicks, keystrokes, navigation and other website interactions. Courts have allowed some such interception/aiding-and-abetting theories to survive dismissal.

The VPPA theory is narrower. The 1988 statute protects personally identifiable information connecting a consumer with specific video materials. Plaintiffs therefore try to establish that a pixel transmitted two things together, or transmitted information that the recipient could combine: identifiable user + specific video viewed.

This theory is not new. Litigation involving Hulu examined whether Facebook cookies combined with watch-page URLs effectively disclosed a person’s video-viewing activity. Hulu ultimately won summary judgment because the evidence did not establish the required knowing disclosure, illustrating how technically dependent VPPA liability can be.

The theory remains active. More recent litigation has produced novel class-certification developments, while courts continue debating who qualifies as a VPPA “consumer,” what constitutes personally identifiable information and which online businesses qualify as video service providers.

In other words, plaintiffs are not claiming that a pixel is literally a 1960s telephone tap or that streaming is literally renting a VHS cassette. They argue that the functional conduct falls within technology-neutral statutory language such as “intercept,” “communication,” “personally identifiable information,” or disclosure of video-viewing information.

The results are decidedly mixed. It would be inaccurate to say either that businesses routinely lose these cases or that courts have rejected the theories.

Plaintiffs have achieved meaningful successes. Courts have allowed CIPA/session-replay claims to survive motions to dismiss. The court in Greenley v. Kochava permitted a broad CIPA pen-register theory to proceed. In Frasco v. Flo Health (Northern District of California), a unanimous jury found Meta violated CIPA Section 632 by intentionally eavesdropping on confidential app communications without consent—an unusually significant plaintiff-side trial result.

But judges are also imposing limits. A notable example is Gabrielli v. Insider (Southern District of New York), where the court rejected a CIPA pen-register claim involving an advertising analytics tracker collecting IP addresses. The decision was viewed as potentially resetting what had become a rapidly expanding pen-register theory.

VPPA litigation similarly produces both plaintiff and defense victories. Hulu, for example, ultimately obtained summary judgment with prejudice despite years of litigation.

The larger business problem is therefore litigation economics rather than certainty of plaintiff victory. A claim does not have to be likely to prevail at trial to be expensive. Discovery into website configurations, vendor contracts, consent records and data flows can itself be costly. Reporting on these cases has even noted judicial concern about plaintiffs or “testers” searching websites for alleged violations in pursuit of quick settlements.

Thus, many demand letters are economically significant even where the underlying legal theory is contestable. The current environment is better characterized as high-volume, unsettled litigation with substantial early-settlement pressure, not as settled law establishing that ordinary pixels violate CIPA.

Notably, courts have also begun to scrutinize litigation brought by serial privacy plaintiffs. In July 2026, the U.S. District Court for the Central District of California declared a plaintiff who had filed 29 lawsuits between 2021 and 2026—14 of which asserted claims under CIPA—to be a vexatious litigant. The court imposed a pre-filing review requirement prohibiting the plaintiff from filing, without prior court authorization, “any new civil litigation or pleading in the United States District Court for the Central District of California that asserts claims under the California Invasion of Privacy Act . . . or related to consumer digital privacy statutes.” (See Vivek Shah v. Crain Communications, Inc.) This decision provides another example of judicial scrutiny of high-volume privacy litigation, particularly where the same plaintiff repeatedly asserts similar statutory claims against multiple businesses. I have several clients who received demand letters from Vivek Shah who were happy to hear about this court’s order!

Being a small business, B2B, or headquartered outside California is not a reliable shield against receiving a demand letter. Recent reporting describes thousands of templated CIPA demands being directed at businesses of every size based on routine analytics and marketing tools. In fact, my latest clients to receive such demand letters were a local San Diego surf board maker, a San Diego based surf retail company and a small local machine shop.

The reason is partly technological. A plaintiff’s firm or tester does not necessarily need to identify a famous consumer brand. Websites can be systematically examined for Meta Pixel, Google Analytics, session replay, chat software and similar scripts.

Also, California website privacy obligations have historically reached well beyond companies physically located in California. California’s online privacy requirements can apply to operators outside the state when they collect information from California residents.

There is another important distinction: a company can fall outside CPRA/CCPA applicability thresholds yet still face a CIPA claim. The statutes have different scopes and requirements. “We aren’t subject to the CPRA” therefore does not answer the question of whether the business is vulnerable to a CIPA claim. That makes the risk profile much broader than many small-business owners assume.

How Plaintiffs Describe the Transaction

The CIPA theory reframes a normal page load. From the answer to the second question above:

The CIPA theory essentially reframes that transaction as:

Visitor

→

Website

→

+ Third-Party Tracker

rather than simply:

Visitor

→

Website

Part 2

Cookie Banners, Privacy Policies and “Do Not Sell or Share My Personal Information”

Why a pop-up banner and a template policy can leave a website exposed, and what “sale or share” means under CCPA/CPRA.

Many businesses buy a cheap cookie banner plugin and assume they are safe. Legally speaking, what is the difference between a simple pop-up banner and the "Zero-Cookie Load" standard that courts and regulators are looking for?

This is really comparing apples to oranges. A cookie banner is primarily a notice/interface; “Zero-Cookie Load” describes a technical configuration intended to prevent nonessential tracking from occurring before the required consent is obtained. So, you might say that the key difference is what the website actually does before the visitor makes a choice.

A simple pop-up cookie banner may appear when a visitor arrives and offer “Accept,” “Reject,” or “Manage Preferences.” But the mere existence of that banner does not mean tracking has been stopped. On many websites, Google Analytics, Meta Pixel, advertising tags, session-replay software, and similar technologies begin loading as soon as the page loads—before the visitor has clicked anything. If that happens, information may already have been transmitted to third parties by the time the visitor selects “Reject.”

By contrast, under a “Zero-Cookie Load” or prior-blocking approach, nonessential tracking technologies are prevented from firing until the visitor has provided whatever consent is legally required. The sequence is therefore:

Simple banner:

Page loads → tracking scripts fire → data may be transmitted → banner appears → visitor chooses.

Zero-Cookie Load/prior blocking:

Page loads → nonessential trackers remain blocked → banner appears → visitor chooses → permitted trackers activate.

The term “Zero-Cookie Load” can be misleading, however. It is not a defined standard in the CCPA/CPRA or CIPA, and it should not be understood to mean that literally no cookies can be placed when a page loads. Strictly necessary technologies—such as cookies required for security, authentication, shopping-cart functionality, or maintaining a user’s privacy preferences—may operate without the same consent treatment. The concern is principally nonessential analytics, advertising, profiling, and similar tracking technologies.

The distinction is particularly important under CIPA because timing definitely matters. In Javier v. Assurance IQ, LLC, the Ninth Circuit Court of Appeals held that California law requires prior consent to the interception of a communication; consent obtained after the interception cannot retroactively authorize it. Thus, if a tracking technology has already received the visitor’s communication before the visitor encounters or accepts the consent mechanism, the banner may have appeared too late to provide the consent defense the business expected.

For CCPA/CPRA, the analysis is somewhat different. California generally does not impose a universal GDPR-style requirement that all analytics and advertising cookies be blocked until affirmative opt-in consent. Instead, much of the California framework centers on notice and the consumer’s right to opt out of the sale or sharing of personal information, including sharing for cross-context behavioral advertising. A business subject to those requirements must ensure that its technical systems actually honor the consumer’s choice, including applicable opt-out preference signals such as Global Privacy Control. California enforcement has also emphasized symmetrical choices: if “Accept All” takes one click, rejecting should not be intentionally harder through dark-pattern design.

So the key compliance principle is not merely “display a banner.” It is: The site’s actual network behavior must correspond to the visitor’s legally required choice, and the timing of tracker activation matters.

A simple cookie banner provides little protection against CIPA claims if the website’s tracking technologies have already transmitted information before the visitor is given a legally effective choice. A prior-blocking or “Zero-Cookie Load” configuration goes further by technically preventing nonessential trackers from firing until the required consent has been obtained. Although California law does not establish “Zero-Cookie Load” as a universal statutory standard, prior blocking can materially reduce CIPA litigation risk because courts have held that consent obtained after an alleged interception cannot retroactively authorize the interception.

A $20 plugin that displays attractive consent language while Meta, Google and other scripts fire underneath it can therefore provide little protection.

From a litigation perspective, the biggest problem is generally a mismatch between what the policy says and what the website actually transmits.

The most important deficiencies include:

  • failing to identify categories of information actually collected through cookies, pixels, SDKs, session replay and similar technologies;
  • failing to disclose third-party analytics and advertising collection;
  • failing to explain purposes of collection and disclosure;
  • failing to accurately disclose sale or sharing for cross-context behavioral advertising;
  • saying information is not “sold” when advertising technology produces data transfers potentially falling within California’s much broader statutory definition;
  • failing to explain applicable opt-out rights and provide functioning privacy-choice mechanisms;
  • failing to recognize required browser-based preference signals such as Global Privacy Control where applicable;
  • failing to address sensitive information where trackers can capture health, financial or similarly sensitive activity;
  • failing to maintain appropriate vendor/service-provider contractual restrictions; and
  • leaving policy language unchanged after marketing personnel add or reconfigure trackers.

These are not theoretical concerns. Recent California enforcement has focused on broken opt-outs, failure to honor Global Privacy Control, inadequate vendor restrictions and incomplete privacy disclosures.

The underlying lesson from tracking litigation is especially important: draft the policy from a technical data-flow inventory, not from a generic privacy-policy template. Older VPPA litigation demonstrated how liability questions can turn on information leaking through URLs, cookies and social plug-ins that policy drafters may not even realize are transmitting data.

The short answer is “Yes.”

California’s definition of “sale” is much broader than the ordinary English meaning of selling a customer list for money. It can include disclosure or transfer of personal information for monetary or other valuable consideration. California analysis has specifically recognized that exchanging browsing, geolocation or network activity for advertising or analytics services can potentially qualify.

The CPRA also separately introduced “sharing,” principally addressing disclosure for cross-context behavioral advertising. Consequently, a transaction can potentially constitute “sharing” even if nobody pays the website owner cash for the information.

The analysis does not depend on whether the business receives money from Meta or transmits a consumer’s name. Online identifiers and browsing activity may themselves constitute personal information. Accordingly, a business using Meta Pixel for retargeting should carefully evaluate any representation that it “does not sell or share personal information” and, where applicable, provide and technically honor consumers’ rights to opt out of sale or sharing, including through Global Privacy Control. (See Cal. Civ. Code §§ 1798.120, 1798.135, 1798.140.)

Simple Banner vs. Zero-Cookie Load

The difference is what the website actually does before the visitor makes a choice. The two sequences, from the answer above:

Simple banner:

Page loads

→

tracking scripts fire

→

data may be transmitted

→

banner appears

→

visitor chooses.

Zero-Cookie Load/prior blocking:

Page loads

→

nonessential trackers remain blocked

→

banner appears

→

visitor chooses

→

permitted trackers activate.

Part 3

Can You Keep Google Analytics and Meta Pixel Data and Still Be Compliant?

How the attorney advises clients to keep the marketing measurement that matters while closing off uncontrolled data transmission.

Many businesses rely heavily on tools like Google Analytics and Meta pixels to run their company, and blocking those trackers hurts their marketing data. How are you advising clients to balance their aggressive marketing and sales goals with strict legal compliance?

The main objective for my clients is to preserve the marketing functions that have measurable value while eliminating uncontrolled data transmission.

A workable approach is to inventory every pixel, tag, SDK and cookie; determine exactly what each sends and to whom; classify it as necessary, analytics, advertising/retargeting or another purpose; and then configure the consent-management platform and tag manager so those classifications actually control execution. Current compliance guidance specifically emphasizes tracker inventories, vendor vetting, contracts, consent/opt-out settings, removal of obsolete trackers and technical mechanisms that enforce user choices. Once these steps have been completed, I make sure my clients have a comprehensive and detailed Privacy Policy outlining and describing all pixels, tags, SDKs and cookies used.

For higher-risk technologies—particularly Meta retargeting, session replay, chat recording, detailed event tracking and pixels on pages containing sensitive or video-related information—I would consider blocking transmission until the appropriate consent/choice mechanism has been satisfied. For lower-risk analytics, the answer may differ depending on configuration, contractual restrictions, jurisdiction and whether the data is used solely for the business’s purposes.

I’d also separate analytics from behavioral advertising rather than putting everything in one “cookies” bucket. A business may be able to preserve substantial first-party measurement while restricting cross-context advertising activity for users who opt out. First-party data strategies are increasingly important precisely because they can reduce dependence on third-party tracking, although they still require appropriate transparency and consent analysis.

Finally, compliance needs to be tested at the network level, not merely by reading the privacy policy or clicking the banner. Regulators have specifically encountered sites where the interface said an opt-out had occurred while pixels continued sending information behind the scenes.

The question for my clients in 2026 is:

“Before and after the visitor makes a privacy choice, exactly which HTTP requests leave that person’s browser, which third parties receive them, what information is contained in those requests, what are those recipients contractually permitted to do with it, and does that behavior match our disclosures and the visitor’s choice?”

That question simultaneously addresses much of the exposure arising under CIPA interception/pen-register theories, VPPA pixel litigation, and CPRA/CCPA sale/share and opt-out enforcement. The current litigation literature likewise emphasizes effective notice (ie a detailed Privacy Policy), enforceable consent, script governance and auditable records rather than relying on policy language alone.

One qualification: this area remains unusually unsettled. In particular, whether ordinary website tracking constitutes a CIPA “pen register,” when a tracker becomes an impermissible third-party interceptor, and when a particular identifier constitutes VPPA personally identifiable information remain heavily fact- and jurisdiction-dependent. Recent decisions show both significant plaintiff successes and meaningful judicial pushback.

"Before and after the visitor makes a privacy choice, exactly which HTTP requests leave that person's browser, which third parties receive them, what information is contained in those requests, what are those recipients contractually permitted to do with it, and does that behavior match our disclosures and the visitor's choice?"

Part 4

What to Do If Your Business Receives a CIPA Demand Letter

The preferred sequence, in the attorney’s words, and the things not to do in the first days after a letter arrives.

The preferred sequence:

Preserve

→

document

→

remediate promptly

→

test

→

document the remediation.

If a business owner opens their mail tomorrow and finds one of these demand letters regarding their website, what are the absolute first things they should—and shouldn't—do?

The first rule of thumb is: do not ignore the letter, but do not panic and assume that the alleged violation has been established. A CIPA demand letter is an allegation, not a judicial determination of liability. Many current website-tracking demands involve legal theories that remain contested, and the viability of a claim may depend heavily on the particular technology involved, the information actually transmitted, the timing of the transmission, consent, standing, and the specific CIPA provision being invoked.

At the same time, the company should take the letter seriously because receipt of a sufficiently concrete demand letter may trigger a duty to preserve relevant evidence. Under California law, the preservation obligation can arise before a lawsuit is filed when the party is objectively on notice that litigation is reasonably foreseeable. The California Court of Appeal has explained that this means litigation is “probable and likely to arise” from the dispute, rather than merely a possibility. (See Victor Valley Union High Sch. Dist. v. Superior Court, 91 Cal. App. 5th 1121, 1138–39 (2023).)

A demand letter expressly asserting a CIPA violation and threatening litigation can therefore be highly significant to the preservation analysis. Once litigation is reasonably foreseeable, relevant electronically stored information should not simply be deleted or allowed to disappear through routine retention practices. California Code of Civil Procedure §2023.030(f)’s safe harbor for Electronically Stored Information (“ESI”) lost through routine, good-faith operation of an electronic information system does not protect destruction of ESI occurring when the party was already under a duty to preserve the evidence.

That does not mean the company should leave the allegedly defective website configuration running. Preservation and remediation are two different things. If a Meta Pixel, session-replay tool, analytics script, chat application, or other tracker appears to present a legitimate concern, there is ordinarily no reason to continue the potentially problematic conduct merely to preserve evidence.

Instead, the preferred sequence is:

Preserve → document → remediate promptly → test → document the remediation.

Before making material changes, the company and its counsel should preserve enough evidence to reconstruct how the website operated at the relevant time. Depending upon the claim, that may include the privacy policy and cookie notice in effect on the date of the alleged visit; consent-management-platform settings and logs; Google Tag Manager containers and version history; Meta Pixel and Google Analytics configurations; source code and relevant scripts; server logs; screenshots of the consent flow; vendor agreements; and, where feasible, a network-level capture showing which HTTP requests leave the browser, which domains receive them, and what information is transmitted before and after the visitor makes a privacy choice.

Once that evidence has been adequately preserved, the company should promptly correct any genuine deficiency it identifies. Preservation does not ordinarily require a business to continue conduct that may create additional exposure. Indeed, continuing a questionable tracking configuration after receiving actual notice of the alleged problem could create unnecessary additional risk.

Counsel should also consider sending a preservation notice to the claimant and claimant’s attorney. A prospective plaintiff’s preservation obligations can likewise arise before filing suit when litigation is reasonably anticipated. Depending upon the allegations, potentially important claimant-side evidence could include the device and browser used for the visit, cookies and local storage, browser history, screenshots, HAR or other network captures, the precise URLs visited, date and time of the alleged visit, consent selections, Global Privacy Control settings, browser extensions, privacy settings, IP information, and the scanning or testing methodology used to identify the alleged violation. California’s preservation standard focuses on whether litigation is reasonably foreseeable rather than simply whether a complaint has already been filed.

The company should then have counsel and appropriate technical personnel reproduce the alleged conduct. The central questions are factual: What happened when the claimant visited the site? Which tracker fired? When did it fire? What information was transmitted? To whom? Did the behavior differ before and after consent? Did the claimant reject tracking or transmit an opt-out preference signal? And does the technical evidence actually support the allegations in the demand letter?

There are also several things the company should generally not do. It should not contact the claimant directly to apologize, explain the website’s operation, admit that tracking was unlawful, or negotiate a payment before the claim has been evaluated. It should not indiscriminately delete trackers, logs, tag-manager histories, consent records, or prior versions of its privacy policy without first preserving relevant evidence. And it should not assume that because a tracker was present, a CIPA violation necessarily occurred. Courts continue to disagree about important aspects of these claims, including whether particular tracking technologies satisfy CIPA’s statutory definitions and whether plaintiffs have suffered an injury sufficient to establish standing.

Finally, the company should promptly check its cyber, privacy, technology E&O, or other potentially applicable insurance policies. Notice provisions can be important, and coverage questions should be evaluated before the company incurs substantial defense expenses or negotiates a settlement.

The practical advice is therefore:

Preserve quickly, remediate quickly, and investigate before responding. Receipt of a demand letter can place a business on notice of reasonably foreseeable litigation and therefore create preservation obligations under California law, but that obligation does not require the company to leave potentially problematic tracking technology running. Preserve sufficient evidence to reconstruct the historical website configuration, correct any legitimate deficiency, test the corrected configuration, and have counsel evaluate the claim based upon what the website actually transmitted—not simply what the demand letter alleges.

This formulation also avoids suggesting that a business should freeze its website in a potentially noncompliant state, while recognizing the preservation rule established in the Victor Valley Union High Sch. Dist. case.

Do

Preserve quickly, remediate quickly, and investigate before responding. Receipt of a demand letter can place a business on notice of reasonably foreseeable litigation and therefore create preservation obligations under California law, but that obligation does not require the company to leave potentially problematic tracking technology running. Preserve sufficient evidence to reconstruct the historical website configuration, correct any legitimate deficiency, test the corrected configuration, and have counsel evaluate the claim based upon what the website actually transmitted—not simply what the demand letter alleges.

Don’t

There are also several things the company should generally not do. It should not contact the claimant directly to apologize, explain the website's operation, admit that tracking was unlawful, or negotiate a payment before the claim has been evaluated. It should not indiscriminately delete trackers, logs, tag-manager histories, consent records, or prior versions of its privacy policy without first preserving relevant evidence. And it should not assume that because a tracker was present, a CIPA violation necessarily occurred. Courts continue to disagree about important aspects of these claims, including whether particular tracking technologies satisfy CIPA's statutory definitions and whether plaintiffs have suffered an injury sufficient to establish standing.

Part 5

How to Audit Your Website for Trackers and Cookie Compliance This Week

The one step to take this week, and the four conditions a tracking audit should test.

The four states to test

1

when a visitor first arrives and takes no action on the cookie banner

2

after the visitor accepts tracking

3

after the visitor rejects tracking

4

when the visitor uses an opt-out preference signal such as Global Privacy Control

Without getting too technical, what is the very first step a business owner reading this should take this week to audit their own website and figure out if they are currently at risk?

The first step is surprisingly simple: find out what your website is actually sending to third parties when someone visits it. Do not assume that because you have a privacy policy or cookie banner, your website is operating the way those documents say it does.

Have someone perform a basic website tracking audit that (a) identifies every third-party technology operating on the site—such as Meta Pixel, Google Analytics, advertising tags, session-replay software, chat tools, embedded video, and similar technologies—and (b) determines what information is transmitted, who receives it, and, importantly, whether those transmissions occur before the visitor has an opportunity to consent or opt out.

The audit should test the website under several conditions: when a visitor first arrives and takes no action on the cookie banner, after the visitor accepts tracking, after the visitor rejects tracking, and, where applicable, when the visitor uses an opt-out preference signal such as Global Privacy Control. The goal is not simply to identify which cookies appear in the browser. It is to determine what information actually leaves the visitor’s browser and whether the website’s behavior changes when the visitor exercises a privacy choice.

Once you know that, compare the results against what your privacy policy and cookie banner actually say. If the policy says, for example, that you do not “sell or share” personal information, but the website is transmitting browsing information through Meta Pixel for retargeting, that deserves immediate attention. Likewise, if clicking “Reject All” still allows advertising or other nonessential trackers to fire, the banner may be providing the appearance of compliance without actually implementing the visitor’s choice.

For businesses concerned about CIPA litigation, I would pay particular attention to third-party technologies that activate immediately when a page loads and receive information about the visitor or the visitor’s interaction with the site before any consent is obtained. That does not automatically mean the technology violates CIPA, but it identifies the type of data flow that should be reviewed more carefully.

So, if a business owner does only one thing this week, it should be this: have the website tested from the visitor’s side and create an inventory of every third party receiving information from the browser, what it receives, when it receives it, and whether the visitor’s privacy choices actually stop the transmission.

That relatively simple exercise frequently reveals the most important issue: the business’s privacy policy says what the company believes its website does; the audit shows what the website actually does. The gap between those two is where much of today’s website privacy risk begins.

Quick Answers

FAQ on Website Privacy & Cookie Compliance

Why are so many businesses suddenly receiving legal letters about their websites?

There is a wave of class-action lawsuits and demand letters targeting business websites—with over 800 claims filed in California alone last year. Law firms use automated bots to scan sites for tracking tools like the Meta Pixel, Google Analytics, or session-replay software. If these trackers capture user data before a visitor explicitly consents, plaintiffs’ attorneys are successfully alleging this violates state wiretapping laws and federal privacy laws.

A pixel is a tiny, invisible piece of code placed on a website that tracks how visitors interact with the site (such as pages viewed, buttons clicked, or items added to a cart). This data is often sent back to platforms like Meta, LinkedIn, or Google to help businesses measure ad performance and target their marketing.

Yes. Even if your business is based in another state, if your website is accessible to residents in strict privacy states like California, you can be sued under those laws. Furthermore, plaintiffs are invoking federal laws like the Video Privacy Protection Act (VPPA) and the Electronic Communications Privacy Act (ECPA), which apply nationwide. Other states, including Florida, Pennsylvania, and Illinois, are now seeing their own surge in pixel-tracking litigation.

Not necessarily. A banner that simply says “We use cookies” and makes the user click “OK” is no longer enough. Regulators and courts now enforce “Zero-Cookie Load.” This means your website must physically block all non-essential tracking scripts from loading until the user actively clicks “Accept.” If your trackers fire in the background while the banner is just sitting there, you are out of compliance.

No. A privacy policy acts as a notice, not a shield—and relying on a generic, template policy (like the ones built into WordPress or basic website builders) is a major liability. Standard templates usually fail to explicitly name the third-party platforms tracking your users (like Meta or Google) and lack mandatory “Do Not Sell or Share My Personal Information” clauses required by state laws. If your policy says “we do not sell your data,” but your site uses marketing pixels for retargeting, plaintiffs will use your own policy against you to claim deceptive practices.

Speak to your web developer or agency about conducting a technical cookie audit. You need to identify every tracker running on your site, update your Privacy Policy to reflect your actual data practices, and implement a specialized Consent Management Platform (CMP) to ensure all non-essential tracking is strictly gated behind user consent.

What a CIPA Demand Letter Looks Like (Example)

Below is an example of the kind of letter businesses are receiving. Bracketed items are placeholders.

RE: Notice of Violation of California Invasion of Privacy Act (Cal. Penal Code §§ 630 et seq.) and California’s Trap and Trace Statute (Cal. Penal Code §§ 638.50 et seq.)

Dear [Company Name],

This firm represents [Claimant Name] ("Client") in connection with privacy violations occurring on your website located at [Website URL] (the "Website").

During Client's visit, the Website caused Client's browser to transmit electronic communications and identifying behavioral data to Meta Platforms, Inc. via the Meta Pixel — a JavaScript tracking tool embedded in your website — prior to obtaining Client's consent.

This conduct constitutes a violation of Cal. Penal Code § 631 (wiretapping) and § 638.51 (pen register/trap and trace).

Statutory damages for these violations are $5,000 per violation under § 631; and $5,000 per violation under § 638.51.

To resolve this matter, Client requests written confirmation within 21 days that the Meta Pixel has been disabled or placed behind a strict consent gate, together with a settlement offer. Failure to respond will result in the filing of a class action complaint without further notice.

Official Legal Resources

Primary sources from state and federal agencies. Each link opens in a new tab.

Latest on Web Privacy

New guidance on cookie consent, tracking and privacy compliance from the KWSM team.

What Your Business Website Needs for Privacy Compliance in 2026
Stephen Wagner

What Your Business Website Needs for Privacy Compliance in 2026

For years, data privacy lawsuits felt like a problem reserved for massive tech enterprises. But as of 2026, the landscape has fundamentally shifted. With 20 U.S. states now enforcing comprehensive data privacy laws, small and medium-sized businesses (SMBs) are increasingly in the crosshairs of aggressive legal action. As discussed in

Read More »
The Legal Risks of Website Tracking, Explained by a Privacy Attorney
KWSM Team

The Legal Risks of Website Tracking, Explained by a Privacy Attorney

Across the country, small and mid-sized businesses are receiving formal legal demand letters alleging that standard marketing pixels—like Google Analytics, Meta Pixels, and session-replay software—violate 1960s state wiretapping statutes. To help business owners cut through the noise, separate myth from reality, and protect their digital infrastructure without destroying their marketing

Read More »

Our Guarantee

Experience our collaborative 6-week strategy process before committing to a long-term engagement.

Find out what your website is really sending.

Fill out this form to speak to a member of our team about a website tracking audit, consent management setup, and bringing your privacy policy in line with what your site actually does.

Know what your website is sending before someone else does.

This page is provided for general informational purposes only and does not constitute legal advice, nor does it create an attorney-client relationship with Karen Batcher, Alliance Data Privacy Solutions, Inc., or KWSM. Laws, regulations and court decisions in this area change quickly. Consult an attorney about your specific situation. KWSM is a digital marketing agency, not a law firm.

Last reviewed: September 30, 2026

Video Studio Day

Atlanta - Aug 21, 2026
Orange County - Aug 19, 2026

Create videos for your website or social media channels.

Core Values at KWSM a digital marketing agency