Sign in with Apple and Hide My Email Move to private.icloud.com
What You Need to Know
- Apple consolidating Sign in with Apple and Hide My Email under private.icloud.com domain this summer.
- Existing forwarding addresses on legacy domains remain functional with uninterrupted mail forwarding.
- Developers must update systems to accept private.icloud.com in domain validation and allowlists.
- Sign in with Apple and Hide My Email use identical forwarding address technology.
Apple is planning to consolidate two of its privacy-focused email features under a single domain, private.icloud.com, later this summer. Right now, Sign in with Apple generates forwarding addresses on privaterelay.appleid.com, while iCloud+ Hide My Email uses icloud.com. Both will move to the new shared domain, though existing addresses on the legacy domains will keep working and mail will continue forwarding without interruption.
The change is largely invisible to regular users. Anyone already relying on either feature keeps their existing address and sees no disruption. The consolidation is more of a backend housekeeping move than a feature change, which makes it easy to miss how much infrastructure Apple has quietly built around private email routing over the past few years.
What Developers Need to Check
The people who actually have work to do here are developers and email service providers. Apple has flagged three areas where action may be needed:
- Account systems and email validation logic that check address format or domain
- Allowlists that currently only accept the two legacy domains
- Domain-based filtering, suppression lists, or routing rules on the provider side
Any app or website using Sign in with Apple that validates or filters by domain will need to add private.icloud.com to its accepted list before the cutover arrives.
The consolidation also signals something Apple has not made a point of advertising: Sign in with Apple and Hide My Email, though launched separately and marketed differently, are functionally the same plumbing. Both generate throwaway forwarding addresses to keep a user’s real email off third-party servers. Putting them under one roof makes that architectural overlap explicit.
Whether this eventually leads to a more unified privacy settings interface, or stays purely at the infrastructure level, the source material does not say. For now, the deadline is sometime this summer, and the developer side has the shorter checklist.
0 Comments