Privacy signals are becoming part of everyday web development. On November 18, the WebKit team announced a new API that lets apps embedding web content turn on Global Privacy Control, a W3C signal that tells websites a user wants to opt out of the sale or sharing of their data and cross-context targeted advertising.
Where it works
The API is available in iOS, iPadOS, visionOS and macOS 27. It is aimed at developers of apps that show web pages inside a WKWebView or the SwiftUI WebPage view, rather than at Safari itself.
How apps turn it on
For WKWebView, developers set a globalPrivacyControlEnabled property on the web page preferences used when deciding how to handle a navigation. For SwiftUI’s WebPage, there is an equivalent setting in the navigation preferences. Apple recommends giving users their own setting in the app and applying it on each navigation.
What web developers will see
When the signal is on, websites can read navigator.globalPrivacyControl in JavaScript, and requests include the Sec-GPC: 1 header. According to WebKit, both apply to the main page, embedded frames and subresources.
What this means for designers and front-end teams
If you build sites that use analytics, advertising or consent banners, you should check how they respond to GPC. In some regions, privacy laws treat the signal as a valid opt-out request. A good practice is to detect the signal and reflect it in your consent interface, for example by showing that tracking is already turned off instead of asking the user again.
A step toward consistency
Some browsers already support GPC. Making it available to apps that embed web views means users can get the same privacy signal inside apps, not only in standalone browsers. That reduces the number of places where privacy choices are silently ignored.
Next steps
Check your consent management tools for GPC support, test pages inside an app web view with the signal turned on, and make sure your privacy policy explains how you handle it.
Sources:




