When a visitor's browser sends Global Privacy Control, DPDP Comply detects it, records a compliant opt-out granting only essential purposes, and never interrupts them with a banner. Honoring a choice they've already made — the way it should work.
On by default · A per-project toggle you control
What is GPC?
Global Privacy Control (GPC) is a preference a visitor sets once and their browser then sends to every site they visit. It travels as the Sec-GPC: 1 request header and is exposed to JavaScript as navigator.globalPrivacyControl. Instead of clicking through a cookie banner on every site, a person opts out of non-essential processing up front — and expects you to listen.
How it works
The consent widget acts on GPC before any non-essential tag can run — no configuration required beyond the toggle that's already on.
The widget reads the Sec-GPC request header on the server side and navigator.globalPrivacyControl in the browser. Either one marks the visitor as opted out.
When GPC is present, the visitor is never shown the consent banner. Their pre-expressed choice is respected silently, before any tag would run.
A consent record is written granting only your required, essential purposes — everything optional stays denied — with the source tagged as GPC.
“Respect Global Privacy Control” is a per-project toggle, on by default. Turn it off for a project and the banner behaves normally again.
Every GPC opt-out is written to your audit trail as a distinct auto-denied-via-GPC event — so you can prove, and report on, exactly how many visitors' pre-expressed choices you honored.
Where the signal comes from
GPC is an open standard, so the same signal arrives whatever the visitor uses — some browsers turn it on for everyone, others make it a setting.
Sends GPC by default
Browser & extension, on by default
Opt-in privacy setting
Privacy Badger and others
Why it matters
India's DPDP Act 2023 requires consent that is free, specific, informed and unambiguous (Section 6), and that withdrawal is as easy as giving it (Section 6(4)). Acting on a signal a visitor has already set respects the spirit of those obligations — you are not extracting a click for processing they've declined.
The same posture carries across regimes: GPC is recognized as a valid opt-out mechanism under frameworks like the GDPR and California's CCPA/CPRA. DPDP Comply respecting GPC out of the box means one setting covers visitors regardless of where they browse from. GPC is not specifically mandated by the DPDP Act; honoring it is a best-practice signal of good faith, not a statutory requirement of that Act.
FAQ
Global Privacy Control is a browser-level privacy signal — a standardized “do not sell or share my personal information” preference that a visitor sets once and their browser then sends to every site. It travels as the Sec-GPC HTTP request header (Sec-GPC: 1) and is exposed to JavaScript as navigator.globalPrivacyControl. It lets a person express an opt-out choice up front, instead of clicking through a banner on every site they visit.
Yes. When a project has “Respect Global Privacy Control” enabled — which is the default — the consent widget honors the signal automatically. It detects GPC via the Sec-GPC header the server sees and via navigator.globalPrivacyControl in the visitor's browser, and treats the visitor as opted out of non-essential processing.
The widget records a consent decision that grants only your required, essential purposes and leaves every optional purpose denied — without ever showing the banner. The record is tagged with a GPC signal source and logged distinctly (as an auto-denied-via-GPC event) so it is easy to filter in your reporting. If Google Consent Mode is enabled for the project, the consent state is emitted as denied to match.
Yes. “Respect Global Privacy Control” is a per-project setting in the banner configuration, enabled by default. If you turn it off for a project, the widget ignores the GPC signal for that project and shows the banner as usual.
Brave sends GPC by default, and DuckDuckGo's browser and extension enable it by default as well. Firefox offers GPC as an opt-in privacy setting, and browser extensions such as Privacy Badger can add the signal to other browsers. In every case the browser sends the same Sec-GPC header and exposes navigator.globalPrivacyControl.
Add the DPDP Comply widget and pre-expressed opt-outs are respected automatically — with a compliant record and a defensible audit trail behind every one.
Get Started — It's FreeNo credit card required · Setup in under 10 minutes