Starting with iOS 14.5, Apple will proxy the Safe Browsing service in Safari through its own servers instead of Google's to protect user data
Starting with iOS and iPadOS 14.5, Apple will proxy Google's “Safe Browsing” service used in Safari through its own servers instead of relying …
Context & Ripple Effects
Safari had already broadened its malicious-site-warning sources beyond Google with a possible Tencent Safe Browsing integration, while Apple separately made Safari block third-party cookies by default. Routing Google Safe Browsing requests through Apple adds a network-level privacy control to that browser strategy.
The move preserves Google’s Safe Browsing role but changes the path through which Safari users reach it, placing Apple between Safari and a Google-operated safety service.
First-order effects
- Safari requests to Google Safe Browsing in iOS and iPadOS 14.5 will be proxied by Apple, so Google no longer receives those requests directly from Safari users.
- Apple takes on the operational role of relaying a security service that Safari continues to use, making Apple responsible for the new privacy boundary.
Second-order effects
- Google’s security-data relationship with Safari becomes more mediated by Apple, even as Google remains the underlying Safe Browsing provider.
- The change reinforces Apple’s ability to differentiate Safari through privacy safeguards that sit around third-party web services, alongside its earlier cookie blocking.
Third-order effects
- If Apple applies the same intermediary model more broadly, browser privacy competition shifts from simply limiting trackers to controlling how external services receive user request data.
- Browser vendors may increasingly have to balance security features that benefit from URL-level signals against architectures designed to minimize direct user-data exposure.
The trend: Browser privacy is moving toward proxying and limiting data flows to third-party services, not only blocking traditional tracking mechanisms.