The Privacy Brand and the Google Server
Apple spent years making privacy the organizing argument for why its products were worth more than competitors' alternatives. The rebuilt Siri makes that argument harder to maintain without significant qualification. When a user's most demanding requests travel to Google's infrastructure for processing , Apple's privacy claim becomes conditional — true for some tasks, routed elsewhere for others, with no published accounting of which is which.
The community reaction to this arrangement was not simply critical. It was structural. Observers did not argue that Apple was wrong to make the choice — they argued that the choice revealed a limit. One account framed it directly: Apple built its rebuilt Siri on Foundation Models co-developed with Google, and its most demanding requests process on Google's servers — a dependence on a rival for core intelligence that marks a significant shift for a company that marketed itself as the privacy alternative . That framing is the product's most consequential fact, and no amount of on-device processing for lighter tasks changes what it means when the demanding work leaves Apple's infrastructure entirely.
The EU Exclusion Has No Announced End Date
The indefinite delay for EU iPhone and iPad users is not a localization lag or a certification backlog — it is a signal that Apple and EU regulators have not reached terms under which the rebuilt Siri can operate in that jurisdiction. That distinction matters for anyone building on iOS in Europe. The feature set announced at WWDC is the feature set available in some markets, not across the platform.
Regulatory complications of this kind do not resolve on Apple's schedule. The EU's approach to AI and platform regulation has consistently run ahead of what US companies expect, and the open-ended language around Siri AI's European availability — 'delayed indefinitely' — is the honest admission that Apple does not yet have a path through. Developers and enterprises building AI-integrated products on iOS in the EU are now planning around an assistant that is, on paper, the platform's centerpiece and, in practice, absent from their market. That absence compounds with each month iOS 27 ships without an EU-compliant Siri AI version, because the feature gap between EU and non-EU users widens in real time.
Screen Awareness and the Audit Gap
The privacy concern that surfaced most concretely in community response was not about the Google routing — it was about what happens before the routing decision is made. Screen Awareness, which gives Siri AI the ability to read on-screen content, is the kind of feature that requires continuous data access to be genuinely useful, and Apple provided no clear documentation of when it activates versus when it waits for explicit invocation .
A user who raised this directly noted that chats, photos, and personal context are automatically pulled to provide personalized responses — and that the boundary between passive collection and active processing was not drawn at the launch event . For a feature that, in its most expansive form, could read anything visible on the display, the absence of a clear on/off accounting is not a technical omission. It is the gap between what Apple marketed and what Apple documented, and it lands hardest precisely because Apple's brand premium has always rested on the claim that its devices do not behave this way.
Google's Infrastructure Role Is Not Incidental
The SpaceX Colossus lease that Google executed in advance of iOS 27's rollout changes the framing of the Apple-Google arrangement from opportunistic to architectural. This is not Google filling a temporary capacity gap while Apple builds its own infrastructure. This is Google building the scaled compute layer that Apple's announced product requires to function at consumer scale — and it is a layer Apple does not own, cannot unilaterally redirect, and did not build.
The business logic runs in two directions simultaneously. Google gains a distribution channel for its Foundation Models that reaches every iPhone user running a supported version of iOS, without owning the device relationship. Apple gains the model capability and server infrastructure it would need years and significant capital to replicate. Both parties get what they could not easily obtain alone. But the asymmetry matters: Google's position improves regardless of whether Apple stays or leaves, because the model capability and compute infrastructure exist independently of the iOS contract. Apple's position deteriorates the longer it relies on Google, because switching costs compound with each iOS release that ships on this architecture.
The Vindication Story Requires Ignoring the Liabilities
Some accounts framed WWDC 2026 as proof that Apple's patience paid off — that while other labs raced, Apple delivered something coherent and considered . That reading requires setting aside the EU exclusion, the unresolved privacy documentation, and the fact that the intelligence behind the product belongs to a competitor. What Apple delivered is a well-designed interface over capabilities it does not own, available in some of its markets, with open questions about what it does with user data along the way.
The developers and enterprises evaluating iOS 27's AI capabilities will make the more consequential judgment. An assistant that cannot be deployed uniformly across a global user base, whose data handling Apple cannot fully account for, and whose core intelligence is licensed rather than owned, is a platform dependency — not a platform advantage. Apple's patience produced a product that requires Google to exist, and EU regulators have already decided that is not their problem to resolve.