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 Privacy Protection Agency broke its own record, issuing a $2.75 million settlement against a streaming platform for opt-out failures.
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:
- 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.
- GPC isn't applied everywhere. The signal is detected, but some ad tags, pixels or subdomains don't respect it.
- 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:
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.
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.
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.
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.
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.
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.