[00] Subset Opt-Out, Guide
Show "Opt-Out Request Honored" on a WordPress site
California's rules now require a site to show visitors that their Global Privacy Control signal was honoured. What that means and how to add it in WordPress.
- Published
- Fix uses
- Subset Opt-Out (free)
- Reading time
- 3 min
What the rule says
Since 1 January 2026, the California Consumer Privacy Act (CCPA) regulations require a business to show whether it processed a visitor’s opt-out preference signal, such as Global Privacy Control (GPC), as a request to opt out of sale and sharing (§ 7025(c)(6)). The regulation gives an example: show “Opt-Out Request Honored” when a browser sending the signal visits, and show through a toggle or radio button that the visitor has opted out.
A separate rule, § 7026(g), requires a way for a visitor to confirm that their request to opt out was processed.
Before 2026, showing the status was optional, and the example read “Opt-Out Preference Signal Honored”. That’s why both phrases appear in guides about the rule. The current text is in the CCPA regulations (opens in a new tab), and our page on the California Consumer Privacy Act covers who the law applies to.
What Subset Opt-Out shows already
Subset Opt-Out treats a visitor whose browser sends GPC as opted out from their first page view. When that visitor opens Your Privacy Choices, the switch for sale and sharing is off, and the panel says:
Your browser is sending a Global Privacy Control signal, so we treat you as opted out, even if you allowed sale/sharing before. To allow it anyway, turn on the switch and save.
That covers the toggle in the regulation’s example. The panel opens when the visitor clicks your opt-out link. For a status the visitor sees without a click, add one to the page.
Add a status line to every page
The status has to be decided in the visitor’s browser. A cached page is the same HTML for everyone, so a line written by PHP would show the same thing to every visitor. Subset Opt-Out exposes the visitor’s state as window.subsetCM, which exists before any script WordPress prints after its head script.
Add an empty, hidden element where you want the line, for example in a Custom HTML block in your footer:
<p id="opt-out-status" hidden>Opt-Out Request Honored</p>
Then show it for visitors whose opt-out came from the signal. This script goes in the same block, or anywhere after wp_head():
<script>
document.addEventListener("DOMContentLoaded", () => {
const status = document.getElementById("opt-out-status");
if (!status || !window.subsetCM) return;
const update = () => {
status.hidden = window.subsetCM.get().source !== "gpc";
};
update();
document.addEventListener("subset-cm:consent-changed", update);
});
</script>
get().source is "gpc" when the opt-out came from the signal. If the visitor turns the switch back on and saves, the source becomes "user" and the line hides again. The developer reference lists the rest of the API.
Posting a Custom HTML block with a script needs a role that’s allowed to add unfiltered HTML, which on a single site means an administrator or editor.
Check it in your browser
Turn GPC on. Brave and DuckDuckGo send it by default, and Firefox has a setting under Settings → Privacy & Security. In Chrome, install an extension that sends it, such as Privacy Badger.
Open your site in a private window, so no earlier choice is stored. The status line should show. In the DevTools console, navigator.globalPrivacyControl should be true and subsetCM.get().source should be "gpc". How Subset Opt-Out reads Global Privacy Control has the full set of checks, including the cookie and Google Consent Mode.