Back in June 2026, Apple announced it would consolidate both Hide My Email and Sign in with Apple under a single new domain: private.icloud.com. Tidier. More organized. Also, a real problem for the feature people actually rely on — and the privacy stakes were higher than Apple’s tidy housekeeping framing let on.
Here’s why it mattered. Hide My Email’s entire defense mechanism rests on blending in. Your alias looks like a regular iCloud address. A website wanting to block privacy-relay addresses would have to block all of iCloud mail to do it — collateral damage too costly to justify for most services. Move those aliases to a recognizable privacy domain, and that calculus changes fast. Blocking private.icloud.com becomes trivial and consequence-free. It’s a bit like going undercover with your name embroidered on the hat.
Apple Listened – Partially
Your Hide My Email aliases survive intact — developers, though, have homework.
After “further consideration and reviewing community feedback,” per Apple’s developer announcement on August 24, 2026, the company reversed course on Hide My Email. Your aliases stay on icloud.com. No disruption, no new domain, no increased blocking risk.
Sign in with Apple is a different story. New addresses will shift from privaterelay.appleid.com to private.icloud.com later this year. Existing addresses keep forwarding without interruption — Apple confirmed that directly. Developers and email providers, however, need to update their systems to accept private.icloud.com alongside legacy relay domains, or some Sign in with Apple logins risk breaking.
Here’s what that means in plain terms:
- Hide My Email: unchanged. Existing and new aliases stay on icloud.com.
- Sign in with Apple: new addresses move to private.icloud.com later in 2026.
- Existing Sign in with Apple addresses forward without interruption.
- Developers must allowlist private.icloud.com — Apple’s guidance is clear, and this is an action item, not a suggestion.
The asymmetry is worth noting. The consumer-facing privacy tool keeps its camouflage. The developer-facing authentication feature gets a new domain and a to-do list that arrives whether anyone wanted it or not.
A Win, With an Asterisk
User pressure moved a tech giant — which almost never actually happens.
Think about every streaming cancellation petition that dissolved into absolutely nothing — thousands of signatures, zero results. This time, the noise worked. Apple cited community feedback as the reason for the reversal, and the outcome is the right one. That’s worth saying plainly, without crediting Apple for fixing a problem it created.
Your Hide My Email aliases work exactly as they did before the June announcement. Spam stays filtered. Your real inbox stays hidden. If you’re a developer, add private.icloud.com to your allowlist before the Sign in with Apple migration rolls out later this year.
The larger picture cuts both ways: Apple demonstrated it will course-correct under sufficient pressure, but the original plan reached the public announcement stage before pushback forced a rethink — which is a reminder that staying loud matters more than staying polite.
