Google Chrome Tests Visible Global Privacy Control Toggle in Canary

Google is testing a new visible toggle for Global Privacy Control in Chrome Canary that lets users send a standardized request asking websites not to sell or share their personal data and not to use it for targeted advertising. When enabled, the browser adds the Sec-GPC: 1 header to web requests and exposes the setting via navigator.globalPrivacyControl. In regions with supporting laws such as California's CCPA, the signal can serve as a formal opt-out from data sales. The feature currently appears primarily on Android, with experimental flags available on Windows, macOS, Linux, and ChromeOS, though the desktop interface remains incomplete. Two separate flags are required—one to show the toggle and another to actually transmit the signal—because enabling only the UI does not send Sec-GPC: 1. The mechanism is not a guaranteed enforcement tool; websites decide how to respond, and effectiveness depends on legal frameworks and site compliance. The feature is absent from the stable Chrome release and may still change before wider rollout.

AntiMalwareTranslated from Russian

Read at source

Google is testing a visible toggle for Global Privacy Control (GPC) inside Chrome Canary. The control lets users send a single request asking websites not to sell or share personal data and not to use it for targeted advertising.

When the toggle is enabled, the browser automatically adds the Sec-GPC: 1 header to outgoing web requests and exposes the corresponding value through the navigator.globalPrivacyControl JavaScript property. In jurisdictions with compatible legislation, such as California’s CCPA, this signal can be treated as a formal “Do Not Sell or Share” opt-out.

The new switch appears in the privacy section of Chrome Canary, primarily on Android. Experimental flags also exist for Windows, macOS, Linux, and ChromeOS, although the desktop user interface is not yet fully implemented.

During testing, researchers discovered that two separate flags must be activated: one to display the toggle and another (Force Global Privacy Control Signal) to actually transmit Sec-GPC: 1. Simply enabling the visible button is insufficient.

Even after full activation, GPC remains a request rather than an enforceable command. Websites determine their own response, and real-world impact depends on both technical support for the standard and the legal requirements of each region.

The feature is not yet present in the stable version of Google Chrome and its final behavior may still change before wider release.

Meridian digestThe week's most consequential security stories, distilled into one briefing.See the digest

More in Privacy & Surveillance

Maximizing iPhone Privacy: Essential Settings to Enable, Disable, and Verify Immediately
Top 10 Secure DNS Servers for Privacy, Threat Blocking and Ad Filtering in 2026
WebRTC IP Leaks Explained: Why Disabling the Protocol Harms Anonymity in Anti-Detect Browsers