The GPC signal tells websites not to sell or share a visitor's personal data. Learn how it works, where the law requires it, and how UniConsent honors it automatically.

Global Privacy Control (GPC) is a browser setting that tells every website you visit not to sell or share your personal information. When it is on, the browser adds the HTTP header Sec-GPC: 1 to each request and sets navigator.globalPrivacyControl to true for scripts on the page. That is the GPC signal.
In California, Colorado, Connecticut and a growing list of US states, the law treats the GPC signal as a valid request to opt out of the sale or sharing of personal data and of targeted advertising. Websites covered by those laws must honor it automatically, without asking the visitor to click anything.
GPC is the best-known opt-out preference signal, the general term the California regulations use for this kind of browser-level opt-out.
GPC was introduced at the World Wide Web Consortium (W3C) Privacy Community Group in April 2020 by a group of browsers, publishers, privacy researchers and advocates. In November 2024 it became an official work item of the W3C Privacy Working Group, where the specification is being standardized.
The specification defines two ways for a website to read the signal, plus an optional file for the website to declare that it honors GPC:
Sec-GPC: 1 with requests. The header is only sent when GPC is on, and servers should treat any value other than 1 as not set.navigator.globalPrivacyControl returns true when the header would be sent and false when it would not./.well-known/gpc.json to state that it intends to honor GPC.GET /checkout HTTP/1.1
Host: www.example.com
Sec-GPC: 1
// Read the GPC signal in the browser
if (navigator.globalPrivacyControl === true) {
// Treat the visitor as opted out of sale, sharing and targeted advertising
}
// /.well-known/gpc.json
// { "gpc": true, "lastUpdate": "2026-10-01" }
GPC is a signal, not a blocker. It does not stop tags by itself: the website, or its consent management platform, has to detect it and act on it.
| Browser or tool | GPC support |
|---|---|
| Brave | Built in, on by default |
| DuckDuckGo browser | Built in, on by default |
| Firefox | Built-in setting, on by default in private windows |
| Chrome | Built-in setting in testing in Chrome Canary, not yet in the stable release |
| Extensions | Privacy Badger, OptMeowt, Disconnect and others add GPC to browsers without a setting |
California's Opt Me Out Act (AB 566), signed in October 2025, requires browsers to offer a built-in opt-out preference signal setting from January 1, 2027, so GPC traffic is expected to grow.
To check that it works, open the browser console on any page and type navigator.globalPrivacyControl. It returns true when the signal is on.
| Jurisdiction | Law | Honor GPC or a universal opt-out signal from |
|---|---|---|
| California | CCPA and CPRA, regulations 11 CCR §7025 | In force, enforced since 2022 |
| Colorado | Colorado Privacy Act | July 1, 2024 (GPC is on the Attorney General's approved list) |
| Connecticut | CTDPA | January 1, 2025 |
| Montana | MTCDPA | January 1, 2025 |
| Texas | TDPSA | January 1, 2025 |
| New Hampshire | NHPA | January 1, 2025 |
| Nebraska | NDPA | January 1, 2025 |
| New Jersey | NJDPA | Mid-2025 (six months after the law took effect) |
| Minnesota | MNCDPA | July 31, 2025 |
| Oregon | OCPA | January 1, 2026 |
| Delaware | DPDPA | January 1, 2026 |
Under the CCPA regulations, a business that sells or shares personal information must treat the GPC signal as a valid opt-out of sale and sharing for that browser or device and for any profile linked to it, including the consumer's account when the business knows who they are. Since the updated regulations took effect on January 1, 2026, the business must also show on its website whether it has processed the signal, for example with an "Opt-Out Request Honored" message. See all state laws in our US state privacy laws guide.
Do Not Track (DNT) was an earlier browser header that asked websites not to track the user. No law required websites to honor it, so most ignored it, and browsers such as Safari and Firefox have since removed the setting.
GPC is narrower and has legal force. It asks for one thing, no sale or sharing of personal data, and US state laws turn that request into a binding opt-out. A website that ignores GPC in California or Colorado is not meeting the law.
The GDPR does not name GPC, and no EU regulator has made it a required signal. The GPC specification notes that, in the EU, it can express a general request to limit the sale or sharing of personal data, linked to the right to withdraw consent (Article 7) and the right to object (Article 21).
In practice the GDPR is an opt-in law: you still need consent before setting non-essential cookies, whether or not the visitor sends GPC. Treating a GPC signal as a refusal of advertising cookies for EU visitors is a cautious choice, but it does not replace the GDPR consent banner.
Sec-GPC header on the server or navigator.globalPrivacyControl in the browser.With UniConsent, you respect opt-outs and Global Privacy Control automatically, while your analytics keep working.
UniConsent honors Global Privacy Control automatically for visitors covered by your CCPA or US State Privacy settings. A GPC signal counts as an opt-out of the sale and sharing of personal information and of targeted advertising, without the visitor opening the banner. Other purposes are not affected.
The opt-out is passed to your partners in the IAB GPP US sections, including the GPC field, and in the US Privacy string, and is available as the GPC variable in the data layer for Google Tag Manager. On consent categories banners in the US, GPC turns off the targeting category. In mobile apps, the device's limit ad tracking setting is treated the same way as GPC.
Use a consent management platform like UniConsent to honor GPC, show opt-out choices and pass the signal to your partners from one tag.
The GPC signal is a browser setting that tells websites not to sell or share your personal information. When it is on, the browser sends the HTTP header Sec-GPC: 1 with every request and sets navigator.globalPrivacyControl to true for scripts on the page.
Yes, where the law backs it. In California, Colorado, Connecticut and other US states, businesses must treat a GPC signal as an opt-out of the sale or sharing of personal data and of targeted advertising, and regulators have fined companies that ignored it. GPC does not block tags by itself, so the website or its consent management platform has to act on it.
Yes. The CCPA regulations (11 CCR §7025) require businesses that sell or share personal information to treat a GPC signal as a valid request to opt out of sale and sharing for that browser or device and any linked profile. Since January 1, 2026, the business must also show whether it has processed the signal.
Brave and the DuckDuckGo browser send GPC by default. In Firefox, open Settings, go to Privacy & Security and tick the option that tells websites not to sell or share your data; it is already on in private windows. In other browsers, install an extension that sends GPC, such as Privacy Badger.
The GDPR does not name GPC and no EU regulator has made it a required signal. The GPC specification says it can express a request to limit sale or sharing linked to the GDPR rights to withdraw consent and to object, but websites still need opt-in consent before setting non-essential cookies for EU visitors.
Do Not Track asked websites not to track the user, but no law required websites to honor it, so most ignored it. GPC asks only for no sale or sharing of personal data, and US state laws make that request a binding opt-out.
Get started to make your website and application compliant for EU GDPR, US CPRA, CA PIPEDA etc
Sign upPrivacy laws, consent and compliance updates, a few emails a month.