the-fine-printopt-outglobal-privacy-controlenforcementccpa

The Fine Print: Did Anyone Hear the Signal?

Ben TobinUpdated 6 min read

The Fine Print is a twice-weekly series that reads privacy law from the consumer's side: what a word promises, what the text says, and what is left exposed.

This month, California's privacy agency published a Board decision in In the Matter of The Hertz Corporation (Case No. ENF25-001-V-HE). The Board adopted a stipulated final order, which is a settlement, under which the company "shall pay an administrative fine in the amount of one million five hundred fifty thousand dollars ($1,550,000.00)" (Decision and Stipulated Final Order, ¶54). The company admits certain statements in the order, "otherwise neither admits nor denies" the remaining findings and "does not admit liability for any violation of the CCPA, actual or alleged" (¶68).

This post is not about one company. It is about a feature of California law that most people never see at work: the opt-out preference signal. The order is a rare, detailed look at what it means when that signal is sent and the question of whether anyone heard it stays open.

What the word promises

The regulations define an "opt-out preference signal" as "a signal that is sent by a platform, technology, or mechanism, on behalf of the consumer," "that communicates the consumer choice to optout of the sale and sharing of personal information" (Cal. Code Regs., tit. 11, §7001(aa), regulations effective 1 January 2026).

The Agency's own guidance calls it "a simple and easy-to-use way for consumers to automatically exercise their right to opt-out." Its example is "the Global Privacy Control, a protocol available via internet browser or a browser extension" (CalPrivacy, What Is OOPS and How Does A Business Respond). A business that receives one "must stop selling and sharing" and must do so "as soon as feasibly possible." Even where the signal conflicts with a person's privacy settings on a site, "the business still needs to treat the OOPS as a valid request to opt-out of sale/sharing."

That is a strong promise. You switch on one setting, with no forms and no account, and every site you visit gets the message.

What the text says

The order sets out the law it applied. "Consumers have the right to direct businesses not to sell or share their personal information," and "Consumers may do so through an opt-out preference signal, such as Global Privacy Control" (¶34, citing Civ. Code §1798.120(a) and tit. 11, §§7025, 7026). Global Privacy Control works "by sending a standardized HTTP header and setting a JavaScript property" (¶35). Once a business has the request, "it is prohibited from selling or sharing that consumer's personal information" except as the statute allows (¶37, Civ. Code §1798.120(d)). A business online "must also explain how an opt-out preference signal will be processed" in its privacy policy (¶41, tit. 11, §7011(e)(3)(F)).

So the signal is a request. It is one that has to be answered by the business's own configuration, on every page, every time.

What stays exposed

The order's findings, which the company neither admits nor denies, say it "failed to configure its digital properties to properly detect and honor consumers' opt-out preference signals" (¶38). The order's relevant period for the case as a whole "is July 1, 2023 to August 25, 2026, unless otherwise indicated" (¶30). The order also describes a cookie window whose toggles "indicated that all the cookies were turned off," after which "the settings reverted to the default settings, which allowed advertising cookies" (¶¶45–46).

Read from the consumer's side, three questions follow.

The sender gets no reply. A signal is a header your browser sends. Nothing in it comes back to you. From your own screen, a site that acts on it and a site that doesn't can look identical.

A saved choice may not stay saved. The findings describe settings that looked off and then reverted. A person who saved their choices once had no reason to check again.

An opt-out looks forward. It is about selling and sharing from now on. What happens to copies already passed on is a separate question, covered in The Copies Already Sold.

The case the other way

There is a strong case that this is the system working.

Enforcement reached it. The Board acted, and the remedy is specific. The obligations "shall remain in effect for a period of three (3) years" (¶55). The company "must check to see if it has received the consumer's GPC signal before loading tracking technologies" (¶56(b)(i)). It must test its configurations "in both staging and production environments at least quarterly" (¶56(c)), and test its request methods "to ensure that they are functioning properly" (¶58).

The order asks for outside checking. The company "shall not rely solely on the statements, documents, claims, or representations of any service provider" and "shall independently assess, at least twice per year," its service providers (¶60). That is the principle this series keeps returning to: a claim about compliance is checked by someone other than the party making it.

Low friction is the point. A signal that asks nothing of the consumer can fail silently, but the alternative, a separate form on every site, asks far more of each person. A settlement can also put a fix in place sooner than years of litigation.

A fix anyone could carry out

  • For the Agency: the order requires the company to post annual request metrics and to "separately identify the number of requests that were received from an opt-out preference signal" (¶61). Asking for that separate count from every business that already publishes request metrics under tit. 11, §7102 would show, in public, whether signals are arriving and being counted.
  • For businesses: borrow the order's checklist without waiting for an order. Check for the signal before tracking loads, and test quarterly in staging and in production. When a signal is received, say so on the page.
  • For you: turn on Global Privacy Control where your browser offers it, or through an extension. Where you hold an account, also use the site's own opt-out link, so there is a second record of your choice. After saving cookie choices, reopen the panel a few days later to see whether they held. For registered data brokers, California's deletion platform is a separate route; Your DROP Status, Decoded explains what each result means.
  • For everyone: sending a request is step one. Seeing whether it was honored is step two.

Who checks a status a company reports about itself is the subject of our working paper, Who Verifies the Status?. For a federal proposal that would treat a company's own record as proof, see When the Record Becomes the Proof.


Sources, read 20 November 2026: California Privacy Protection Agency Board, Decision and Stipulated Final Order, Case No. ENF25-001-V-HE, ¶¶30, 34–35, 37–38, 41, 45–46, 54–56, 58, 60–61, 68; CalPrivacy, CCPA regulations effective 1 January 2026, tit. 11, §7001(aa); CalPrivacy, What Is OOPS and How Does A Business Respond. Statutory and regulatory provisions other than §7001(aa) are cited as the Board's order quotes them.

Follow Sirveil on LinkedIn: https://www.linkedin.com/company/133457181 · Follow @Sirveil_AI on X.

Disclosure: Sirveil builds privacy verification tools, so we have a commercial interest in this subject.

Sirveil for business: sirveil.ai/for-business

NONE OF THIS CONSTITUTES LEGAL ADVICE.

Share this article

PostShare

Get privacy insights delivered

One email a month: privacy-law changes, data-broker news, and what’s new at Sirveil. No spam, unsubscribe in one click.

Start protecting your personal data

Scan, verify, remove: Sirveil finds where brokers list you, you confirm which entries are yours, and your takedown requests are prepared, transmitted, and chased on your behalf — tracked end to end.

Get Sirveil

Available now on the App Store and Google Play.