Apple's WebKit team on November 18, 2026 documented a programming interface that lets apps which display web pages send the Global Privacy Control signal, a browser-level request asking websites not to sell or share a person's data or use it for cross-context targeted advertising. The interface, available in iOS, iPadOS, visionOS and macOS 27, is off unless an app turns it on, and once it is on it covers every frame and every request a page makes.
In Short
Apple has given app developers a way to make the web pages inside their apps send the Global Privacy Control signal, a request not to sell or share personal data that is defined in a draft web standard. It matters because California and other US states treat that signal as a legal opt-out, so any app that switches it on changes what advertisers and ad tech firms may do with data from those page views. Nothing changes by default: each app must add its own setting, and only navigations where the app enables the signal carry it.
What Apple published
The post, titled "Global Privacy Control (GPC) WebKit API" and signed by John Wilander, is short. "As of iOS, iPadOS, visionOS, and macOS 27, there is now a WebKit API to enable Global Privacy Control (GPC), an emerging web standard," it begins. It is addressed to developers rather than to people who browse: "As a developer using WebKit APIs like WKWebView, or WebPage for SwiftUI, you can add your own user setting to control it."
That distinction is the heart of the announcement. WKWebView is the class iPhone, iPad, Mac and Vision Pro apps use to show web content inside their own interface, and WebPage is its newer Swift counterpart for SwiftUI. The post gives apps built on either a documented switch for Global Privacy Control, in two forms.
For WKWebView, there is a new property on WKWebpagePreferences called globalPrivacyControlEnabled. According to the post, "Setting it to YES on the preferences object handed back from the navigation-policy delegate opts that navigation into GPC. This applies to the whole document tree produced by the navigation." The next sentence sets out how far that reaches: "Once enabled, both navigator.globalPrivacyControl and the Sec-GPC: 1 request header are active for the main frame, its subframes, and their subresources."
For SwiftUI, the same capability sits on a different type. "The Swift WebPage API exposes the same capability through a WebPage.NavigationPreferences property, isGlobalPrivacyControlEnabled," according to the post.
Two things stand out in the framing. The post quotes two outside documents rather than describing the policy goal in Apple's own words: the W3C specification "as of November 10, 2026," and the California Attorney General's page on the California Consumer Privacy Act as of the same date. And it says nothing about Safari, the browser Apple ships on the same devices.
The documentation entries
Apple's developer documentation describes both properties in identical terms. Each is "Whether the Global Privacy Control (GPC) signal is enabled for the navigation." For WKWebpagePreferences, the documentation says "The default value is NO." For WebPage.NavigationPreferences, it says "The default value of this property is false." Both pages repeat the scope in the post: when enabled, the JavaScript property and the request header "are active for the main frame, its subframes, and their subresources."
Both entries list the same five platforms, each from version 27.0: iOS, iPadOS, Mac Catalyst, macOS and visionOS. Mac Catalyst, the route by which iPad apps run on the Mac, appears in the documentation but not in the post. tvOS and watchOS appear in neither.
The new properties sit in the same lists as existing per-navigation settings such as isLockdownModeEnabled, preferredHTTPSNavigationPolicy and allowsContentJavaScript. Apple has, in other words, filed the privacy signal next to Lockdown Mode, among the preferences an app can hand back as a page loads.
| Item | WKWebView API | WebPage API (Swift) |
|---|---|---|
| Type | WKWebpagePreferences | WebPage.NavigationPreferences |
| Property | globalPrivacyControlEnabled | isGlobalPrivacyControlEnabled |
| Declaration | var globalPrivacyControlEnabled: Bool { get set } | var isGlobalPrivacyControlEnabled: Bool |
| Default | NO | false |
| Set in | webView(_:decidePolicyFor:preferences:) navigation-policy delegate | decidePolicy(for:preferences:) |
| Platforms | iOS 27.0+, iPadOS 27.0+, Mac Catalyst 27.0+, macOS 27.0+, visionOS 27.0+ | iOS 27.0+, iPadOS 27.0+, Mac Catalyst 27.0+, macOS 27.0+, visionOS 27.0+ |
| Reach once enabled | Main frame, subframes and their subresources | Main frame, subframes and their subresources |
| What sites see | Sec-GPC: 1 header and navigator.globalPrivacyControl | Sec-GPC: 1 header and navigator.globalPrivacyControl |
How the switch works, according to the documentation
The post includes code samples in Swift for WKWebView, Swift for WebPage and Objective-C. Read together with the two documentation pages, they describe the following sequence.
- The app keeps its own user setting. The post refers to it in the samples as userPrefersGlobalPrivacyControl. The documentation describes no system-wide toggle that apps inherit; the post says developers "can add your own user setting to control it."
- A navigation begins. WebKit calls the app's navigation-policy delegate. For WKWebView, that is the webView(_:decidePolicyFor:preferences:) method, which receives a WKNavigationAction and a WKWebpagePreferences object. For WebPage, it is decidePolicy(for:preferences:), which receives a WebPage.NavigationAction and an inout WebPage.NavigationPreferences value.
- The app sets the property. In the WKWebView sample, the line is preferences.globalPrivacyControlEnabled = userPrefersGlobalPrivacyControl. In the WebPage sample, it is preferences.isGlobalPrivacyControlEnabled = userPrefersGlobalPrivacyControl.
- The app allows the navigation. The Swift WKWebView sample returns (.allow, preferences), the WebPage sample returns .allow, and the Objective-C sample calls decisionHandler(WKNavigationActionPolicyAllow, preferences).
- WebKit applies the signal to the whole page. For that navigation, the main frame, every subframe and every subresource carry the Sec-GPC: 1 header, and scripts reading navigator.globalPrivacyControl see it enabled.
- Without step 3, nothing is sent. The default is NO in Objective-C terms and false in Swift.
Because the value is attached to each navigation, an app could in principle enable the signal for some pages and not others. The post does not discuss that case.
What the signal itself says
GPC is defined by a W3C document. The Working Draft dated 24 September 2026 was published by the W3C Privacy Working Group on the Recommendation track. Its editors are Sebastian Zimmeck of Wesleyan University, Peter Snyder of Brave Software, Justin Brookman of Consumer Reports and Aram Zucker-Scharff of The Washington Post. Robin Berjon, Ashkan Soltani and David Harbage of DuckDuckGo are listed as former editors. The draft carries the usual caveat: "Publication as a Working Draft does not imply endorsement by W3C and its Members."
Its abstract is precise about the purpose: "This document defines a signal, transmitted over HTTP and through the DOM, that conveys a person's request to websites and services to not sell or share their personal information with third parties." The introduction explains why a single opt-out signal was thought necessary. "Requiring that people manually express their rights for each and every site they visit is, however, impractical, and an imposition of 'privacy labor' on people," it states.
The sentence Apple chose to quote comes from the same introduction: "Global Privacy Control is designed to allow users to express a preference to opt out of sharing and cross-context targeted advertising." The draft continues directly with the limits. "GPC is not designed to exercise deletion rights, for example. GPC is also not designed to address data collection or ad targeting within the same context." A publisher showing ads to a reader on its own site based on that reader's activity on the same site is, in the draft's words, outside what the signal is meant to stop.
The mechanics are strict. "A user agent MUST generate a Sec-GPC header field with a field-value that is exactly the numeric character '1'" when the preference is on, and must not send the header at all when it is off. A server that receives any other value "MUST ignore it." HTTP intermediaries "MUST NOT remove a Sec-GPC header set to '1'." The same value is exposed to scripts as navigator.globalPrivacyControl, in both page and worker contexts. The draft's own example of a script check is drily blunt; the code comment reads "// wonderful, we can sell this person's data!" for the case where the property is false.
There is also a rule on timing that maps closely onto Apple's design. "The preference MUST be cached on each top-level navigation," the draft states, and "if the preference changes during or after a top-level navigation, it will not be reflected until the next navigation." Apple's interface is set in the navigation-policy delegate, which runs as each navigation begins.
| Element | What the W3C Working Draft of 24 September 2026 specifies |
|---|---|
| HTTP header | Sec-GPC, with a value of exactly "1"; not sent when the preference is off; no more than one per request |
| JavaScript | navigator.globalPrivacyControl, available in regular and worker contexts |
| Caching | Preference fixed at each top-level navigation; changes apply from the next navigation |
| Site declaration | Optional /.well-known/gpc.json resource with a gpc member (true or false) and a lastUpdate date |
| Test automation | WebDriver commands at /session/{session id}/privacy (POST to set, GET to read) |
| Out of scope | Deletion rights; data collection or ad targeting within the same context |
| Privacy cost | One extra bit that "might increase the information available for browser or device fingerprinting" |
The draft acknowledges that it relies on concepts developed for Do Not Track, the earlier header that websites were never obliged to obey. The difference sits in the last sentence of the abstract: the standard "is intended to work with existing and upcoming legal frameworks that render such requests enforceable."
The California connection
That is why the post quotes California. The Attorney General's CCPA page, last updated on August 28, 2026, lists the rights the law "secures" for California consumers. Among them: "The right to opt-out of the sale or sharing of their personal information including via the GPC."
The page's frequently asked questions spell out the mechanism in more detail. Under the right to opt out of sale or sharing, it says: "You may request that businesses stop selling or sharing your personal information ('opt-out'), including via a user-enabled global privacy control. Businesses cannot sell or share your personal information after they receive your opt-out request unless you later authorize them to do so again."
The words "user-enabled" fit Apple's design. The post tells developers to add their own user setting, and both properties default to off. The W3C draft describes the wider legal pattern: "Many US states say that a user agent may not send a universal opt-out signal by 'default,' though at least one state has said that selecting a privacy focused user agent is a sufficient indicator of user intent." It also records that "At least four states have specifically identified GPC as a valid means to exercise legal opt-out rights."
For advertisers, the definition of sharing is the operative part. According to the Attorney General's page, "sharing refers specifically to sharing for cross-context behavioral advertising, which is the targeting of advertising to a consumer based on the consumer's personal information obtained from the consumer's online activity across numerous websites." The page adds that "Businesses must wait at least 12 months before asking you to opt back in to the sale or sharing of your personal information."
The California Privacy Rights Act, approved by voters as Proposition 24 in November 2020, amended the CCPA, with new protections starting on January 1, 2023. The Attorney General's office notes that it "typically refers to the law as 'CCPA' or 'CCPA, as amended.'"
A further California deadline sits 44 days after Apple's post, by PPC Land's count. California's amendments include AB 566, under which browsers may not be developed or maintained without opt-out preference signal functionality that is easy for a reasonable person to locate and configure, from January 1, 2027. Apple's post does not mention that law, and the documents do not say whether an app's embedded web view counts as a browser for its purposes.
Safari and the apps
Apple's own browser is moving on a parallel track, according to reports from the week before the post. 9to5Mac reported on November 11, 2026 that the iOS 27.3 beta adds a Safari setting named Use Global Privacy Control, under Settings, Apps, Safari, Advanced. iThinkDifferent reported the same day that the setting is off by default and that iOS 27.3 is expected in December. 9to5Mac reported that Apple's support document for the setting had not yet been published. WebKit's public bug tracker shows a report titled "Add off-by-default support for Global Privacy Control" filed on May 1, 2026.
Why does the app interface matter as much as the Safari toggle? Plenty of web pages on Apple devices are never opened in Safari. Apps that show links inside their own screens, from social feeds to email clients, can do it with WebKit's embedded views, and Apple's documentation sets the GPC default in those views to off, with no mention of the Safari setting. WebKit privacy features have reached apps through the engine before. Intelligent Tracking Prevention became active by default in all browsers on iOS 14 in 2020, because they had to use WKWebView, which had it switched on. GPC takes the opposite route: each app decides.
The post also fits a pattern in WebKit's privacy work this year. Wilander was one of three signatories on WebKit's October 19, 2026 post explaining that Safari and WebKit on version 27 block network access to identity resolution infrastructure. After iOS 27's release on September 14, 2026, The Trade Desk could no longer serve ads to affected Safari users. Those measures block. GPC asks.
Why this matters for marketers
A blocked request never reaches a server. A GPC request does, and it arrives with a legal meaning attached in some states. The question for advertisers, publishers and ad tech vendors is therefore not whether their tags load inside apps that adopt the interface, but what those tags do when Sec-GPC: 1 arrives with every call.
Google already answers that question for its own products. It said in June 2025 that GPC signals would trigger restricted data processing in eight more US states, and on November 17, 2026 it began receiving GPC signals directly for ad requests from Louisiana and Vermont. The same week, its state privacy messaging tools reached 24 states. Traffic from apps that switch the signal on would fall into that handling like any other GPC request.
Enforcement has focused on companies that receive the signal and ignore it. California's privacy agency announced a $1.55 million fine against Hertz on November 17, 2026 over sites that failed to detect and honor opt-out preference signals. The Attorney General's $1.55 million settlement with Healthline in July 2025 involved data still flowing to advertisers despite Global Privacy Control signals, and Disney agreed to pay $2.75 million in February 2026 over opt-outs that did not follow users across services and devices. In April 2026, a webXray audit found that 55% of 7,634 sites set advertising cookies despite the signal, a finding Google, Meta and Microsoft disputed.
The scope of Apple's interface adds a practical detail. Because the header reaches "subframes, and their subresources," it is not only the page's owner that receives it. Third-party scripts, pixels and ad iframes on the page get it too. The W3C draft notes the processing cost of that design: "a GPC signal will be attached to every HTTP request made to a given site," and rendering a page "often requires making dozens such requests." It warns that it "can prove impractical for GPC signals to trigger full-blown opt-out procedures with costly audit trails for every single GPC interaction," and encourages regulators to consider processing a signal maintained by the user agent as if the person had already set a standing preference.
Outside the US, the picture is less settled. The draft says GPC "could potentially be used to indicate rights in other jurisdictions as well," pointing to Articles 7 and 21 of the GDPR, but describes this as something a regulator "could determine." A peer-reviewed study PPC Land covered in May found that GPC could cut EU consent banners only partially, and only if regulators clarify how it maps to GDPR.
There is a cost on the privacy side, too. According to the draft, exposing the preference "potentially divides users into two groups in a way that might increase the information available for browser or device fingerprinting." The draft calls this a privacy cost "intended to be justified by the privacy benefit of sending the signal."
What the documents do not say
The post does not say when the properties first shipped; the documentation lists version 27.0, while iOS 27 was released 65 days before the post, by PPC Land's count. It does not say whether Apple's own apps will enable the signal, whether App Store review will ask about it, or whether developers should offer it only in certain regions. It does not mention Safari's setting, AB 566, or any state other than California, and it does not say whether a user's Safari choice will ever carry over into apps.
Key facts
- Source document: "Global Privacy Control (GPC) WebKit API," WebKit blog, November 18, 2026, by John Wilander
- WKWebView property: WKWebpagePreferences.globalPrivacyControlEnabled, declared as var globalPrivacyControlEnabled: Bool { get set }, default NO (Apple documentation)
- SwiftUI property: WebPage.NavigationPreferences.isGlobalPrivacyControlEnabled, declared as var isGlobalPrivacyControlEnabled: Bool, default false (Apple documentation)
- Platforms (documentation): iOS 27.0+, iPadOS 27.0+, Mac Catalyst 27.0+, macOS 27.0+, visionOS 27.0+
- Platforms (post): iOS, iPadOS, visionOS and macOS 27
- Signals sent when enabled: Sec-GPC: 1 request header and navigator.globalPrivacyControl, for the main frame, its subframes and their subresources
- Specification: Global Privacy Control (GPC), W3C Working Draft, 24 September 2026, W3C Privacy Working Group (w3.org); the WebKit post cites the specification as of November 10, 2026
- Legal reference: California Consumer Privacy Act page, State of California Department of Justice, Office of the Attorney General, updated August 28, 2026 (oag.ca.gov)
- Related Safari setting (reported): Use Global Privacy Control, Settings, Apps, Safari, Advanced, iOS 27.3 beta, per 9to5Mac and iThinkDifferent, November 11, 2026
- California browser requirement: AB 566, from January 1, 2027, per PPC Land's December 2025 coverage
Timeline
- 2018 - California enacts the California Consumer Privacy Act
- September 2020 - WebKit's Intelligent Tracking Prevention is active by default in all iOS 14 browsers
- November 2020 - California voters approve Proposition 24, the CPRA, amending the CCPA
- January 1, 2023 - CPRA amendments begin to apply
- June 2025 - Google says GPC will trigger restricted data processing in eight more US states
- July 2025 - California's Attorney General settles with Healthline for $1.55 million
- December 2025 - PPC Land reports California's amendments, including AB 566's 2027 browser requirement
- February 2026 - Disney agrees to pay $2.75 million over streaming opt-out failures
- April 2026 - webXray audit finds 55% of 7,634 sites set ad cookies despite GPC
- May 1, 2026 - WebKit bug "Add off-by-default support for Global Privacy Control" is filed
- May 2026 - Study finds GPC could only partially reduce EU consent banners
- August 28, 2026 - California Attorney General's CCPA page last updated
- September 14, 2026 - iOS 27 released; The Trade Desk can no longer serve ads to affected Safari users
- September 24, 2026 - W3C publishes the GPC Working Draft
- October 19, 2026 - WebKit explains Safari 27's block on identity resolution infrastructure
- November 10, 2026 - Date the WebKit post uses for its quotes from the specification and the Attorney General's page
- November 11, 2026 - 9to5Mac and iThinkDifferent report a Use Global Privacy Control setting in the Safari iOS 27.3 beta
- November 17, 2026 - Google begins receiving GPC directly for Louisiana and Vermont ad requests; its privacy tools reach 24 states; CalPrivacy fines Hertz $1.55 million over opt-out signals
- November 18, 2026 - WebKit publishes the Global Privacy Control (GPC) WebKit API post
- December 2026 - iOS 27.3 expected, according to iThinkDifferent
- January 1, 2027 - AB 566 browser opt-out signal requirement applies
Related PPC Land coverage
- California fines Hertz $1.55m over unprocessed browser opt-out signals - CalPrivacy's order over sites that failed to detect and honor opt-out preference signals.
- Google to honor browser opt-out signals in Louisiana and Vermont from Nov 17 - Google starts receiving GPC directly for two more states and switching those ad requests to restricted data processing.
- Google adds Oklahoma and Alabama to its ad privacy tools, now 24 states - The state list behind Google's privacy messaging and GPC handling.
- California privacy law updates take effect January 1, 2026 - The CCPA amendments, including AB 566's browser opt-out signal requirement from 2027.
- Audit finds Google, Meta and Microsoft set ad cookies after users opt out - webXray's test of GPC compliance across 7,634 websites.
- Healthline settles largest CCPA violation case for $1.55 million - Data kept flowing to advertisers despite Global Privacy Control signals.
- Disney faces $2.75 million fine for broken streaming privacy controls - Opt-outs that applied only to one service or one device.
- GPC could cut EU consent banners - but law must catch up first - A peer-reviewed study on GPC under EU law.
- Safari 27 blocks identity firms that turn email addresses into tracking IDs - WebKit's October explanation of a network-level block co-signed by Wilander.
- Apple's iOS 27 blocks The Trade Desk from serving ads on Safari - What changed for ad delivery after iOS 27's release.
- Apple introduces the Intelligent Tracking Prevention (ITP) on all browsers in iOS14 - How a WebKit privacy feature reached every iOS browser in 2020.
Summary
Who: Apple's WebKit team, in a post by John Wilander, for developers of apps built on WKWebView or WebPage for SwiftUI; the change affects websites, advertisers and ad tech vendors whose pages and tags load inside those apps.
What: Two new properties, WKWebpagePreferences.globalPrivacyControlEnabled and WebPage.NavigationPreferences.isGlobalPrivacyControlEnabled, that let an app send the Global Privacy Control signal, the Sec-GPC: 1 header plus navigator.globalPrivacyControl, for the main frame, subframes and subresources of a navigation. Both are off by default.
When: The WebKit post is dated November 18, 2026. Apple's documentation lists availability from version 27.0 of each platform.
Where: iOS, iPadOS, macOS and visionOS 27 according to the post, plus Mac Catalyst according to Apple's documentation. The legal effect cited by the post is in California.
Why: GPC is a W3C-drafted signal meant to let people opt out of the sale or sharing of their data and of cross-context targeted advertising, and California's Attorney General lists opting out "via the GPC" among the rights the CCPA secures. The post gives apps that display web content a documented WebKit control to send it.
Discussion