US Cookie Consent Rules in 2026: What Your Website Needs

State privacy laws, tracking risk, and the consent platforms that help manage both: a guide for developers, agencies, and site owners.
US Cookie Consent Rules in 2026: What Your Website Needs
David Jenkin
By , Senior B2B Reporter

US websites don’t universally need a cookie banner. The notice, consent, and opt-out controls your site needs depend on applicable privacy laws and how you collect and share visitor data.

This guide explains US cookie consent requirements, Global Privacy Control, and the tracking configurations site owners and agencies should check.

US Cookie Consent Requirements: Key Findings

  • US cookie consent requirements depend on applicable laws and how your site uses visitor data. A banner alone doesn't establish compliance.
  • Twelve states require covered businesses to recognize qualifying browser opt-out signals, with California also requiring visible confirmation that the signal was processed.
  • Five California enforcement actions totaled more than $19 million and highlighted failures in opt-out handling, vendor contracts, and limits on data use.

Five years ago, website privacy compliance in the US meant California. The patchwork of US website privacy regulations now extends across more than twenty states; four more passed privacy laws in 2026, and thresholds keep dropping.

Federal privacy proposals don’t replace businesses’ obligations under existing laws. Congress introduced the SECURE Data Act (H.R. 8413) in April 2026, and a House subcommittee held a hearing on it in June. Website owners should continue to assess applicable state requirements and any federal rules specific to their industry or audience. 

Privacy compliance requirements for websites vary widely by state, but the controls that affect your site make for a short list.

The State Rules That Change What You Build

Nearly every state law gives residents the same core rights: access, deletion, correction, portability, opt-out, and freedom from discrimination for exercising them.

For a website, that translates into four things:

  1. A privacy notice that describes what you collect and why, updated at least annually
  2. A working opt-out mechanism for sale, sharing, and targeted advertising, reachable from every page
  3. Opt-in consent before processing sensitive data, and before processing data from minors
  4. Recognition of browser-level opt-out signals in the states that require it

A few states break the pattern:

  • Texas has no numerical threshold but generally exempts small businesses, except when they sell sensitive data
  • Montana and Rhode Island have the lowest thresholds in the country. Montana starts at 25,000 consumers; Rhode Island reaches businesses handling 10,000 residents' data (if more than 20% of revenue comes from selling it)
  • Maryland bans the sale of sensitive personal information outright rather than requiring consent for it
  • Florida's law reaches only very large technology companies, so most sites can set it aside

California added new regulations on top of this in January 2026 covering automated decision-making, risk assessments, and cybersecurity audits, which has a big impact on hiring or lending algorithms. They have almost nothing to do with your consent banner, and the compliance dates run out to 2030.

Global Privacy Control Requirements by State

Global Privacy Control (GPC) lets visitors communicate an opt-out preference through a supported browser or extension. Covered businesses must apply that preference to the data uses specified by the relevant law, such as sales, sharing, or targeted advertising. It does not automatically mean rejecting every cookie. 

The table below summarizes state requirements for recognizing qualifying opt-out signals. Dates refer to signal recognition rather than the broader privacy law’s effective date. Business thresholds and exemptions still apply.

State Opt-out signal requirement effective Key qualification
CaliforniaAugust 14, 2020The original regulations required recognition of qualifying browser privacy controls. GPC-specific enforcement guidance followed in 2021.
ColoradoJuly 1, 2024GPC is on the state’s list of recognized mechanisms for opting out of sales and targeted advertising.
ConnecticutJanuary 1, 2025Covered businesses must honor qualifying signals for sales and targeted advertising.
DelawareJanuary 1, 2026Signal recognition became mandatory one year after the broader law took effect.
MarylandOctober 1, 2025The law excludes processing before April 1, 2026, despite its earlier effective date and signal deadline.
MinnesotaJuly 31, 2025Covered controllers must honor qualifying universal opt-out requests, subject to statutory exceptions.
MontanaJanuary 1, 2025Signals must meet statutory conditions, including reflecting an affirmative consumer choice.
NebraskaJanuary 1, 2025Browser-based requests operate through authorized-agent provisions, with verification and technical conditions.
New HampshireJanuary 1, 2025A qualifying signal takes precedence over a conflicting site-specific setting, though the business may explain the conflict.
New JerseyJuly 15, 2025The signal requirement began six months after the broader law took effect.
OregonJanuary 1, 2026The requirement covers qualifying organizations, including nonprofits, for sales and targeted advertising.
TexasJanuary 1, 2025Browser-based requests operate through authorized-agent provisions, subject to statutory conditions.

Since January 1, 2026, California has also required businesses to display whether they have processed an opt-out preference signal. Your implementation should both apply the preference and give the visitor a visible indication of its status. 

Will Newmark, Senior Legal Counsel at Usercentrics, says the only workable approach is a single setup that adapts by location.

"One configuration, applied differently by geolocation — that's the only version of this that holds.” He says you need a consent layer that detects where the visitor is and applies the right model, with framework updates maintained for you rather than re-implemented by your dev team each time a state moves.

“California is the baseline, not a special case,” he adds.

Who Is Getting Fined, and What They Got Wrong

five california penalties chart

California’s CCPA penalties can reach $2,663 per violation, or $7,988 for intentional violations and violations involving personal information belonging to consumers the business knows are under 16. These inflation-adjusted limits took effect on January 1, 2025. 

Five enforcement actions illustrate the consequences of ineffective opt-outs, missing contractual protections, and improper data use: 

  • Healthline, $1.55 million: Continued sharing personal information with advertising partners after consumers opted out. The case also involved disclosures that suggested medical diagnoses and a lack of privacy protections in advertising contracts. 
  • Tractor Supply, $1.35 million: Failed to provide effective opt-outs, including through GPC, and omitted required privacy information for consumers and job applicants. Its contracts with other companies also lacked required protections. 
  • Honda, $632,500: Required excessive verification for certain privacy requests, presented unequal privacy choices, and failed to produce required contracts with advertising technology companies. 
  • Disney, $2.75 million: Failed to apply opt-outs across associated devices and streaming services. GPC requests were limited to the device sending the signal, even when the consumer was logged into an account. 
  • General Motors, $12.75 million: Sold drivers’ location and driving data collected through OnStar to data brokers. The case also addressed retaining and using data beyond its original purpose. 

For website teams, these cases show why testing must cover what happens after an opt-out - which data transfers stop, how the choice applies to known users, and what protections govern third-party recipients. 

Why a CCPA-Compliant Website Can Still Face a CIPA Claim

Everything in the previous section started with a regulator. An agency opened an investigation, the business responded, and a settlement landed months or years later.

CIPA claims can arise through private litigation without a prior regulatory investigation. A claimant may use evidence of third-party tracking to allege unlawful interception, although sending data before a visitor interacts with a banner does not, by itself, establish a violation. The legal basis and the information collected matter. 

CCPA vs CIPA: What Each Law Governs

CCPA and CIPA get discussed together because both involve tracking. They regulate different conduct and fire on different conditions.

The CCPA (California Consumer Privacy Act), enforced by a regulator:

  • Governs the sale and sharing of personal information
  • Enforced by the California Attorney General and CalPrivacy
  • Triggered by inadequate notice or an opt-out that doesn't work
  • Civil penalties of $2,663 or $7,988 per violation, assessed by a regulator
  • No private right of action outside certain data breach claims

CIPA (California Invasion of Privacy Act):

  • Regulates interception of communications and certain surveillance practices. 
  • Website claims have involved alleged interception of communication contents under Section 631 and alleged use of pen registers or trap-and-trace devices under Section 638.51. 
  • SB 690, signed on September 30, 2026, will restrict private website-tracking claims under Section 638.51 when its amendments take effect on January 1, 2027. 
  • Private claims involving alleged interception of communication contents remain possible. 

A CCPA-compliant site gives clear notice, offers a working opt-out, and honors GPC signals. It can do every one of those things while analytics, advertising pixels, and a chat widget load on page one. Under CIPA, that sequence is what plaintiffs point to.

A site can pass a regulator's audit and receive a demand letter the following week.

How the Letters Work

The letters read as though someone studied your business but, almost always, nobody did.

"Most of these letters aren't the product of anyone reviewing your business," Newmark says. "They're templated and produced at volume." He describes a largely paralegal-driven process: capture network traffic, spot a tracking script, send a near-identical letter citing CIPA Section 631 or 638.51, with a settlement demand and 20 to 30 days to respond.

What makes it work, he explains, is that CIPA carries a private right of action with no regulator, no cure period, and no requirement to show harm. "At $5,000 per violation, the demand is priced against your cost of defense, not the merits."

You don't need customers or an office in California, just having a publicly accessible site can draw a claim, though jurisdiction and California contacts still matter.

Courts have yet to resolve whether a statute written for telephone wiretapping reaches website software. Rulings have gone in both directions, appeals are pending in California, and a definitive answer is unlikely to arrive soon.

Our reporting on why small businesses are getting CIPA demand letters examines how these claims affect smaller website operators.

Two things worth checking before you need them:

  • Your arbitration clause and class action waiver: Class certification is what turns individual $5,000 claims into eight-figure exposure, so an enforceable waiver changes settlement leverage considerably.
  • How users actually accept your terms: A weak assent process cuts the other way. An agreement nobody meaningfully accepted can make your consent defense worse rather than better.

What to Do If One Arrives

The first 72 hours are the most critical. Here’s what you can do:

  1. Preserve the letter and relevant evidence. Ask counsel whether to issue a formal litigation hold and suspend routine deletion of logs, tag configurations, and consent records.
  2. Avoid contacting the claimant or their firm until qualified counsel has reviewed the demand. Once retained, counsel can handle further communication.
  3. Do not respond to or pay the demand before counsel has evaluated the allegations, available defenses, and settlement position.
  4. Preserve evidence of the banner and tag configuration before changing it. Counsel can advise what to document and when to begin remediation.
  5. Capture a non-destructive audit of the current configuration, listing third-party requests made on page load, the consent state at the time, and any data transmitted before consent.
  6. Identify the sending firm. Counsel familiar with it may understand its strategy, track record, and likely posture.
  7. Review whether your cyber liability or general liability policy may cover the claim, and notify your insurer or broker within any required timeframe. Late notice can affect coverage.
  8. Check what the claimant actually did on your site. A page visit presents different facts from submitting a form, running a search, or opening a chat. Section 631 claims generally depend on the alleged interception of communication contents, while §638.51 claims concern routing, addressing, or signaling data.

Fixing the site afterward isn’t an admission that the earlier configuration was unlawful. Businesses update compliance practices constantly as laws, technology, and risk tolerance evolve.

What that fix involves is mostly a question of load order.

A Lower-Risk Website Configuration

A consent banner can display the right language and record what a visitor clicks without controlling every tracker behind it. On a poorly configured site, GA4, the Meta Pixel, or a chat widget might connect to a third party before the visitor makes a choice.

That gap between page load and consent is central to many CIPA demands. Reducing it requires coordinated consent logic, tag controls, and testing (not merely adding a banner).

Technical Requirements for a Lower-Risk Setup

Meeting privacy compliance requirements for websites cannot guarantee protection from a CIPA claim, but a conservative technical setup should include the following:

  • The CMP or consent logic initializes early enough to set the correct state before dependent tags can transmit data.
  • For a conservative pre-consent posture, nonessential third-party tags remain blocked until the visitor affirmatively consents. Closing the banner or continuing to browse does not grant affirmative consent.
  • Google tags follow the Basic or Advanced Consent Mode configuration the business has deliberately selected.
  • The CMP detects GPC during initialization, applies the relevant opt-out state, and displays confirmation where required.
  • Consent preferences are stored with an appropriate expiry period and tested across browsers, including Safari. No first-party storage should be assumed to survive Intelligent Tracking Prevention indefinitely.
  • Consent choices are written to timestamped, exportable records that identify the banner version and categories accepted or rejected.
  • The site is rescanned and retested whenever tags, templates, plugins, or campaign tools change.

Loading the GTM container doesn’t mean every tag inside it fires. GTM can load while consent defaults and tag-level checks determine how individual tags behave. The risk arises when consent initializes too late, tags lack the necessary checks, or third-party scripts bypass the consent setup entirely.

An EU configuration also doesn’t automatically cover the US because GDPR implementations tend to begin from an opt-in model, while most US state laws use opt-out rights and require additional handling for signals such as GPC. Separate regional rules have to be configured and tested, even when one CMP manages both.

How Consent Mode Affects Google Ads Measurement

Consent Mode v2 is often described as mandatory when its actual role is more specific. Google requires a certified CMP for publishers using AdSense, Ad Manager, or AdMob to serve personalized ads in the EEA, UK, and Switzerland. That requirement doesn't apply merely because a site advertises to US visitors.

Consent Mode can still help advertisers communicate user choices to Google and limit the measurement lost when tracking is restricted. It doesn’t obtain consent, provide a legal basis for tracking, or make every unobserved conversion reappear.

When Google tags are hard-blocked without Consent Mode:

  • Conversions from non-consenting sessions are not directly recorded by those tags
  • Remarketing audiences contain fewer eligible users and may shrink
  • Reported attribution can favor channels whose visitors consent at higher rates, making performance comparisons less reliable

Our guide to how privacy choices affect conversion explores the broader business implications of data transparency.

Google provides two Consent Mode implementations, and the distinction matters:

  • Basic Consent Mode blocks Google tags until the visitor interacts with the banner. If consent is denied, no data is sent to Google. This is more consistent with a hard-blocking approach but provides less detailed modeling.
  • Advanced Consent Mode loads Google tags with consent set to denied and sends measurements without cookies until consent is granted. This supports more detailed modeling, but it's not the same as preventing all pre-consent requests.
If your team needs help configuring consent signals and checking conversion tracking, Google Analytics GA4 agencies can support implementation and testing.

The 10-Minute Audit: See Your Site the Way a Plaintiff's Firm Does

Demand letters don't follow a careful reading of your privacy policy, but an automated scan checking one thing: whether your site sends data to third parties before the visitor agrees to anything.

You can run the same check yourself.

  1. Open your site in a fresh incognito window so no prior consent is stored.
  2. Open DevTools and switch to the Network tab.
  3. Reload the page. Don't touch the banner.
  4. Filter the request list for "facebook," "google-analytics," "googletagmanager," "tiktok," "hotjar," and "clarity."
  5. Anything returning a request before you click Accept is worth investigating.

Not every pre-consent request is a problem. Your CMP itself, your CDN, and security tooling all load early by necessity. What you're looking for is advertising, analytics, session replay, and chat traffic firing before anyone agreed to it.

Run it on the homepage, then on a form page and a checkout or contact page. Tags often differ by template, and the pages carrying the most sensitive input are the ones showing up in complaints.

For newsletter forms, review how consent on your signup page affects email compliance so your checks cover both website tracking choices and permission to send marketing emails.

This catches the obvious cases, but not trackers proxied through your own domain, renamed endpoints, or server-side tagging, and those are exactly what a plaintiff's automated scan is built to find.

What that scan usually turns up is consistent enough that practitioners can predict it.

Newmark says the consistent pattern is advertising pixels, session replay tools, third-party chat widgets, and analytics scripts all loading the moment the page renders. Owners are usually surprised, and the reason is almost always the same.

"Tags were added through a tag manager months after anyone last looked at the consent setup, so the banner is decorative rather than functional." Those four categories, he adds, are exactly what the demand letters name.

For an additional check, Cookiebot’s free cookie checker can help identify cookies and trackers on your website. Review the results together with your manual checks of tag behavior and consent settings.

Six Ways Website Privacy Compliance Breaks Down

The same failures repeat across enforcement actions and demand letters.

  • Treating California as the whole job: Twelve states require covered businesses to recognize universal opt-out signals, although applicability rules vary. Honoring GPC for every visitor can be simpler than maintaining separate state logic.
  • A banner that displays but doesn't block: Load the site fresh, decline, and watch the network tab. If requests keep going out, the banner is documenting an intent your site isn't meeting.
  • Filing marketing tools under "strictly necessary": Necessary means the site breaks without it. Analytics, advertising, and personalization don't qualify.
  • Leaving session replay, heatmaps, and chat ungated: These capture what a visitor types and clicks, which is why they show up in demand letters so often. Gate them like advertising pixels.
  • Cookie disclosures that don't match the site: Name the tools actually running, and update the list when the stack changes.
  • Setting it up once and never checking again: Re-scan on a schedule. The CPPA's Tractor Supply order required quarterly scans of every digital property.

Five of these are setup problems you can fix in an afternoon, but the sixth is why they come back. A configuration that passes today drifts the moment someone adds a campaign pixel, a vendor updates a script, or a state changes its rules.

3 CMPs Evaluated for US Privacy Risk

Every platform here can help manage privacy compliance for websites, and each can block a tracker before consent. The difference comes over the following year as tags get added, states change their rules, and nobody re-checks.

For a broader comparison of features and pricing, see our guide to the best consent management platforms.

That maintenance is what's worth paying for, so rather than feature counts, these three tools are judged on five things:

  1. Does it enforce consent at the script level, or only record what the visitor clicked
  2. Does it load and initialize before the tag manager
  3. Does it detect GPC at initialization and display the confirmation California now requires
  4. Does it produce timestamped, exportable consent records
  5. Does it apply different rules by state without a developer rebuilding the logic each time

None of these covers core US website compliance on its own. US setups default to opt-out, so trackers can still fire before a visitor decides. If CIPA is your concern, you'll need to configure stricter blocking and then test that it actually worked.

The decision to build or buy a CMP for US website privacy compliance comes down to whether one owner can reliably manage the tags, jurisdictions, and contributors involved.

FactorBuild and Maintain In-House Buy a CMP
Tracking stackFew, stable tagsTags change frequently
OwnershipOne technical ownerMarketing, developers, and agencies share access
Regional rulesOne conservative rule for every visitorDifferent state or regional configurations
Consent recordsYour team can maintain exportable recordsRecords need to be standardized and readily available
TestingEvery change can be manually auditedAutomated scans and ongoing monitoring are needed

A CMP can reduce the work involved in maintaining these controls, but someone still needs to review scan results, configure new tools, and test that visitor choices are respected. 

The following three platforms address different consent management needs: 

  1. Cookiebot: Best for automated blocking and regional consent rules
  2. Osano: Best for rights requests and vendor risk management
  3. Termly: Best for affordable consent controls on a single site

The table below compares three CMPs on pre-consent blocking, GPC handling, California opt-out confirmation, and starting price.

Feature Cookiebot Osano Termly
Best forAutomated blocking and regional rulesRights requests and vendor risk managementConsent controls for a single site
Pre-consent blockingYes, when configuredYes, when configuredYes, through Auto Blocker
Setup considerationsCorrect script placement and categorizationBlocking mode, script placement, and classificationSeparate consent settings for GTM tags
GPC supportAutomatic detectionMust be enabledMust be enabled by region
California opt-out confirmationBanner acknowledgmentVisible opt-out indicatorsConfirmation notification
Starting paid price$8/domain/monthCustom pricing$14/website/month, billed monthly

1. Cookiebot: Best for Automated Blocking and Regional Consent Rules

Cookiebot from Usercentrics homepage
[Source: Cookiebot]

Cookiebot addresses several common gaps in privacy compliance for websites. When properly configured, it controls pre-consent scripts, responds to GPC, confirms California opt-outs, and records each consent decision.

Monthly scans help identify configuration drift as teams add new tags, but the protection still depends on implementation. Cookiebot should load early in the page source, outside the tag manager, to ensure pre-consent blocking works as intended. Unclassified trackers also require manual review.

Its main value for US privacy compliance is consistency: one consent layer can manage tag timing, state-specific rules, GPC, and evidence as the website and regulatory landscape change.

Pros

  • Monthly scans on Premium plans flag newly detected and unclassified trackers for review
  • Honors GPC automatically and shows the on-banner confirmation California has required since January 2026
  • Runs EU opt-in and US opt-out experiences from one deployment through geotargeted configurations

Cons

  • Pricing is based on each domain or subdomain and its subpage count, so costs can rise across a large website portfolio

Pricing

  • Free: One domain, up to 50 subpages
  • Premium: Starts from $8 to $96 per domain per month, by subpage count
  • 14-day Premium trial

2. Osano: Best for Rights Requests and Vendor Risk Management

Osano homepage
[Source: Osano]

Osano is the stronger fit when website consent forms part of a wider US privacy program. Its higher tiers combine consent records with rights-request workflows and vendor scoring, helping teams manage both visitor choices and the third parties receiving their data.

That oversight is important because CCPA enforcement often reaches third-party arrangements. Honda was cited in part for sharing personal information with ad tech companies without contracts containing the required privacy protections, and Tractor Supply for the same failure with service providers.

Osano also offers up to $500,000 in coverage for qualifying regulatory fines. The guarantee applies only to eligible plans, depends on meeting its terms, and doesn't cover private CIPA demands.

Pros

  • Manages rights-request intake, verification, deadlines, and fulfillment workflows, with some actions automated where connected systems support them
  • Scores and monitors vendors, with alerts covering breaches, litigation, and privacy-policy changes
  • Offers eligible customers up to $500,000 in coverage for qualifying regulatory fines

Cons

  • Free and Plus are primarily consent-management plans; full rights-request, data-mapping, and vendor-risk capabilities require custom pricing
  • The guarantee is unavailable on Free and Plus, depends on meeting its terms, and does not cover private CIPA claims

Pricing

  • Free: One domain and 5,000 monthly visitors
  • Plus: $199 per month; three domains and 30,000 monthly visitors
  • Basic Privacy and advanced modules: Custom pricing

3. Termly: Best for Affordable Consent Controls on a Single Site

Termly homepage

Termly is a lower-cost option for a single website. When configured for prior consent, its Auto Blocker holds detected nonessential scripts until the visitor opts in. Scripts it can't categorize are assigned to “Unclassified” and blocked by default, although this can disrupt site functions until required scripts are reviewed.

Termly is sensitive to implementation: it must load before other scripts, and GTM tags require separate consent settings. Pro+ adds regional rules, Google Consent Mode v2, consent logs, and weekly scans. GPC must also be enabled for the relevant regions; once enabled, Termly applies the opt-out and displays California’s required confirmation.

Pros

  • Blocks detected, unclassified scripts by default
  • Free tier includes a banner, Auto Blocker, and quarterly scans
  • Pro+ adds weekly scans, regional rules, Consent Mode v2, and consent logs

Cons

  • Auto Blocker does not automatically control tags injected through GTM
  • Plans are licensed per website, and blocking can disrupt functionality until scripts are reviewed

Pricing

  • Free: 10,000 monthly banner views
  • Starter: $10 per month; 50,000 views
  • Pro+: $15 per month; unlimited views

What US Website Privacy Compliance Comes Down To

Every month you leave trackers ungated adds another month of visits a plaintiff could point to, while US website privacy regulations keep multiplying. Fixing it now costs an afternoon and a subscription. Fixing it after a letter costs whatever the letter says, plus the afternoon.

Disclaimer: This article does not contain the equivalent of legal advice and is only for general educational purposes only. For any legal questions or actions, readers need to consult with their legal counsels.

Our team ranks agencies worldwide to help you find a qualified partner. Visit our Agency Directory for the top IT services companies, as well as:

  1. Top Web Development Companies
  2. Top IT Services for Startups
  3. Top Cybersecurity Companies
  4. Top Managed IT Service Providers
  5. Top Web Development Company in Chicago

Our design experts also recognize the most innovative digital projects across the globe. Given the rapid evolution of web development, you’ll want to visit our Awards section for the best & latest in website designs.

Frequently Asked Questions

What is Global Privacy Control, and does my site have to honor it?

Global Privacy Control (GPC) is a browser-based signal that communicates a visitor’s preference to opt out of certain uses of their personal information. Your site must honor qualifying signals when your business is covered by a law requiring recognition.

In California, GPC communicates an opt-out of personal information sales and sharing, not a request to disable every cookie. The state table above explains the relevant dates and qualifications.

Does the CCPA require a cookie banner?

The CCPA doesn’t specifically require a cookie banner. Covered businesses must provide notice at or before collecting personal information and meet applicable opt-out requirements, including honoring GPC signals.

A CCPA cookie banner can help present these notices and choices, but its controls must work as described.

The CCPA generally uses an opt-out model for sales and sharing, with exceptions such as affirmative authorization for consumers known to be under 16. Other applicable laws may impose additional consent requirements. 

Who is liable when an agency installs a tracking pixel?

Hiring an agency doesn’t automatically transfer the website owner’s privacy responsibilities. Liability depends on the applicable law, each party’s conduct, and the contractual relationship.

Warranties and indemnities may allocate costs between the business and agency, but they don’t automatically prevent claims against either party.

The agreement should identify who approves trackers, maintains consent settings, tests changes, and handles complaints after launch.

Does cyber liability insurance cover CIPA claims?

A cyber policy may cover some CIPA claims, but coverage depends on its wording and the allegations. Exclusions for unlawful tracking, eavesdropping, or violations of privacy statutes can limit coverage even when the policy covers data breaches.

A broker or coverage lawyer can confirm whether the policy covers defense costs and settlements, which notification deadlines apply, and whether the insurer must approve a settlement before it occurs.

How does SB 690 change California Invasion of Privacy Act lawsuits?

Signed on September 30, 2026, SB 690 will remove the private right of action for website and online-app activity covered by CIPA’s pen-register and trap-and-trace provision, Section 638.51.

The amendments take effect on January 1, 2027, and will also apply to qualifying pending claims in actions filed within the preceding two years.

SB 690 doesn’t eliminate every CIPA claim. Private actions alleging interception of communication contents under other provisions remain possible, so the change shouldn’t be treated as blanket permission for website tracking. 

Latest IT Services Trends
Receive our NewsletterJoin over 70,000 B2B decision-makers growing their brands