On 6 November 2026, California's privacy regulator voted unanimously to start formal rulemaking that would tighten how businesses must honour browser-based opt-out signals such as Global Privacy Control (GPC). If your website or app reaches California residents, the proposed rules could change what your consent and tracking stack has to do.
The vote came at a meeting of the board of the California Privacy Protection Agency (CalPrivacy), as reported by the IAPP. Nothing is final yet: the draft still has to be published and go through public comment. But it shows where US privacy enforcement is heading, and it echoes a debate EU businesses already know from the GDPR and ePrivacy world: should a user's browser setting count as a binding privacy choice? This article explains what was proposed, what is still open, and what a small or mid-sized business can do now. It is for general information only and is not legal advice.
Background: what an opt-out preference signal is
An opt-out preference signal (OOPS) is a setting a person turns on once, usually in a browser or extension, that tells every website they visit: do not sell or share my personal information. Global Privacy Control (GPC) is the best-known example. Under California's CCPA rules, a business that receives a valid signal has to treat it as the consumer's opt-out request, with no extra clicks or forms.
California regulators have been tightening expectations for a while. According to a Wilson Sonsini alert, the agency's view is that ignoring a GPC signal and cleaning up later does not satisfy the rule that businesses stop selling or sharing “as soon as feasibly possible”. CalPrivacy also ran a preliminary public consultation on opt-out preference signals between 6 March and 6 April 2026, listed on its opt-out preference signals page.
Two more pieces of context matter. In August 2026 the board directed staff to draft formal amendments, as covered by Wilson Sonsini and Alston & Bird. And California's AB 566, the Opt Me Out Act, requires browser developers to build in a universal opt-out signal starting 1 January 2027, so more consumers will be sending these signals by default.
What the board advanced
The board voted unanimously to open formal rulemaking on amendments to the CCPA regulations covering opt-out preference signals. Based on the IAPP report, the proposal would:
- name GPC explicitly as a recognised opt-out preference signal;
- add worked examples showing how the rules apply to pseudonymous profiles, cookie syncing, and browser features that disclose a consumer's personal information;
- require systems to recognise signals and apply the opt-out across all of a business's digital properties, according to CalPrivacy counsel;
- stop browser features from interfering: a browser feature that acts for the consumer must not block or get in the way of sending the opt-out preference to businesses;
- add metrics reporting: businesses that must run a cybersecurity audit or risk assessment would report how many opt-out requests reached them through preference signals.
The August discussions add detail. Per Alston & Bird, the staff direction also covered a clarification that privacy controls must be processed before personal information is sold, shared or disclosed, which in practice means a GPC signal should be honoured before advertising cookies or trackers fire. The Wilson Sonsini alert adds that the existing 10-million-consumer threshold for annual metrics reporting would be replaced by a “significant risk” standard.
Timeline
The draft must first be published in the California Regulatory Notice Register and on CalPrivacy's regulations portal. A 45-day public comment period follows, then 15-day periods for any revised drafts. We could not open the draft text itself, so check the published proposal before you rely on any specific wording.
Why it matters for European businesses
If you are an EU or EEA company that sells to, or tracks, visitors in California, the CCPA applies once you meet its thresholds, wherever you are based. Server location and company seat do not change that. Many European SMBs with a US-facing webshop or SaaS product are in scope without realising it.
The rule also rhymes with European law. Article 21(5) GDPR already allows people to exercise their right to object by automated means using technical specifications, and the ePrivacy rules on cookies hinge on valid consent (see our guide to cookie banner mistakes). EU policymakers have also discussed machine-readable browser signals for cookie choices as part of the reform debate (see our Digital Omnibus article), so check the current legislative status before you plan around it. The direction is the same on both sides of the Atlantic: a choice made once in the browser should be respected, not re-asked through a banner.
The practical lesson is technical. A cookie banner that looks compliant is not enough if your tag manager fires advertising scripts before it checks the browser's signal. Regulators are testing what actually happens on the page.
What to do now
You do not need to wait for the final text. These steps are sound practice under the rules already in force:
- Check whether the CCPA applies to you: California consumers, revenue or data-volume thresholds, and whether you sell or share personal information.
- Test your site with GPC switched on, in a browser or extension that sends it, and watch which cookies and third-party requests still fire.
- Make your consent tool and tag manager read the signal before advertising or analytics tags load, not after.
- Apply the opt-out to the whole consumer where you can, including logged-in accounts and linked identifiers, not just that one browser.
- Cover every digital property: subdomains, microsites, checkout, and apps where the signal can reach them.
- Start logging opt-out requests received through preference signals, so you can report numbers if the new rules apply to you.
- Review vendor contracts so ad-tech and analytics partners honour the opt-out downstream.
- Update your privacy notice to describe how you respond to opt-out preference signals.
- Watch for the formal notice and comment period, and decide whether to submit feedback.
The bottom line
California is turning browser-level opt-outs from a best practice into a rule with examples, reporting numbers and a clear expectation that signals are honoured before tracking starts. The final text will change, but the direction will not, and with AB 566 browsers will send these signals by default from 2027.
If you also serve US customers, now is a good moment to review how your consent setup behaves in practice, not just how it looks. GDPRGard's audit tool is a good place to start.
Sources
- IAPP: CalPrivacy board advances rulemaking to update opt-out preference signals requirements (9 Nov 2026)
- Wilson Sonsini: CalPrivacy authorizes rulemaking on opt-out signals (18 Aug 2026)
- Alston & Bird: California privacy, opt-out signals and data brokers (14 Aug 2026)
- CalPrivacy: Opt-out Preference Signals
- GDPR, Regulation (EU) 2016/679, EUR-Lex
- ePrivacy Directive 2002/58/EC, EUR-Lex
The positions above are summarised from the sources listed; the proposal is reported secondhand and the draft text had not been published when this article was written, so check it before relying on specific wording. Analysis of how it fits with EU law is ours.
Also read:
- 5 Cookie Banner Mistakes That Break GDPR (and How to Fix Them)
- Is “Schrems III” coming? A Supreme Court ruling shakes the Data Privacy Framework
- Inside the EU's Digital Omnibus: what's actually changing for GDPR, and what just stalled