The new Edge setting comes with two limits. It is available only in the US for now, and Microsoft makes no promise about what websites will do when they receive the signal. Chrome is further behind. Google's work on GPC is still in prototype and Canary flags, not in the stable browser.
What Microsoft actually shipped
Microsoft's support page for the feature confirms that Microsoft Edge users can now set Global Privacy Control (GPC) preference within the browser. Once the setting is on, the GPC signal will be shared with websites you visit to indicate your preference that your data is not sold or shared for targeted advertising.
The same page also sets limits on what the feature does:
- Regional availability: The GPC Setting is currently available in the US. Microsoft has not given a version number, a rollout percentage or a date for other regions.
- No guarantee: Microsoft says plainly that websites may or may not honor this signal, even if Microsoft Edge is sending it.
- Applies to every site: When the GPC preference is enabled in Microsoft Edge, all sites that you visit receive the signal. There is no per-site allow list in the documented setting.
Neowin first reported the change after finding the support article. It noted that until now, on Chrome and Edge, users have had to rely on third-party browser extensions and add-ons.
In short: Edge now has a native GPC switch for US users. It asks websites not to sell or share your data, and websites decide whether to comply.
How to turn on Global Privacy Control in Edge
Microsoft's documented steps:
- Open Microsoft Edge.
- Go to the top-right corner and select Settings and more (...), then select Settings.
- Select Privacy, search, and services > Privacy > Global Privacy Control.
- Turn the setting on.
Checking that it works. The GPC project's website detects the signal when you visit it. PiunikaWeb used this method while testing Chrome Canary and saw a "GPC signal detected" message once the signal was enabled. Advanced users can also open DevTools on any page and check navigator.globalPrivacyControl in the console. The W3C specification defines this JavaScript property alongside the Sec-GPC: 1 request header.
Troubleshooting:
- The setting isn't there. Microsoft says the setting is available in the US. If you are outside the US, or your Edge build hasn't received it yet, you won't see the toggle, and Microsoft hasn't said when that will change.
- An open tab doesn't show the change. The W3C draft says the preference is cached when a top-level page starts loading. A change made after that only takes effect on the next navigation, so reload the page.
- You're getting the header twice. If you already use a GPC extension such as Privacy Badger or DuckDuckGo Privacy Essentials, consider removing it once the native setting is on, so you only have one thing to troubleshoot. The spec says browsers must not send more than one
Sec-GPCheader per request, and servers must handle duplicates. Duplicates are untidy but shouldn't break anything. - Managed PCs. Microsoft's support article does not mention a Group Policy or Intune setting for GPC. Admins should not assume one exists until it appears in Edge's policy documentation.
What GPC does and doesn't do
GPC has two parts. The browser adds an HTTP request header, Sec-GPC: 1, and the character '1' is the only allowed value for the header. It also sets a JavaScript property, navigator.globalPrivacyControl, which sites can read. Websites can optionally publish a file at .well-known/gpc.json to indicate how they respond to the GPC signal. This is useful for developers who want to state their compliance in a machine-readable way.
The obvious comparison is Do Not Track, the earlier opt-out header that most websites ignored. The difference is legal backing. Unlike the now-deprecated Do Not Track header, which was unsuccessful as it was ignored by third parties, GPC is intended to have legal force under privacy laws. California's Attorney General says GPC must be honored by businesses covered by the California Consumer Privacy Act (CCPA) as a valid request to stop the sale or sharing of personal information.
The scope is narrower than a general "stop tracking" switch:
- The W3C draft says GPC is not meant to exercise deletion rights.
- It is not meant to limit how a site uses your data within its own service, for example a publisher showing ads based on what you read on that publisher's site.
- Its legal effect depends on where you live and which law applies. Several US states recognize universal opt-out signals. Others are silent on them.
- GPC is still being standardized. The latest W3C publication is a Working Draft dated September 24, 2026, not a final Recommendation.
In short: GPC sends a request with some legal weight in certain jurisdictions. It does not block anything technically. Keep using tracking prevention, content blocking and site-level privacy choices.
Where Chrome stands: prototype and Canary flags
Chrome does not yet have a GPC setting in its stable release.
On January 6, 2026, Chromium contributor Maciej Czarnecki posted an "Intent to Prototype: Global Privacy Control" on the blink-dev mailing list. The proposal covers three things:
- a user preference to turn the signal on
- the
Sec-GPC: 1header sent on all outgoing requests when it is on - the
navigator.globalPrivacyControlJavaScript property
The internal preference key is enable_global_privacy_control. His first code change had no user-facing setting. He wrote that decisions were still needed about where the setting should live and how it should be labeled.
Google's Mike West called a prototype in Chromium's core layers "quite reasonable." He suggested each Chromium-based browser build its own settings and explanatory text, because those choices could have legal and policy implications. That is relevant to Edge, which is built on Chromium. Shared plumbing in Chromium and separate settings screens in each browser would fit the pattern Microsoft is now following.
Neowin reports that the work was merged into Chromium's main branch in July. PiunikaWeb then found a "Force Global Privacy Control signal" flag in Chrome Canary 153.0.8002.0 in August. In PiunikaWeb's testing, the signal was sent when the flag was set to Enabled and was not sent when it was set to Disabled or left at Default. PiunikaWeb also said there was no sign the flag was ready for stable Chrome.
An Intent to Prototype is an early step, not a commitment to ship. Neowin's expectation of a wider rollout is speculation. Google has announced no date for stable Chrome.
The California deadline behind the timing
Both browsers may be on a schedule. The Chromium proposal cites a California bill under the CCPA/CPRA that requires browsers to let users send a do-not-sell-or-share preference before 2027. The proposal also argues that a GPC extension may not be enough to comply.
Cookiebot's GPC guide identifies the measure as AB 566, effective January 1, 2027. It says that once Chrome and Edge ship native support ahead of the January 2027 mandate, GPC is set to become a default setting for a substantial share of all web traffic. That forecast is Cookiebot's. Also, Cookiebot's browser table, published about 75 days ago, still lists Edge as "Not Yet," which shows how recent Microsoft's change is.
The deadline is one reason Edge's setting is US-only for now. It doesn't explain why Microsoft limited it to the US rather than just California.
How the browsers compare
| Browser | GPC status (per sources reviewed) |
|---|---|
| Microsoft Edge | Built-in setting, US only, documented by Microsoft |
| Google Chrome | Stable: none. Canary: experimental flag |
| Firefox | Built-in, available in settings |
| Brave | Built-in and on by default on desktop and Android. On iOS the HTTP header is not sent, according to Brave |
| DuckDuckGo | Built-in and on by default |
Neowin described Firefox as having GPC enabled by default. The GPC project lists Firefox as "available in settings" and Brave and DuckDuckGo as on by default. The table follows the GPC project's description.
In short: Edge has moved ahead of Chrome but has not caught up with the privacy-focused browsers. They turn GPC on by default, and Edge makes it an opt-in setting.
Analysis
Neowin points out that this comes shortly after Edge's AI troubleshooting tool raised data-collection concerns. A GPC toggle doesn't address those concerns, but it does give users a cheap, legally recognized way to state a preference.
Some caveats:
- Edge's setting is opt-in, not on by default. The W3C draft notes that many US states say a browser may not send a universal opt-out signal "by default." That may explain Microsoft's choice.
- The setting asks websites not to sell or share your data. It doesn't stop collection.
- If you are outside the US, you can still get GPC in Edge through the long-standing extensions until Microsoft expands availability.
For US Edge users, turning the setting on costs nothing and has legal effect with CCPA-covered businesses. Just don't treat it as a replacement for Edge's tracking prevention.
References
- Chrome, Edge finally getting a key feature built-in which Firefox, Brave has had for years Neowin · 2026-10-24T20:24:02+00:00
- Chrome Canary now has a dedicated flag to force the Global Privacy Control signal piunikaweb.com
- Global Privacy Control & Universal Opt-Outs cookiebot.com