Skip to content
Skimwire
Live wire
Security 2 min skim

Apple will check public iCloud links for harmful content starting with iOS 27.3

Files and photos shared with 'Anyone with the link' aren't end-to-end encrypted and will be checked. Here's what to do instead.

AI illustration of a smartphone on a wooden desk with a glowing chain link and open padlock floating above it, beaming light at floating photo and document thumbnails
Illustration: Skimwire (AI-generated)

The skim

  • Starting with iOS 27.3, iPadOS 27.3, macOS 27.3 and visionOS 27.3, Apple will check iCloud Drive files and iCloud Photos shared with "Anyone with the link" for harmful content.
  • Those public links are not end-to-end encrypted, even with Advanced Data Protection turned on. Items shared only with "People you choose," or sent as a copy, aren't part of the check, according to MacRumors.
  • Apple doesn't define "harmful content." If it finds some, it says it can remove the file, disable your Apple Account or, "if necessary," involve law enforcement.

What happened

Apple published a new support document on Nov. 3, "Learn more about sharing content that can be accessed by Anyone with the Link," that spells out a policy change coming with its next point releases. The key line: "Starting in version 27.3 or later of iOS, iPadOS, macOS, and visionOS, items shared using Anyone with the Link will be checked by Apple for harmful content."

The same document says items shared this way are "no longer end-to-end encrypted, even if the owner or participants have turned on Advanced Data Protection." It also lists what Apple can do if it finds a problem: "Apple reserves the right to move, refuse, modify, remove, or delete the content at any time. Apple may also take action against your Apple Account, including blocking or disabling your Apple Account, blocking the ability to create a new Apple Account with the associated email address or phone number, or if necessary, involving law enforcement."

MacRumors and 9to5Mac both reported the change. MacRumors notes that only the "Anyone with the link" option is evaluated. Files shared with "People you choose" or sent with "Send a Copy" are not. The 27.3 updates are in developer beta now, and MacRumors expects them to reach the public in December.

Why it matters

This is Apple drawing a clear line between private sharing and public links. A public iCloud link works for anyone who has the URL, so it behaves more like a file posted on the web than a private message. Apple is now treating it that way.

It's also a notable shift for a company that dropped its plan to scan iCloud Photos for child sexual abuse material after privacy pushback. This new check is narrower. It covers only content you choose to make public by link, not your whole library.

Two things are still unclear. Apple doesn't say what counts as "harmful content." It also doesn't say whether links created before 27.3 will be checked once you update, a gap MacRumors also flagged. Apple notes that "not all features are available in all countries or regions."

What you should do

  • Use "People you choose" for anything personal. Tax documents, medical files and family photos don't need a public link. Our step-by-step guide shows how: How to share iCloud Drive files with only the people you choose on iPhone.
  • Review links you've already shared. In the Files app, open the Shared view, then touch and hold an item and choose Manage Shared File or Manage Shared Folder to see who has access. Stop sharing anything that no longer needs a public link.
  • Keep your own backup. Apple says it can move or delete flagged content, so don't let a shared link be the only copy of an important file.

The 27.3 updates aren't out for most people yet, so there's no setting to change today. Now is a good time to clean up old public links.

Sources: Apple Support, MacRumors, 9to5Mac, The Verge.

Newsletter

Get the day's tech, skimmed.

Two emails a day, morning and afternoon, with each edition's verified tech stories. Free, unsubscribe anytime.

Check your inbox to confirm.

Something went wrong. Try again.