On November 3, Apple published a support document clarifying how iCloud Advanced Data Protection interacts with public link sharing. The core finding is both significant and easy to miss: if you share an iCloud file or photo using the “Anyone with the Link” option, end-to-end encryption is disabled for that item — even if you have Advanced Data Protection turned on.
For users who have enabled ADP specifically to prevent Apple from accessing their data, this represents a meaningful exception to the protection they believe they have.
What Advanced Data Protection Is Supposed to Do
Advanced Data Protection, available to users in most countries, is iCloud’s strongest privacy setting. When enabled, the encryption keys for the majority of your iCloud data — including your entire iCloud Photos library and iCloud Drive files — are stored only on your enrolled devices. Apple cannot access them.
This means that if Apple receives a government subpoena for your iCloud Photos, it cannot comply — not because it refuses, but because it technically cannot access the data. The same applies to data breaches at Apple’s level: if someone gains access to Apple’s servers, they cannot decrypt ADP-protected content without your device-side keys.
ADP is the feature that meaningfully distinguishes “Apple holds the keys and can be compelled” from “Apple cannot access this even under legal pressure.” For users with serious privacy needs — journalists, activists, domestic abuse survivors, or anyone storing sensitive personal photos — it is the setting that matters most.
What Public Link Sharing Changes
The November support document states the limitation directly: sharing an item with “Anyone with the Link” disables end-to-end encryption for that item, even when ADP is enabled.
The technical reason is straightforward. End-to-end encryption works by ensuring only specific, enrolled devices hold the decryption keys. A public link, by definition, can be opened by anyone with a compatible device — which means the encryption cannot be tied to a specific set of key holders. For the link to work, the data must be accessible without a device-specific key.
Apple’s implementation handles this by moving the item from the E2E-encrypted tier to the standard iCloud encrypted tier — where Apple holds the key — when a public link is created. The item is now accessible to Apple and to anyone who possesses the link.
Why This Is Easy to Miss
The disconnect is in how most users understand privacy settings. Advanced Data Protection is presented as an account-level setting: you turn it on, and your iCloud data is end-to-end encrypted. That framing encourages users to think of protection as a persistent state rather than something that can be selectively suspended.
Sharing via “Anyone with the Link” is a common action — used for sharing a family photo album, sending a document to someone who doesn’t have an Apple ID, or quickly passing a file to someone. Users are not typically thinking about encryption key custody when they tap the share button.
The result is a gap between expectation and reality. A user who has enabled ADP to protect their family photos from unauthorized access may share a folder of those photos publicly — removing ADP’s protection for those specific files — without realizing the connection.
What “Anyone with the Link” Actually Means for Privacy
There are two separate privacy risks when you create a public link in iCloud:
Encryption risk: As described above, the linked content moves out of ADP protection. Apple can now access it, and can be compelled to produce it.
Access control risk: Anyone with the link can access the content. Links can be forwarded, indexed by web crawlers, or exposed through browser history. The intended recipient is not the only possible viewer.
Apple’s November policy change adds a third element: the company will now scan content shared via “Anyone with the Link” for harmful content. This scanning applies to iCloud Photos items and iCloud Drive files. It is consistent with Apple’s existing approach to scanning for specific categories of illegal content in other contexts.
The scanning applies only to publicly shared content — not to content stored privately with ADP enabled. But because creating a public link disables ADP for that item, the population of items Apple can now scan includes anything a user has chosen to share publicly.
Who This Affects Most
Users who have enabled Advanced Data Protection for strong privacy guarantees are most affected by this clarification, because their expectation of protection is highest.
Standard iCloud users — those without ADP — are less directly impacted by this specific policy, because Apple already holds the keys to their data. The encryption change from creating a public link does not represent a meaningful shift for users who were already in the standard encryption model.
For ADP users, the practical question is: do you use public link sharing? If yes, do you understand that those specific items are no longer end-to-end encrypted while the link is active?
What You Can Do
Avoid public link sharing for sensitive files. If you use ADP for privacy protection, sharing via “Anyone with the Link” directly contradicts what you are trying to protect. Use person-specific sharing instead — sending directly to someone’s Apple ID or email preserves ADP’s protection.
Check whether you have active public links. In iCloud Drive on the web, you can review shared items and see which use public links versus person-specific sharing. Remove public links for any items whose encryption you care about.
Understand what ADP covers, item by item. ADP is not a uniform state across all iCloud data. Some categories — Mail, Contacts, Calendar — are not covered by ADP regardless. Publicly shared files are now explicitly excluded from ADP protection while they remain shared publicly.
Treat public links like public posts. From a privacy standpoint, an item shared publicly via iCloud is accessible to Apple, accessible to anyone with the link, and now subject to content scanning. Apply the same judgment you would to a post on a public social media feed.
The Transparency Question
Apple’s November support document is a clarification rather than an announcement of a new policy. The behavior it describes — public links disabling E2E encryption — may have been present before the document was published. The document makes the limitation explicit in a way it was not previously.
Whether users who enabled ADP understood this limitation before is an open question. The standard presentation of ADP focuses on what it protects, not on the conditions that suspend it.
This kind of documentation update — clarifying a behavior that was technically present but not clearly communicated — reflects a broader challenge in privacy engineering. Strong security guarantees need equally clear explanations of their limits. A setting that provides protection in most cases but not in a common use case creates a false sense of security in exactly the situations where the limitation applies.
For iCloud users with ADP enabled, the November document is worth reading. It describes your protection accurately. The question is whether the protection you have is the protection you thought you had — and whether you need to change how you share.
daftei is designed for storing personal files and memories privately. File sharing does not use anonymous public links. When files need to stay private, they stay stored with encryption rather than being moved to a publicly accessible tier. Files are encrypted with TLS 1.3 in transit and AES-256 at rest — server-side encryption, not end-to-end. That is worth stating clearly: daftei holds the encryption keys, which is the standard model for cloud storage services, and means legal requests can be complied with. The service does not sell data, does not train AI on content, and is GDPR and CCPA compliant.