Skip to content
TagSentry
Blog

Guide · Rules and enforcement

Global Privacy Control: what it is and how to honour it

Global Privacy Control is a browser signal that says don't sell or share my data. What it sends, Safari's new setting, and who must honour it.

The TagSentry team · September 15, 2026 · updated November 12, 2026 · 8 min read

The short answer

Global Privacy Control (GPC) is a browser setting that tells every site you visit "don't sell or share my personal information". The browser sends it as a Sec-GPC: 1 header and as navigator.globalPrivacyControl in JavaScript. A dozen US states require businesses to treat it as an opt-out, and from 1 January 2027 California makes every browser offer a setting like it. To honour it, read it before your tags load and keep advertising tags from firing, with no click needed from the visitor.

What it is

GPC is a single yes signal. When a person switches it on, their browser adds it to every request and every page. It says this person doesn't want their data sold or shared.

It's narrower than a cookie banner answer. It says nothing about analytics or about cookies a site needs to work. But "don't sell or share" covers most advertising and cross-site tracking, which is where the legal risk sits.

Which browsers send it

BrowserGPC today
DuckDuckGoBuilt in, on by default
BraveBuilt in
FirefoxA setting ("Tell websites not to sell or share my data"), on by default in private windows, since version 120
ChromeNot in the normal release yet. It arrived in Canary test builds in July 2026, and a test flag that sends the signal appeared in August
EdgeThrough an extension, such as Privacy Badger
SafariIn beta. iOS 27.3 adds a "Use Global Privacy Control" setting, off until you switch it on. Apple hasn't listed it in release notes yet

What a browser sends (we tested it)

The specification says a browser with GPC on sends two things. We checked both in Firefox 153, once with the setting off and once with it on, and then loaded a live site that runs TagSentry (tagsentry.ai itself) from a US state outside the twelve listed below.

GPC offGPC on
Sec-GPC request headernot sent1
navigator.globalPrivacyControlfalsetrue
Google's ad signals after the page loaded (ad_storage, ad_user_data, ad_personalization)granteddenied
analytics_storagegrantedgranted
What the visitor sawnothing (a clear page)a small notice: "Opt-out request honored" and "Your browser sent Global Privacy Control."

The header goes out with the very first request, so a server can act on it before any HTML arrives. And the JavaScript value is there from the start of the page, so a script at the top of <head> can read it before Tag Manager loads.

To check your own browser, open the developer console on any page and type navigator.globalPrivacyControl. true means it's on.

Does Safari support Global Privacy Control?

Not in a released version yet. The iOS 27.3 beta, out in early November 2026, adds a switch called "Use Global Privacy Control" under Settings, Apps, Safari, Advanced. Apple's text under it reads: "Safari can ask websites to not sell or share your data." It's off until you turn it on.

Apple hasn't mentioned the setting in its release notes, and beta features can change or vanish before release. If it ships as it is, any iPhone owner who flips the switch sends the same signal Firefox sends, and your site should treat it the same way.

Who has to honour it

California was first. Its regulators treat GPC as a valid request to opt out of sale and sharing, and their first public settlement under the state privacy law, with Sephora in 2022, was partly about ignoring it. Sephora paid $1.2 million.

Other states followed. Colorado made universal opt-out signals mandatory from July 2024. California's privacy regulator, the CPPA, counts at least twelve states requiring them as of 2026: California, Colorado, Connecticut, Delaware, Maryland, Minnesota, Montana, Nebraska, New Hampshire, New Jersey, Oregon and Texas. Louisiana joins in January 2027 and Vermont in January 2028.

In other US states, honouring GPC is good practice rather than a clear legal requirement.

California's rules also ask you to show whether you processed the signal. The regulator's own examples are a line such as "Opt-Out Preference Signal Honored", or a toggle showing the visitor is opted out.

What the Opt Me Out Act changes in 2027

California's Opt Me Out Act (AB 566) was signed in October 2025. From 1 January 2027, any business that makes a browser must give people a setting that sends an opt-out preference signal to the sites they visit.

The law is aimed at browser makers. Your duty as a site owner stays the same: honour the signal when it arrives. What changes is how often it arrives.

Today GPC comes from Firefox, Brave, DuckDuckGo and extensions. Chrome added it to Canary test builds in July 2026, and Chromium code suggests its switch may show only where a law requires one. Safari has its own switch in the iOS 27.3 beta.

The CPPA, which now calls itself CalPrivacy, is also rewriting its own rules. At its meeting on 5 and 6 November 2026 the board voted unanimously to start formal rulemaking on opt-out preference signals. The draft names Global Privacy Control in the regulation itself, as an example of a signal businesses must honour.

The draft also adds an example aimed at sites: a business whose ad and analytics tags load before its consent tool and Tag Manager have checked for GPC is selling or sharing data in the first milliseconds of the page load. The agency's draft reasoning calls that "a direct violation of the timing requirement".

None of this is in force. A 45-day public comment period starts once the text is formally published, and as of 12 November the CPPA's regulations page doesn't list it yet.

The work for a site now is the same as before, done sooner. Make sure the signal is read before your tags load, check your ad tags stop, and test it in Firefox before Chrome ships its setting.

How to honour global privacy control

You have to respect the signal before anything that counts as sale or sharing happens. Reading it after your tags have fired is too late.

  1. Read it first. Check navigator.globalPrivacyControl in a script that runs before Tag Manager, at the top of <head>. California's draft rules use exactly this case as their example of getting the timing wrong.
  2. Treat it as an opt-out. For that visitor, advertising tags should not fire, and Google's Consent Mode signals for ads should be denied.
  3. Don't ask them to confirm. A GPC visitor already said no. A pop-up nudging them to opt back in defeats the point.
  4. Tell them it worked. A small confirmation like "Opt-out request honored" is enough.
  5. Record it. Keep a record that this visitor's browser sent GPC and what you did about it.

Doing it in Tag Manager

Tag Manager has no built-in GPC switch. Most people do it like this:

// At the very top of <head>, before the Tag Manager snippet
window.dataLayer = window.dataLayer || [];
function gtag(){dataLayer.push(arguments);}
if (navigator.globalPrivacyControl === true) {
  gtag('consent', 'default', {
    ad_storage: 'denied',
    ad_user_data: 'denied',
    ad_personalization: 'denied'
  });
}

Then, for non-Google tags like the Meta Pixel or TikTok, add a trigger condition so they only fire when advertising consent is granted. Google's tags read Consent Mode by themselves. Other vendors' tags don't.

To confirm Google got the message, look at the gcs value on a Google request: the decoding table in our Consent Mode checking guide shows which value means ads denied and analytics granted.

The snippet is the easy bit. Getting it to run first, in every state, and keeping it working when someone adds a new pixel next month, is the harder part.

Even when the consent tool reads the signal, other tags may not follow it. We visited 47 sites running Osano with GPC on: Osano recorded the opt-out on 43, and on 20 of those, ad platforms still got data (what we found).

Common mistakes

MistakeWhy it matters
Reading GPC inside a Tag Manager tagOther tags may already have fired
Only handling Google's tagsMeta, TikTok and others ignore Consent Mode
Showing a "please reconsider" pop-upUndermines the opt-out and annoys the visitor
Forgetting pixels outside Tag ManagerA Meta Pixel pasted into your theme ignores your GTM logic
Honouring it on one device onlyPart of what Disney settled over
No recordYou can't show you honoured it

Enforcement

California regulators didn't stop at Sephora. Healthline paid $1.55 million in July 2025, partly for sharing data with ad partners after visitors opted out. The CPPA fined Tractor Supply $1.35 million in September 2025 and PlayOn Sports $1.1 million in March 2026, both over opt-out signals.

In February 2026 Disney agreed to pay $2.75 million, the largest settlement under the state's privacy law when it was announced. Among other things, when a visitor sent GPC, Disney applied the opt-out only to that one device, even when the person was logged in to their account.

In October 2026 Lyft agreed to pay $1.8 million, the attorney general's ninth action under the law. The attorney general's main complaint was an opt-out buried behind privacy-policy links that made people log in again.

The court order also spells out how far an opt-out has to reach, including one sent by a browser signal. For someone logged in, it covers every Lyft service tied to their account. For someone who isn't, it covers that browser, app or device and any profile linked to it, including pseudonymous advertising profiles.

Regulators find these cases through sweeps. In September 2025 the CPPA and the attorneys general of California, Colorado and Connecticut ran a joint one aimed at businesses that ignore GPC. The cheapest check is to run your own: turn GPC on in Firefox and watch what your tags do.

How TagSentry handles GPC

TagSentry reads GPC before anything fires and honours it wherever visitors can opt out: every US state, the rest of Canada, and countries with no consent law. That goes further than the states that require it, because the signal is the visitor's own choice wherever they happen to be.

When more browsers send it in 2027, any signal built to the GPC standard is honoured the same way, with nothing for you to change.

GPC means "don't sell or share", so that's what the banner applies. Ad tags wait, Google's ad signals are set to denied, and your own analytics keeps running.

The first time, the visitor sees a small notice, "Opt-out request honored", and their saved choices show it as "via GPC". The signal goes into the consent record, which you can export as a CSV. The test above shows it on our own site.

Sources

  1. W3C: Global Privacy Control specification
  2. Global Privacy Control: browsers and extensions that send it
  3. Mozilla: Global Privacy Control in Firefox 120 (on by default in private browsing)
  4. Mozilla Support: Global Privacy Control in Firefox
  5. Chromium blink-dev: Intent to Prototype Global Privacy Control (January 2026)
  6. PiunikaWeb: Chrome Canary adds a Global Privacy Control flag (August 2026)
  7. California AG: Sephora settlement over Global Privacy Control
  8. California AG: $2.75 million settlement with Disney (February 2026)
  9. Colorado AG: universal opt-out mechanism
  10. Colorado AG: Colorado Privacy Act (universal opt-out from 1 July 2024)
  11. CPPA Board: opt-out preference signals, informational session paper (6 August 2026)
  12. CPPA: preliminary rulemaking on opt-out preference signals
  13. CPPA: regulations (no proposed packages listed as of 12 November 2026)
  14. CPPA Board meeting materials, 5 and 6 November 2026 (opt-out preference signal rulemaking)
  15. CPPA: draft Initial Statement of Reasons, opt-out preference signals (October 2026)
  16. IAPP: CalPrivacy Board advances rulemaking on opt-out preference signals (November 2026)
  17. California AG: $1.8 million settlement with Lyft (October 2026)
  18. People v. Lyft: final judgment and permanent injunction (29 October 2026)
  19. 9to5Mac: iOS 27.3 adds a Global Privacy Control setting to Safari (November 2026)
  20. Pixel Envy: Safari 27.3 adds support for Global Privacy Control (November 2026)
  21. PiunikaWeb: Global Privacy Control added to Chrome Canary (July 2026)
  22. PiunikaWeb: Chrome's GPC setting may appear only where the law requires it (August 2026)
  23. California AG: $1.55 million Healthline settlement (July 2025)
  24. CPPA: Tractor Supply to pay $1.35 million (September 2025)
  25. CPPA: PlayOn Sports to pay $1.1 million (March 2026)
  26. IAPP: California requires an in-browser opt-out preference signal