Global Privacy Control (GPC) is a browser-level signal that tells every website a user visits that the person does not want their personal data sold or shared. Within privacy, and in the field of cookies & consent in particular, GPC works as a universal opt-out mechanism: the user sets the preference once in a browser or extension, and the browser transmits it automatically with each request.
Unlike earlier voluntary signals, GPC was designed to carry legal weight. Several US state privacy laws, led by California, require businesses to treat a GPC signal as a valid opt-out request, which turns a simple technical flag into an enforceable instruction rather than a polite suggestion.
How the GPC signal is transmitted
GPC is transmitted through two technical channels defined in its specification. The browser adds the HTTP request header Sec-GPC: 1 to outgoing requests, and it exposes the JavaScript property navigator.globalPrivacyControl, which returns true when the signal is enabled. Server-side code reads the header, while scripts on the page, including a consent management platform, read the property.
Websites may also publish a small JSON file at /.well-known/gpc.json to declare that they honor the signal. This declaration is optional and does not change legal obligations, but it helps auditors and researchers verify compliance claims. The specification is developed within the W3C standards process.
The table below lists the components a site typically handles.
| Component | Where it appears | Who reads it |
|---|---|---|
Sec-GPC: 1 header | Every HTTP request | Web servers and edge logic |
navigator.globalPrivacyControl | Browser JavaScript environment | Consent tools and tag managers |
/.well-known/gpc.json | Website root directory | Auditors and research crawlers |
| Browser or extension setting | User interface | The user who enables it |
Legal status of GPC across jurisdictions
The legal force of GPC depends on where the user lives and which law applies to the business. In California, the regulations under the CCPA as amended by the CPRA require businesses to process an opt-out preference signal as a request to opt out of the sale or sharing of personal information. The first public enforcement action, a 2022 settlement with a cosmetics retailer for 1.2 million dollars, centered on failing to honor GPC.
Colorado formally recognized GPC as a universal opt-out mechanism, with obligations applying from July 2024, and other states, including Connecticut, Texas, Oregon, Montana and New Jersey, have adopted comparable requirements. California also enacted a law in 2025 that will require browsers to offer an opt-out preference setting from 2027.
The comparison below summarizes the position in key jurisdictions.
| Jurisdiction | Legal effect of GPC | Practical consequence |
|---|---|---|
| California | Binding opt-out of sale and sharing | Must be honored without extra steps |
| Colorado | Recognized universal opt-out mechanism | Mandatory since July 2024 |
| Other US states | Universal opt-out signals required by statute | Phased effective dates |
| European Union | Debated as an automated objection under the GDPR | No settled obligation yet |
| Most other countries | No specific recognition | Voluntary to honor |
In the EU, Article 21(5) GDPR allows individuals to object by automated means using technical specifications, and some commentators argue GPC fits that wording. Regulators have not confirmed this interpretation, so its status under European law remains uncertain and contested.
GPC compared with Do Not Track and consent banners
GPC is best understood as the successor to Do Not Track (DNT), a header introduced around 2010 that failed because no law obliged sites to respect it and its meaning was never standardized. GPC narrows the scope to a clearly defined legal right and ties itself to statutes, which gives it the enforcement backbone DNT lacked.
It also differs from a consent banner or a reject all button. A banner collects a choice site by site, whereas GPC expresses a single standing preference across all sites. The two often coexist: a consent management platform reads GPC and pre-sets the opt-out before showing any remaining choices.
| Mechanism | Scope | Legal backing | Granularity |
|---|---|---|---|
| Global Privacy Control | All sites, one setting | Yes, in several US states | Single opt-out flag |
| Do Not Track | All sites, one setting | None in practice | Undefined meaning |
| Consent banner | One site at a time | GDPR and ePrivacy Directive | Per purpose or vendor |
| IAB TCF string | Participating vendors | Industry framework | Per purpose and vendor |
Implementing GPC on a website
Implementing GPC correctly means detecting the signal before any data leaves the page. A typical setup checks navigator.globalPrivacyControl in the consent management platform, then suppresses advertising and cross-context tracking tags that would constitute a sale or sharing of personal data.
- Detect the signal on the server through the header and in the browser through the JavaScript property.
- Map the signal to the correct legal right, such as opt-out of sale, sharing or targeted advertising.
- Block or reconfigure affected tags, pixels and server-side data feeds immediately.
- Associate the opt-out with a known account or profile when the user is logged in.
- Display a confirmation such as “Opt-out request honored” where regulations expect it.
- Record the processing of the signal for audit and enforcement evidence.
Businesses must not ask users to confirm the signal through extra clicks or override it with a pre-ticked choice. A conflicting earlier consent may be addressed only in the ways the applicable rules permit, and California rules allow a business to ask, but not to ignore the signal by default.
Limitations and common mistakes
GPC is powerful but narrow by design. It communicates one preference, opting out, and it cannot express nuanced consent, such as allowing analytics but refusing advertising. Browser support is also uneven: Brave and DuckDuckGo send it by default, Firefox offers a setting, while Chrome and Safari require an extension.
The table below lists frequent implementation errors.
| Mistake | Consequence | Fix |
|---|---|---|
| Reading the signal only after tags load | Data already shared before opt-out | Check GPC before firing any tags |
| Ignoring server-side data flows | Sale continues through back-end feeds | Apply the opt-out to server pipelines |
| Not linking to logged-in profiles | Opt-out lost on other devices | Store the preference on the account |
| Treating GPC as GDPR consent refusal by default | Incorrect legal mapping | Assess each jurisdiction separately |
A final limitation concerns identity: GPC applies to the browser that sends it, so a person who uses several devices must enable it on each one unless the business links the preference to an account.
The idea in brief
Global Privacy Control is like a standing note your browser hands to every website, saying: please do not sell or share my information. You switch it on once in your browser settings or with a small add-on, and it works everywhere you go.
In some places, especially California and Colorado, websites are legally required to obey that note. That makes it more useful than clicking through dozens of cookie pop-ups, although it covers only one choice: saying no to selling or sharing your data.
A practical scenario
An online furniture retailer with customers across the United States runs advertising pixels and shares browsing data with ad partners. A shopper in Los Angeles uses a browser that sends Sec-GPC: 1 by default. The retailer’s consent management platform detects the signal on page load and disables all advertising and retargeting tags before they fire.
When the shopper later logs in, the retailer attaches the opt-out to the customer account, so the preference also applies in the mobile app and in a weekly data feed that previously went to a marketing partner. The compliance team logs each processed signal and reviews the records quarterly. During a state privacy audit, the retailer demonstrates that GPC requests were honored within milliseconds and across server-side flows, and the audit closes without findings.