WebKit's new Global Privacy Control API is a change for sites and developers, not a switch you flip in Safari's settings. If you came looking for a GPC toggle on your iPhone, iPad, or Mac, this release does not add one.
Developers should test GPC behavior in Safari on iOS 27, iPadOS 27, visionOS 27, and macOS 27, then confirm each site responds correctly when GPC is enabled.
In this guide, I have covered:
Contents
Safari Adds a Global Privacy Control API
You saw “Global Privacy Control” mentioned next to Safari and went looking for a setting to turn on. There isn’t one in this change. What shipped is an API.
According to the official WebKit announcement, WebKit now provides Safari with an API for enabling Global Privacy Control (GPC), an emerging web standard. The post covers browser-platform plumbing, not a new item in Safari’s settings.
Platforms Covered
Which releases actually carry the API? The WebKit post names four:
- iOS 27
- iPadOS 27
- visionOS 27
- macOS 27
Because the API is part of WebKit, it is available to Safari on each listed Apple platform release. If you test on one platform and your site supports the others, repeat the test where your visitors actually browse.
The source does not state that GPC is enabled by default in Safari. It says WebKit now offers an API that can enable it.
What the Safari GPC API Changes for Developers
If your site already honors GPC, the hard part is not building the behavior. It is knowing where to test it. Use the announcement to confirm platform availability, then plan Safari coverage across every release you support.
- Read the official WebKit post for the supported releases and API details.
- Test your site’s GPC behavior in Safari on each relevant operating system.
- Confirm your site responds correctly when GPC is enabled.
You’ll know it worked when Safari on each platform returns the response your site’s GPC handling expects. If one release behaves differently, treat that as a test gap you still need to close.
What Safari Users Can Check
Nothing here asks you to change a setting. This update describes no new GPC switch in the Safari interface, so there is nothing to enable before you browse.
Want to review the privacy controls Safari already offers? See Safari’s privacy and security settings on iPhone and iPad. That guide covers existing browser settings, while this update concerns the new WebKit API.
For developers, the next step runs the other way: read the announcement and test GPC behavior on any site that relies on it.
Frequently Asked Questions
Which Apple platforms include the new GPC API?
WebKit lists iOS 27, iPadOS 27, visionOS 27, and macOS 27 as the platform releases covered by the new API.
Does the update add a GPC control to Safari?
The source does not describe a new visible GPC switch in Safari. It covers an API that lets web content enable GPC.
What should web developers check?
The official announcement provides the supported platform list and API scope. Developers should also verify GPC behavior in Safari on each platform their site supports.
Is GPC enabled by default in Safari?
The source does not make that claim. It says WebKit now provides an API to enable GPC and describes GPC as an emerging web standard.
