Apple Says Safari Is Blocking Post-Cookie Ad Tracking. Publishers Still Want to Know Who Sets the Rules.
Who decides what Safari can reach?
That is the question behind Apple’s latest privacy dispute with the ad-tech industry. In an October 19 explanation, WebKit said Safari blocks network access to third-party systems that turn email addresses into identifiers for recognizing people across websites and devices. WebKit says the policy is meant to limit that kind of cross-site identity resolution. For users, it may mean fewer ways for ad systems to recognize them as they move between sites. It does not mean Safari is blocking all ads, all cookies, or every tool with the word “identity” in its sales pitch.
First-party is a different door
WebKit drew a line between cross-site identity resolution and a website using information about its own customers to personalize its service. In plain English: a bookstore remembering what you asked it to remember is different from a third-party system being used to recognize you on other websites. That distinction matters because privacy rules can limit cross-site tracking without treating every useful website feature as a crime against the cookie jar. It also leaves practical questions for publishers and ad companies: which systems fall on which side of the line, and how does a browser apply that boundary?
The blocklist has a visibility problem
Digiday reported on October 20 that publishers want more clarity about which services are blocked and how decisions can be challenged. The report also described an ad-server service that was initially caught in a block and later restored. That is one reported incident, not proof of a widespread pattern. Still, it illustrates why a privacy policy can also be a governance question. If a browser blocks a tool used by publishers, the affected parties need a way to understand what happened and what review, if any, is available. The packet does not establish a specific appeal process.
Privacy protection and platform power
Digiday also reported scrutiny of Apple’s advertising business alongside publisher concerns about Safari’s restrictions. That is a reason to ask questions, not evidence that Apple set the policy to benefit its own ads. The distinction matters: users deserve meaningful protection from cross-site tracking, while publishers have a legitimate interest in understanding rules that can affect the tools they use. Nobody needs to choose between privacy and accountability, unless the platform’s preferred menu has only one button and it says “Agree.”
The practical takeaway
WebKit’s stated target is third-party identity resolution, not every ad or every form of website personalization. The policy may limit some ways of recognizing people across sites, while decisions about which systems Safari can reach may also affect publisher tools. Apple’s policy should be judged on what it says it does and how clearly its boundaries are explained—not on an unproven theory about motive. Privacy is not a favor from a company, and transparency should not be an optional add-on sold separately from the browser.