TL;DR
- John Wilander's WebKit post of 18 November 2026 says iOS, iPadOS, visionOS and macOS 27 apps can now switch on GPC for the pages they load.
- Apple's docs give the defaults as NO for WKWebpagePreferences.globalPrivacyControlEnabled and false for the SwiftUI WebPage property.
- Once an app enables it, WebKit sends Sec-GPC: 1 and exposes navigator.globalPrivacyControl for the main frame, subframes and subresources.
- The post cites California's CCPA page on opting out of sale or sharing via GPC and does not mention Safari, Google or Thailand.
Apple's WebKit team said on 18 November 2026 that iOS, iPadOS, visionOS and macOS 27 include a new WebKit API that lets apps turn on Global Privacy Control (GPC) for the web pages they load. When an app enables it for a navigation, WebKit sends the Sec-GPC: 1 request header and exposes navigator.globalPrivacyControl to the page. The setting is off by default, and each app decides whether to offer it to its users. The details come from a post on the WebKit blog by John Wilander and the two Apple Developer Documentation pages it links to.
What Apple announced on 18 November 2026
John Wilander wrote on the WebKit blog on 18 November 2026 that iOS, iPadOS, visionOS and macOS 27 now have a WebKit API to enable Global Privacy Control, which he called "an emerging web standard." The audience is app developers. The post says that a developer using WebKit APIs such as WKWebView, or WebPage for SwiftUI, can add their own user setting to control GPC.
That last point shapes everything else. Apple is not switching GPC on for apps. It is giving apps a switch, and each app has to build the setting, show it to users and pass the user's choice to WebKit.
The two new properties
The WebKit post and Apple's developer documentation describe two properties that do the same job in two frameworks:
- WKWebpagePreferences.globalPrivacyControlEnabled, for apps built on WKWebView. Apple's documentation says the default value is NO.
- WebPage.NavigationPreferences.isGlobalPrivacyControlEnabled, for apps using the Swift WebPage API. Apple's documentation says the default value is false.
According to the WebKit post, setting globalPrivacyControlEnabled to YES on the preferences object handed back from the navigation-policy delegate opts that navigation into GPC, and it applies to the whole document tree produced by the navigation. Apple's documentation for both properties says that once enabled, both navigator.globalPrivacyControl and the Sec-GPC: 1 request header are active for the main frame, its subframes and their subresources.
The post includes sample code in Swift for WKWebView, Swift for WebPage and Objective-C. In each example the app sets the property from a value named userPrefersGlobalPrivacyControl inside its navigation-policy callback and then allows the navigation. In plain terms, the app checks the user's saved preference every time a page starts to load and tells WebKit whether to send the signal.
Platforms and defaults at a glance
The table below collects the facts stated in Apple's developer documentation and the WebKit post.
| Item | WKWebView API | SwiftUI WebPage API |
|---|---|---|
| Property name | WKWebpagePreferences.globalPrivacyControlEnabled | WebPage.NavigationPreferences.isGlobalPrivacyControlEnabled |
| Default value | NO | false |
| Platforms listed by Apple | iOS, iPadOS, Mac Catalyst, macOS, visionOS 27.0+ | iOS, iPadOS, Mac Catalyst, macOS, visionOS 27.0+ |
| Where it is set | Navigation-policy delegate, per navigation | decidePolicy callback, per navigation |
| What it turns on | Sec-GPC: 1 header and navigator.globalPrivacyControl for the main frame, subframes and subresources | Same |
tvOS and watchOS are not listed on either documentation page.
What GPC is, according to the sources Apple cites
The WebKit post quotes the W3C Global Privacy Control specification as of 10 November 2026. In that text, GPC is designed to let users express a preference to opt out of sharing and of cross-context targeted advertising. The W3C currently publishes the specification as a Working Draft, dated 24 September 2026.
The post also quotes the California Office of the Attorney General's webpage on the California Consumer Privacy Act, as of the same date. That page lists, among the rights the law gives California consumers, the right to opt out of the sale or sharing of their personal information, including via GPC. Apple does not add legal commentary of its own, and it does not mention any other law or country.
How the signal reaches a website
This section is analysis of how the mechanism works in practice, based on the behaviour Apple documents. A site can see GPC in two places:
- On the server, as an HTTP request header, Sec-GPC with the value 1. Because Apple says the header is sent for subresources as well, requests for scripts, images and tracking pixels loaded by the page carry it too. That includes requests to third-party analytics and ad endpoints the page loads.
- In the browser, through the JavaScript property navigator.globalPrivacyControl, which a tag manager rule or consent platform can read before deciding which tags to fire.
Sending the signal does not block anything by itself. GPC is a preference, not a filter. A site, its consent management platform or its vendors have to read the signal and change what they do. If nobody reads it, the page behaves exactly as before.
Who is and is not affected
This section is analysis. The new API is for apps that display web content using WebKit. That covers in-app browsers, apps that open links inside a web view, and hybrid apps whose screens are partly web pages. Traffic from those apps will only carry GPC if three things are true: the device runs version 27 of iOS, iPadOS, macOS or visionOS, the app's developer has added a GPC setting, and the user has switched it on. Apple's own post gives no figures on adoption, and it is too early for any.
The WebKit post does not mention Safari. It does not say whether Safari has, or will have, its own GPC setting, and it does not describe any system-wide switch. Anything you read elsewhere about a Safari setting should be checked against Apple's own release notes before you plan around it.
What this means for measurement and ads
This section is analysis, not something Apple said. For most advertisers the short-term effect is small, because adoption depends on individual app developers. The longer-term questions are about what your site does when the signal arrives.
Consent tools and tag managers
If your site uses a consent management platform, check whether it reads navigator.globalPrivacyControl or the Sec-GPC header, and what it does when the value is true. A platform may be able to map an opt-out signal to its own opt-out state. If yours does, sessions from GPC-enabled apps may be treated as opted out of ad personalisation or data sharing, depending on how it is configured.
Google consent mode and GA4
Google's consent mode works on the consent states your site sets, such as ad_user_data and ad_personalization. Apple's post does not mention Google, and the GPC signal does not change those states by itself. If your consent setup maps GPC to a denied state, the Google tag will behave as it does for any user who declined, and reports in Google Analytics 4 and conversion data sent to ad platforms will reflect that. The practical step is to test it: load your site with GPC on, look at which consent states are set, and check which tags fire.
Audiences and remarketing
If GPC-flagged sessions are excluded from sharing or targeted advertising, remarketing lists and conversion counts built from US traffic could shrink over time as more apps adopt the setting. How much depends on how many apps add it and how many users turn it on, neither of which is known today. It is worth watching list sizes and modelled conversions in your Google Ads account once GPC-enabled apps start shipping.
What to check in your own setup
These steps are a practical checklist, not instructions from Apple.
- Ask your developer or consent platform vendor whether your site reads GPC today, and how it maps the signal.
- Check server or CDN logs for requests carrying Sec-GPC: 1, so you can see whether any of your traffic already sends it.
- Confirm that your consent setup and tag manager rules behave the same for a GPC opt-out as for a user who rejected cookies in your banner, if that is the policy your legal team wants.
- If your business has its own iOS or macOS app with an in-app browser, decide with your legal team whether to add a GPC setting once you build against the version 27 SDK.
- Record the date you made any change, so later shifts in GA4 or ad platform data can be traced to it.
What Apple's post did not say
- It does not say whether Safari itself will send GPC.
- It does not say whether any Apple app will offer a GPC setting.
- It does not give a system-wide setting; the control is per app.
- It does not say how websites are required to respond. It quotes the W3C specification and the California Attorney General's CCPA page and leaves it there.
- It does not mention Google, consent mode, GA4 or any ad platform.
- It does not mention Thailand or any law outside California.
What this means for Thai marketers
Apple's post does not mention Thailand, and the only law it cites is California's CCPA. The signal is not limited by country, so Thai sites may also receive it from apps that enable it; whether they must act on it is a legal question the post does not address. Thai brands that advertise to US users, sell to California residents or run their own apps with in-app browsers have more reason to look at it. The practical work is the same as any consent change: know whether your site reads the signal, decide with legal advice what it should do when the signal is present, and check that your analytics and ad tags follow that decision. If you are not sure how your consent setup feeds GA4 and your ad accounts, an audit of the tagging is a sensible first step.
Frequently asked questions about Apple's GPC WebKit API
Is Global Privacy Control turned on by default in iOS 27 apps?
No. Apple's documentation says the default value is NO for WKWebpagePreferences.globalPrivacyControlEnabled and false for WebPage.NavigationPreferences.isGlobalPrivacyControlEnabled. Each app has to add its own setting and switch it on per navigation.
What does a website receive when an app enables GPC?
The website receives the Sec-GPC: 1 request header and can read navigator.globalPrivacyControl in JavaScript. Apple says both are active for the main frame, its subframes and their subresources.
Does this mean Safari now sends GPC?
Not stated. The WebKit post from 18 November 2026 covers the API for apps using WKWebView and WebPage. It does not mention Safari.
Will GPC stop GA4 or Google Ads tags from firing?
Not on its own. GPC is a signal, and tags change behaviour only if your site or consent platform reads it and sets consent states accordingly. Apple's post does not mention Google products.
Does Thailand's PDPA require sites to honour GPC?
The source does not say. Apple's post cites only California's CCPA page; for Thai legal obligations, ask your own legal adviser.
Next steps
Apple's change is small in code and slow in effect: a property that defaults to off, in apps that choose to use it. The useful work now is on your side of the request. Find out whether your site reads GPC, decide what it should do, and check that GA4 and your ad tags follow. Relevant Audience can review how your consent and tracking setup handles signals like this.







