Checklist

What is the Global Privacy Control (GPC) signal, and how do you test it?

Run the free scan

The GPC signal is a browser opt-out, often sent as Sec-GPC: 1. Enable it in a clean profile and compare cookies and ad requests with a GPC-off visit to the same store URL.

In brief

Global Privacy Control (GPC) is a browser GPC signal that the visitor wants to opt out of the sale or sharing of personal information. Supporting browsers send Sec-GPC: 1, which a GPC checker can confirm. Test a storefront by comparing a clean GPC-off visit with a clean GPC-on visit: cookies, storage, and third-party ad or analytics requests. This page covers the signal, enabling it, and that paired test. The GPC signal present but marketing still loads page covers mismatch diagnosis.

This article explains the Global Privacy Control GPC signal and how to test it on a storefront. It is not legal advice, not a CPRA compliance guarantee, and not counsel on whether any business must honor GPC. Observation is not counsel permission.

A GPC signal on the request shows what the browser sent. It does not, by itself, show that the storefront changed cookies or third-party requests. Last updated October 6, 2026.

Short answer

Global Privacy Control (GPC) is a browser GPC signal that tells a site the visitor wants to opt out of the sale or sharing of personal information. Supporting browsers send a Sec-GPC: 1 HTTP header. To test it, enable GPC in a clean profile, confirm Sec-GPC: 1 on the document request, and compare cookies and third-party ad or analytics requests with a GPC-off visit to the same URL. When the CMP says GPC was detected and the network still matches GPC-off, open the GPC signal present but marketing still loads page. This page is technical testing guidance, not legal advice.

Save both runs. This page covers the GPC signal, how to enable it, and the paired storefront test.

What GPC is

GPC is a preference the browser sends for the visitor. The W3C Global Privacy Control specification describes the signal, over HTTP and through the DOM, as a request that sites not sell or share the person's personal information. Read that specification and the Global Privacy Control site for the wording.

You can confirm the browser sent the signal and still find the same advertising requests as the GPC-off visit. Record those as separate facts. A marketing line that says the store honors GPC is a claim. The paired visits are the check.

  • The visitor's preference: opt out of sale or sharing, in plain language.
  • The browser's signal: Sec-GPC: 1 on requests, and sometimes navigator.globalPrivacyControl in JavaScript.
  • The site's response: which cookies, storage keys, and third-party requests change when the signal is on.

The Sec-GPC header

On a GPC-on visit, the GPC signal arrives as Sec-GPC: 1. Open DevTools, select the document request for the page you loaded, and read the request headers. The GPC specification, which is being standardized in the W3C Privacy Working Group, defines that header value as 1. A missing header means this visit did not send the GPC signal, so do not label the file GPC-on.

A redacted document request can look like this: host shop.example, path /products/example-tee, request header Sec-GPC: 1. Strip cookie values and query secrets before you share the screenshot or the HAR snippet. The example host is illustrative. It is not a live store capture.

Some stacks also expose navigator.globalPrivacyControl in page JavaScript. On the same visit, open the console and read that value. A true result is an optional check. File the header from the document request. A console value without the header is an incomplete GPC-on record.

Sec-GPC: 1 is present — what still needs a second visit

The document-request header answers whether this load sent GPC. File that header. A missing Sec-GPC: 1 means do not label the visit GPC-on.

On the same visit, read navigator.globalPrivacyControl in the console. That check is optional. A console value without the header is an incomplete GPC-on record.

Honor is the diff between a GPC-off visit and a GPC-on visit on the same URL. Compare cookies, marketing hosts, and banner state. The header does not show that the shop stopped tracking.

CMP copy that says GPC was detected is a claim. Network rows are the check.

A free US-baseline scan is not a California GPC conclusion. Pair the visits in the GPC honor evidence pack. California scenarios are on pricing and Billing.

How shoppers enable GPC

Use a dedicated clean profile. Extensions, logins, and leftover consent cookies pollute the cookie table. Close other windows in that profile before you load the shop.

As of September 22, 2026, the Global Privacy Control site lists Brave and DuckDuckGo with the signal on by default, and Firefox with the signal available in privacy settings. Chrome and similar browsers typically need a GPC extension, because they do not ship the same built-in control. Menu labels move. Enable the capability, then confirm Sec-GPC: 1 on the document request before you record cookies or pixels.

Write down the browser and the enable method. If the document request lacks Sec-GPC: 1, fix the profile before you record the rest of the visit.

Storefront test: two isolated runs

Prepare two clean profiles. Use the same public URL, a similar time of day, and no logged-in account unless that path is the test. Write down the region you actually used. A California conclusion needs a California-context run. A free US-baseline visit sits outside that path. Leave the banner untouched unless the written plan requires a click. Change only the GPC signal.

  1. Run A, GPC off. Load the homepage, wait for the banner, and do not click it. Export cookies, storage, and third-party requests. Screenshot the banner. Repeat on one product URL if that template is in scope.
  2. Run B, GPC on. Use a new profile. Confirm Sec-GPC: 1 on the document request. Optionally read navigator.globalPrivacyControl in the console. Record the same cookies, storage, and requests.
  3. Diff the runs. List vendors and cookies present in both, tags you expected to drop on GPC-on that stayed, and any CMP detected state that arrived without a network change.
  4. Save the URL and timestamps. Strip identifier query values before you send the pack.

Swipe to see more

Paired storefront runs for Global Privacy Control. Label every file GPC-off or GPC-on. Technical record, not a legal determination.
RunSetupRecord
A GPC offClean profile, signal off, same URLCookies, storage, third-party ad and analytics requests, banner screenshot
B GPC onClean profile, Sec-GPC: 1 confirmed on the document requestThe same surfaces, plus whether the CMP shows a detected state

CMP copy and the network

A CMP line that says GPC was detected is an interface state. Suppression is a smaller set of cookies and third-party requests on the GPC-on run than on the matched GPC-off run. Record both. If the detected line is on screen and the request list still matches GPC-off, you have a claims-versus-runtime gap.

Open GPC signal present but marketing still loads for the mismatch table. Open the CMP claims versus runtime evidence guide when banner copy and the wire disagree on reject or accept as well. Record the CMP vendor only so engineering can find the integration.

California observation

This section is a testing note for California shoppers. It is not legal advice, and it is not a statement that every site must honor the GPC signal.

If the store says it honors GPC for California shoppers, prove that sentence with the paired runs, on a California-context path, with the header confirmed. A free US-baseline visit records one non-California pass. It does not produce a California GPC conclusion. Read the free versus paid guide before you file that report as a GPC result. The SB 690 page covers lawsuit status. It does not run this comparison.

Evidence pack

Label every artifact GPC-off or GPC-on. Include the cookie table, storage keys, the request URLs you are asking engineering to review, a screenshot or HAR snippet that shows Sec-GPC: 1, a screenshot of the CMP when it shows a detected state, the URL, the browser, and the timestamps.

ConsentProbe maps findings to the request, the cookie, and the screenshot. The California scenario stores the GPC-off visit next to the GPC-on visit.

DIY compared with a California GPC scenario

Use the DIY pair to learn the signal. Use the saved California scenario when you need a repeatable pack tied to requests, cookies, and screenshots.

Swipe to see more

DIY browser profiles compared with ConsentProbe's California GPC scenario. Technical scope only.
CheckDIYConsentProbe California GPC
SetupManual profiles and DevToolsThe scenario runs GPC off, then GPC on
ConsistencyEasy to miss the header or reuse a polluted profileLabeled scenarios you can repeat
EvidenceYou assemble the HAR and screenshotsFindings linked to request, cookie, and screenshot
ScopeEnough to learn the signal and the diffUse when you need a California GPC evidence pack

Save the paired visits

Run ConsentProbe's California scenario when you need the GPC-off and GPC-on visits stored on the storefront URL. A free US-baseline visit remains a format check. This page is technical testing guidance, not legal advice.

FAQ

What is the GPC signal?

A browser preference signal, often sent as Sec-GPC: 1, that communicates an opt-out of sale or sharing. Presence of the GPC signal is not proof the site honored it.

What is the Sec-GPC header?

The HTTP request header set to Sec-GPC: 1 when the GPC signal is on. Confirm it in DevTools on the document request. navigator.globalPrivacyControl in the console is an optional extra check.

How do I test the GPC signal on my storefront?

Enable GPC, confirm Sec-GPC: 1, and compare GPC-off versus GPC-on cookies and marketing requests.

If my CMP shows that GPC was detected, am I done?

No. Compare the GPC-on network and cookies with the GPC-off run. A detected line without a network change is a mismatch. Use the GPC signal present but marketing still loads page for that diagnosis.

Does a free US ConsentProbe scan prove GPC?

No. A free US-baseline visit is one non-California pass. Use the California GPC scenario, or an equivalent DIY pair on a California-context path. Read the free versus paid guide before you stretch the file.

Is honoring GPC required for every site?

That is a legal question. This page covers how to test the signal. Talk to your own counsel about whether your business must honor it.

What do I send engineering or counsel?

Paired GPC-off and GPC-on evidence packs: cookie tables, request URLs, the Sec-GPC header capture, CMP screenshots, timestamps, and the URL. Banner screenshots alone are not the pack.

Use the GPC signal present but marketing still loads page when a detected state and the request list disagree. Use the free versus paid guide before a US-baseline file stands in for a California result.

On Shopify, run the GPC honor test: signal off, then Sec-GPC: 1, same URL. Keep both files in the evidence pack.

Sources

These links cover the platform and regulatory context used in this guide. Applicability still depends on the organization and jurisdiction.

Save a US-baseline technical record

After a DIY check, run a free US-baseline scan: one browser visit outside California, with cookies, requests, and screenshots stored as evidence. That visit does not run EU reject/accept or California GPC. EU, California, and Global 2 audits can be purchased from Billing after sign-in.

What Is GPC (Sec-GPC: 1) and How to Test It | ConsentProbe