Clym Logo

What Is Global Privacy Control (GPC)? What Changes for Websites on Jan. 1, 2027

Published
Updated
AS
AuthorAdam Safar
7 min read

Global Privacy Control explained

Global Privacy Control (GPC) is a browser setting that automatically tells every website a person visits not to sell or share their personal data. In California and a growing number of states, businesses must treat that signal as a valid opt-out request. Starting Jan. 1, 2027, California requires web browsers to offer it.

Summarize full article with:

If you have a cookie consent banner on your website, you might think your privacy obligations are covered. They are not. There is a separate, automated privacy signal that millions of users are sending to every website they visit, silently, before they ever click anything. It is called the Global Privacy Control, and 12 US states now legally require your website to honor it.

In this post, we will explain exactly what Global Privacy Control is, which states require it, what the fines look like when businesses ignore it, and the three steps your website needs to take to address it.

Key takeaways

  • GPC is a browser signal that tells websites not to sell or share a visitor's personal data. California and a growing list of states require businesses to honor it.
  • From Jan. 1, 2027, California's Opt Me Out Act (AB 566) requires browsers to give users an easy-to-find setting that sends the signal, so more visitors will arrive with GPC switched on.
  • Many websites already miss it. A DataTrue test of 242 major U.S. sites found about 3 in 4 sites with ad trackers didn't fully honor GPC.
  • Regulators penalize setup failures, not just missing tools. California fined retailer Todd Snyder $345,178 after its consent banner and GPC handling stopped working and nobody noticed.

What is Global Privacy Control?

Global Privacy Control (GPC) is an open technical standard that allows users to signal their privacy preferences through their browser. When a user turns on GPC, their browser sends an automatic HTTP header to every website they visit. That header says, in effect: do not sell or share my personal data.

The signal is sent automatically, before any user interaction. Under US state privacy laws that recognize GPC, this signal carries the same legal weight as if the consumer had manually clicked a "Do Not Sell or Share My Personal Information" link on your website.

Browsers that send GPC signals include Brave (50+ million monthly active users) and DuckDuckGo's mobile browser. Firefox and several Chrome extensions also support it. Estimates from 2025 put GPC signals at roughly 5 to 10 percent of all web traffic, a share expected to grow as browser adoption expands.

What changes on Jan. 1, 2027?

Until now, sending GPC usually meant using a privacy-focused browser such as Brave or DuckDuckGo, switching it on in Firefox, or installing an extension. California's Opt Me Out Act (AB 566), signed Oct. 8, 2025, changes that. From Jan. 1, 2027, companies that make web browsers must include an easy-to-find setting that sends an opt-out preference signal to every site a California user visits, and must explain how it works.

The law doesn't require the setting to be on by default, so users still choose to turn it on. But mainstream browsers are already moving: Microsoft Edge now offers a native GPC setting in the U.S., and Google has begun rolling out a similar option in Chrome. For businesses, the obligation itself isn't new. California already requires covered businesses to honor GPC. What changes is how many visitors will send it.

Which states require businesses to honor GPC signals?

As of 2026, 12 US states legally require businesses to recognize and act on GPC signals, according to legal analysis from Gunster: California, Colorado, Connecticut, Delaware, Maryland, Minnesota, Montana, Nebraska, New Hampshire, New Jersey, Oregon and Texas. Louisiana joins the list on Jan. 1, 2027, when its new privacy law takes effect. Not every new state law follows this pattern: Oklahoma's (Jan. 1, 2027) and Alabama's (May 1, 2027) laws do not require businesses to honor opt-out signals, according to ArentFox Schiff and DLA Piper.

State

GPC required since

Key rule

California

2022 (CPRA)

Must also display visible confirmation from Jan 2026

Colorado

2024 (CPA)

Treat GPC as a valid opt-out of data sale/sharing

Connecticut

2025 (CTDPA)

Treat GPC as a valid universal opt-out signal

Delaware, Maryland, Minnesota, Montana, Nebraska, New Hampshire, New Jersey, Oregon, Texas

2024–2026

Treat GPC as a valid universal opt-out signal

Louisiana

Jan. 1, 2027 (LDPA)

Must honor opt-outs sent through browser or device settings

Importantly, there is no small-business exemption under most of these laws. If your business meets the applicability threshold for the state law, the requirement applies to you. You can view details on each relevant regulation through Clym's regulation guides, or see how applicability thresholds compare across all 20 active U.S. state laws in our state privacy law comparison guide.

GPC enforcement: the fines businesses have paid

This is not a theoretical risk. Regulators have already issued significant fines tied directly to GPC non-compliance.

In 2022, Sephora paid $1.2 million in California, partly for failing to honor opt-out requests sent through GPC signals. In 2025, Tractor Supply Company settled for $1.35 million over similar failures.

Then in February 2026, the California Attorney General announced a $2.75 million settlement with Disney, at the time the largest CCPA settlement. Among other failures, when a logged-in user sent a GPC signal, Disney applied the opt-out only to the device in use.

November 2026 brought three more. California’s privacy agency fined FedEx $2.975 million, partly for failing to honor opt-out signals. It then fined Hertz $1.55 million for failing to process opt-out preference signals, and ordered the company to test its opt-outs every quarter across browsers and devices and to report how many opt-out requests arrived through those signals. Two days later, Polaris was fined $910,986 for failing to honor the signals, in a joint investigation with the Minnesota Attorney General, which collected another $150,000 under Minnesota’s privacy law.

Not every case involves ignoring GPC on purpose. In May 2025, the California Privacy Protection Agency fined clothing retailer Todd Snyder $345,178. For 40 days in late 2023, its cookie banner appeared and vanished almost immediately, and the same misconfiguration meant the site didn't recognize GPC. The agency said the company relied on third-party privacy tools "without knowing their limitations or validating their operation," and ordered it to monitor whether its opt-out methods actually work.

California has since tightened its rules further. Under regulations that took effect January 1, 2026, businesses must now do more than silently process a GPC signal in the background. They must also display a visible confirmation to users, such as a badge or notification confirming that their opt-out request has been honored. A cookie banner alone does not satisfy this requirement.

More changes are coming. In November 2026, California's privacy agency advanced proposed rules that would name GPC as a valid signal, require businesses to apply opt-outs across all their websites and apps, and make clear the signal must be honored before tracking cookies are set. The proposal is not final yet.

Why most websites are not ready

Part of the problem is awareness, and it is most acute among smaller businesses. Cisco's 2025 Data Privacy Benchmark Study found that organizations with 50 to 249 employees were the only company size category to reduce their privacy spending year over year, even as the number of state laws requiring action continued to grow.

Cookie consent banners became familiar after GDPR. They gave business owners something visible to point to. The GPC signal is invisible by design. It arrives in the HTTP header of a web request, before any user interaction takes place, and most website owners have no idea it is being sent.

The scale of the gap is striking: the GPC protocol has grown from fewer than 7,000 active domains in 2022 to more than 459,000 by mid-2025 (a roughly 67-fold increase). That growth reflects rising browser adoption among users, not rising compliance among businesses.

Even large organizations struggle, and often not because they lack a privacy tool. The tool just isn't doing its job. Recent tests show how common that is:

  • A 2026 audit found that 73% of major U.S. hospital websites kept running ad trackers with GPC switched on.
  • DataTrue tested 242 major U.S. websites in October 2026: about 3 in 4 sites with ad trackers didn't fully honor GPC, and 20 of 24 sites with a clear "Reject" button kept connecting to ad companies after it was clicked.
  • webXray scanned 7,634 sites from California in March 2026: 55% set advertising cookies even with GPC turned on.
  • Consumer Reports and Wesleyan University found that 12 of 40 online retailers appeared to keep retargeting visitors after receiving GPC.

These failures usually fall into three patterns:

  1. Tracking starts before the choice. Tags fire on page load, before the consent tool has read the GPC signal or the visitor's banner choice.
  2. GPC isn't applied everywhere. The signal is detected, but some ad tags, pixels or subdomains don't respect it.
  3. Something breaks and nobody notices. A site update, new tag or misconfigured banner quietly stops opt-outs from working.

A connection to an ad company doesn't by itself show what data was sent or that a specific law was broken, as DataTrue notes. But regulators treat these gaps as the business's responsibility.

What your website needs to do to honor GPC

Addressing the universal opt-out requirement involves five steps:

  1. Detecting the signal. Your website needs to be able to identify when an incoming HTTP request carries a GPC header. This requires technical implementation, either through custom code or a consent management platform that handles detection automatically.

  2. Acting on it. When the signal is detected, you must stop selling or sharing that user's personal data for the duration of that session and beyond. This typically means suppressing third-party tracking scripts and data-sharing integrations for that user.

  3. Confirming it (California only, from Jan 2026). In California, you must also display a visible confirmation to the user that their opt-out preference has been registered.

  4. Honoring it before anything fires. GPC should be applied before ad tags, pixels or sale/share cookies load, not after. California's proposed rules would make this explicit.

  5. Checking that it keeps working. Confirm GPC handling is switched on, then re-test after site changes, new tags or new vendors. As the Todd Snyder case shows, a tool that quietly stops working is still the business's responsibility.

A detected GPC signal can affect advertising, analytics, attribution, and audience-building activities, not just privacy controls. Read our guide on what a detected GPC signal means for your marketing and analytics.

For most websites, implementing GPC detection from scratch requires developer resources and ongoing maintenance, and every site change is another chance for it to break. The more practical approach is a consent management platform that supports GPC detection natively, so the signal processing and privacy controls happen automatically.

How Clym supports Global Privacy Control

Clym's Global Privacy Control solution is built into the platform's consent management framework. When you add Clym's script to your website, it automatically detects GPC signals from all major browsers and extensions, then applies the appropriate privacy controls based on the user's jurisdiction, with no custom development required.

To check what your own website does when GPC is on, use Clym Pulse, our free Chrome extension.

Here is how it works in practice:

  • Automatic signal detection. Clym identifies GPC signals from any browser or extension that sends them, including Brave, DuckDuckGo, Firefox and Microsoft Edge, without any manual configuration.

  • Jurisdiction-based application. GPC signals are applied based on the user's location and the applicable privacy regulations in that jurisdiction, using Clym's geofencing capability.

  • Seamless integration with consent. GPC signals are processed within the same consent framework as your explicit opt-out mechanisms, including Google Consent Mode and IAB TCF.

  • User override option. You can optionally allow users to override their browser's GPC signal if they want to provide different preferences, giving you flexibility in how you manage user choice.

  • Pre-configured regulatory profiles. Clym's ReadyCompliance® feature means your GPC settings are pre-configured based on your regulatory profile, so the implementation is structured from day one.

Conclusion

Global Privacy Control is no longer a technical curiosity. It is a legal requirement in a growing number of US states, it is enforced with real fines, and from Jan. 1, 2027, every browser used in California must offer it.

The gap between user adoption and business readiness is growing. With Edge and Chrome adding built-in settings, the share of visitors sending GPC is set to grow. Enforcement activity from California is escalating. And the requirement to visibly confirm opt-out requests adds a layer that a traditional cookie banner cannot cover.

The practical path forward is to use a consent management platform that handles GPC detection, jurisdiction-based processing, and user confirmation automatically. That way, when a user arrives with a GPC signal active in their browser, your website is already set up to respond correctly.

Frequently asked questions

A cookie consent banner is a user-facing interface that asks visitors to make a consent choice. Global Privacy Control (GPC) is an automated browser signal that sends a privacy preference before any user interaction. A cookie banner does not detect or honor GPC. These are two separate mechanisms, and businesses in relevant US states need both.

Yes. Eleven other US states beyond California now require businesses to honor GPC signals: Colorado, Connecticut, Delaware, Maryland, Minnesota, Montana, Nebraska, New Hampshire, New Jersey, Oregon, and Texas. The obligation applies if you process personal data of residents in those states, regardless of where your business is based.

Ignoring GPC signals in US states that require you to honor them exposes your business to regulatory enforcement. California has issued fines ranging from $1.2 million to $2.75 million for opt-out failures. There is no small-business exemption under most state privacy laws.

It means the website detected the GPC setting in your browser and treated it as a request not to sell or share your personal data. California has required websites to show a confirmation like this since January 1, 2026. You do not need to do anything else on that site.

GPC signals are sent as an HTTP header and as a JavaScript property (navigator.globalPrivacyControl). You can detect them with custom code, but the most common approach is a consent management platform that supports GPC natively, automating detection and the downstream privacy controls without developer intervention.

Brave sends GPC by default. DuckDuckGo's mobile browser also sends it by default. Firefox users can enable it manually. Several Chrome extensions (such as Privacy Badger) add GPC support. As of 2025, GPC signals are estimated to appear in 5 to 10 percent of web traffic.

Adam Safar

Head of Digital Marketing

Adam is the Head of Digital Marketing at Clym, where he leverages his diverse expertise in marketing to support businesses with their compliance needs and drive awareness about data privacy and web accessibility. As one of the company’s original team members, Adam has been instrumental in shaping its journey from the very beginning. When he’s not diving into marketing strategies, Adam can be found cheering on his favorite sports teams or enjoying fishing.

Find out more about Adam