If your team shares files through public iCloud links, the privacy and compliance assumptions behind that habit change with iOS 27.3. Items shared with “Anyone with the Link” become accessible to Apple for content checks and are no longer end-to-end encrypted. A convenient sharing shortcut now becomes a decision your security and legal staff may want to review before the update arrives in December.
What happened
The Verge, following a report from 9to5Mac, says Apple will check iCloud items that anyone with a link can open for “harmful content”. The change starts with version 27.3 of iOS, iPadOS, macOS and visionOS. Apple’s support document states that content shared this way is made accessible to Apple to check for harmful content.
The Verge also reports that sharing with Anyone with the Link permissions means the item is no longer end-to-end encrypted. The support document does not define harmful content. The Verge connects the move to protesters who have urged Apple to tackle child sexual abuse material stored in iCloud.
Apple says it reserves the right to move, refuse, modify, remove or delete harmful content that a user tries to upload. It may also block or disable accounts, prevent a person from opening a new account and, “if necessary”, involve law enforcement. The Verge says the first 27.3 developer betas launched the day before its report, and that Apple has said it plans to ship iOS 27.3 in December.
Why it matters
Apple has long presented privacy as a product feature, and end-to-end encryption is central to that pitch. The sources describe a specific change for items shared through open links, which lose that protection and become accessible to Apple for checks. They say nothing about how other iCloud storage or sharing methods are handled, so readers should not assume either way and should look to Apple’s own documentation.
The undefined term “harmful content” is the main uncertainty. Without a definition, organisations cannot easily judge what could trigger removal or an account action. The enforcement language is broad, and account-level penalties matter more to a business than to a casual user, since one flagged link could affect an account that holds other work.
As analysis, this suggests the trust model may depend increasingly on how a file is shared and not only on where it is stored. Whether other vendors take a similar path is unknown, but buyers can reasonably compare each vendor’s stated scanning scope for public links.
What it means for you
Start with an inventory. Find out whether staff use iCloud public links for client files, design assets, contracts or internal documents. Once devices run 27.3 or later, newly shared open links will be accessible to Apple for checks. Compare that with your confidentiality agreements and data-handling policies.
- Review your acceptable-use and sharing policy. Decide whether open iCloud links stay allowed for anything sensitive.
- Move regulated or client-confidential material to a managed sharing tool with access controls and audit logs.
- Ask your legal or privacy lead whether privacy notices or customer contracts promise end-to-end protection that open links no longer meet.
- Tell staff that account blocks are possible, and keep work data backed up outside a single personal Apple account.
If you manage Apple devices, test the 27.3 betas to see how sharing prompts and warnings appear to users. If you build products that hand users iCloud links, review that flow. Our gadgets coverage will track follow-up changes.
What to watch
- Whether Apple publishes a definition of “harmful content” before or after the December release.
- Changes in the beta builds, including any warnings shown when a user creates an open link.
- Reports of removed files or disabled accounts after release, especially for business users.
- Whether rival cloud storage vendors change their own public-link policies in response.
