California just told browser makers to build an opt-out switch.
It did not tell them to answer for what happens after the switch is flipped. That part stays with the website on the other end.
If you sell or share personal information and you take web traffic from California, the new law is about you, even though your name is not in it.
What does AB 566 (Civil Code 1798.136) actually require, and of whom?
AB 566 added Civil Code 1798.136 to the CCPA. Its addressee is narrow: a business "that develops or maintains a browser." That business "shall not develop or maintain a browser that does not include functionality configurable by a consumer that enables the browser to send an opt-out preference signal to businesses with which the consumer interacts through the browser." The setting must be "easy for a reasonable person to locate and configure."
The browser maker must also "make clear to a consumer in its public disclosures how the opt-out preference signal works and the intended effect of the opt-out preference signal."
Two definitions frame the scope:
- A browser is "an interactive software application that is used by consumers to locate, access, and navigate internet websites."
- An opt-out preference signal is "a signal that complies with this title and that communicates the consumer's choice to opt out of the sale and sharing of the consumer's personal information."
The California Privacy Protection Agency "may adopt regulations as necessary to implement and administer this section."
On timing, be precise. Section 1798.136 was added by Stats. 2025, Ch. 465 (AB 566), effective 1 January 2026, and subdivision (f) states: "This section shall become operative on January 1, 2027." It is not yet in force for browsers.
Note what the text does not say. It does not require the setting to be on by default, and it names no signal standard.
If you don't build a browser, why does 1 January 2027 still matter to you?
Because the obligation to honour the signal was never the browser maker's. It is yours, and it already exists.
AB 566 changes supply, not duty. From 1 January 2027, every browser subject to the section must offer a consumer-configurable setting that can send it.
More browsers able to send the signal means more consumers sending it. The receiving business carries the volume.
Global Privacy Control is the implementation most often discussed. The CCPA text does not name it or any other protocol; it defines the signal by what it communicates and leaves specifications to regulation. Treat Global Privacy Control as one signal you may receive, not as the legal definition.
What must a business already do when it receives an opt-out preference signal under 1798.135?
Start with the underlying right. Under 1798.120(a)(1), a consumer "shall have the right, at any time, to direct a business that sells or shares personal information about the consumer to third parties not to sell or share the consumer's personal information." This is the CCPA sale or sharing opt-out.
"Sharing" here is specific. 1798.140 defines it as communicating personal information "to a third party for cross-context behavioral advertising, whether or not for monetary or other valuable consideration." Ad-tech tags with no money changing hands can still be sharing.
Section 1798.135 then gives a business two routes:
→ Subdivision (a): clear and conspicuous homepage links, "Do Not Sell or Share My Personal Information" and "Limit the Use of My Sensitive Personal Information," or a single combined link.
→ Subdivision (b): no obligation to post those links "if the business allows consumers to opt out of the sale or sharing of their personal information and to limit the use of their sensitive personal information through an opt-out preference signal."
The statute is explicit that "a business may elect whether to comply with subdivision (a) or subdivision (b)."
Here is the part teams miss. Subdivision (e) says a consumer may authorize another person to opt out "including through an opt-out preference signal," and "a business shall comply with an opt-out request received from a person authorized by the consumer to act on the consumer's behalf, pursuant to regulations adopted by the Attorney General regardless of whether the business has elected to comply with subdivision (a) or (b)."
Choosing the link route does not let you ignore the signal.
Once a signal is received, the general 1798.135(c) duties apply. A business must:
- Not require a consumer to create an account or provide information beyond what is necessary to opt out.
- State in its online privacy policy either the opt-out links or "a statement that the business responds to and abides by opt-out preference signals."
- Refrain from selling or sharing, and "wait for at least 12 months before requesting that the consumer authorize the sale or sharing" again, "or as authorized by regulations."
- Use personal information collected with the opt-out request "solely for the purposes of complying with the opt-out request."
The duty also runs downstream. Under 1798.135(f), if a business communicates an opt-out to a person it authorized to collect personal information, that person is then "prohibited from" selling or sharing it. Under (g), the business is not liable for that person's violation if, when it passed the request on, it had no "actual knowledge, or reason to believe, that the person intends to commit such a violation."
That shield only works if you pass the signal on. An opt-out that stops at your banner and never reaches the tags on the page protects no one. This is where your data registries and third-party risk records need to agree on who collects what on each page.
Why does the browser maker's liability shield in 1798.136(d) put the risk on the receiving site?
Subdivision (d) is the allocation clause: "A business that develops or maintains a browser that includes a functionality that enables the browser to send an opt-out preference signal pursuant to this section shall not be liable for a violation of this title by a business that receives the opt-out preference signal."
Read it as a routing rule. The browser maker's job ends when a compliant signal leaves the browser. What the receiving site does next is the receiving site's exposure.
Under 1798.155(a), a business that violates the title is liable for an administrative fine of up to $2,500 per violation, or $7,500 per intentional violation, "as adjusted pursuant to subdivision (d) of Section 1798.199.95," in an action brought by the California Privacy Protection Agency.
There is a counterweight for receiving businesses. The rulemaking mandate in 1798.185(a)(18)(A) directs that the signal specifications should ensure "that the manufacturer of a platform or browser or device that sends the opt-out preference signal cannot unfairly disadvantage another business."
Can you ask a consumer to consent to ignoring the signal, and on what conditions?
Yes, but the route is narrow and conditioned.
A business relying on subdivision (b) "may provide a link to a web page that enables the consumer to consent to the business ignoring the opt-out preference signal," provided that:
- (A) the consent page lets the consumer "revoke the consent as easily as it is affirmatively provided";
- (B) the link "does not degrade the consumer's experience on the web page the consumer intends to visit and has a similar look, feel, and size relative to other links on the same web page";
- (C) the consent page complies with technical specifications in regulations under 1798.185(a).
The rulemaking mandate in 1798.185(a)(19) adds direction on how a business may respond. Regulations should ensure the business does not respond to a signal by intentionally "degrading the functionality of the consumer experience," charging "the consumer a fee," or displaying "any notification or popup in response to the consumer's opt-out preference signal."
Any opt-in link must not be "part of a popup, notice, banner, or other intrusive design," must not "make use of any dark patterns," and must apply "only to the business with which the consumer intends to interact."
A drafting point for counsel: 1798.135(b) cross-refers to specifications in "paragraph (19) of subdivision (a) of Section 1798.185," but in the current text the signal specifications sit in (18)(A) and business-response rules in (19). Cite substance, not only paragraph numbers.
The practical reading: a consent-to-ignore flow works only as a quiet, symmetric, per-business option. A modal triggered by the signal is the pattern the statute tells the regulator to stop.
How do you test signal handling end to end before 1 January 2027?
You do not need a new browser release to test. The duty to honour signals is live now.
→ Detect. Each California-facing property reads the signal on first page load, before any sale or sharing tag fires.
→ Apply. Confirm the signal suppresses every third party that receives personal information for cross-context behavioral advertising. Check the tag inventory, not the banner.
→ Propagate. Confirm the opt-out reaches each person you authorized to collect personal information, so the 1798.135(g) shield is available.
→ Persist. Confirm the 12-month wait before asking the consumer to authorize sale or sharing again, and that no account or extra data is demanded.
→ Disclose. Confirm your privacy policy contains the statement that you respond to and abide by opt-out preference signals, if you rely on subdivision (b).
→ Consent path. If you offer a consent-to-ignore link, test revocation symmetry and confirm nothing pops up in response to the signal.
Record the evidence per property against the subdivision it satisfies. When the California Privacy Protection Agency adopts rules under 1798.136(c), you rerun the test against the changed requirement, not from scratch.
That is the approach our platform takes: every obligation traced to a verbatim quote from the legal text, so a change to one subdivision touches only the controls that depend on it. Answer once. Assess everything.
FAQ: AB 566, Global Privacy Control and the CCPA opt-out signal
When does AB 566 apply? Civil Code 1798.136 is effective 1 January 2026 and operative 1 January 2027 under its subdivision (f). The browser-maker duty applies from that operative date.
Does AB 566 create a new duty for websites to honour opt-out signals? No. That duty already sits in 1798.135, including subdivision (e). AB 566 makes the signal available in more browsers.
Is Global Privacy Control the legally required signal? The statute does not name it. Test against whatever signals your properties actually receive.
Does AB 566 require browsers to turn the signal on by default? The text requires a consumer-configurable setting that is "easy for a reasonable person to locate and configure." It does not require a default-on setting.
See how your California opt-out obligations map to controls and evidence at agrc.ai.


