Apple has narrowed an upcoming change to its private email relay domains. In an August 24 developer update, the company said new Sign in with Apple addresses will move from privaterelay.appleid.com to private.icloud.com later in 2026.
The same update leaves iCloud+ Hide My Email addresses on icloud.com. Apple had previously planned to move new addresses from both features to the shared private.icloud.com domain.
Existing privaterelay.appleid.com addresses will continue to work and forward mail. The immediate task for developers is therefore compatibility, not an account or address migration.
Apple split its June domain plan
Apple’s original announcement on June 15 proposed moving new Sign in with Apple and Hide My Email addresses to private.icloud.com later in the summer.
Under that plan, new Hide My Email addresses would have moved away from icloud.com. Existing addresses on the older domains were still expected to remain operational.
The August update withdraws the Hide My Email portion after what Apple described as further consideration and community feedback. The Sign in with Apple domain change remains scheduled for later in 2026.
Apple has not published an exact activation date, a regional schedule, or detailed rollout mechanics. Teams should treat this as an announced compatibility requirement rather than a completed release.
Sign in with Apple still requires code changes
Sign in with Apple can provide a user with a private relay address instead of revealing the person’s underlying email address. Apple’s private email relay documentation explains that messages sent to the relay address are forwarded to a verified address on the user’s Apple Account.
Applications may store that relay address in account, contact, notification, or support systems. Apple says existing addresses will remain valid, so those records do not need to be rewritten merely because the new domain is introduced.
Apple specifically tells developers using Sign in with Apple to update account systems, email validation logic, and allowlists to accept private.icloud.com.
Support for the new suffix must be added alongside privaterelay.appleid.com, not used as a replacement. Removing the older domain could reject existing users whose relay addresses remain active.
Teams should inspect strict email-domain comparisons, regular expressions, registration validators, import pipelines, notification systems, and administrative tools wherever they make decisions based on the address suffix.
Test fixtures should cover both Sign in with Apple domains before the rollout. Developers should not assume that an existing user will receive a replacement address unless Apple documents a separate reissue process.
Hide My Email remains a separate path
Hide My Email is an iCloud+ feature that creates random addresses which forward messages to a user’s personal inbox. Apple’s current support guide describes its use across Apple devices, iCloud.com, and supported app or website fields.
Apple now says Hide My Email addresses will remain on icloud.com. The August notice does not announce a new developer migration for that feature.
The two services can look similar because both conceal a personal address, but they serve different workflows. Sign in with Apple supplies a relay address during an authentication flow, while Hide My Email lets an iCloud+ user create an address for a broader range of interactions.
Systems that classify or route these addresses should preserve that distinction. The revised notice does not justify treating every icloud.com address as a new Sign in with Apple relay address.
What teams should verify before the rollout
Start by inventorying every service that validates, stores, imports, exports, filters, or routes Sign in with Apple addresses. Confirm that private.icloud.com is accepted without disabling privaterelay.appleid.com.
Once Apple begins issuing the new addresses, test registration, login recovery, notifications, support workflows, and mail delivery with an actual new relay address. Monitor rejected registrations and mail failures for suffix-dependent rules missed during the audit.
The exact switch date remains unknown. Until Apple publishes further details, the safe implementation is to support both Sign in with Apple domains while leaving Hide My Email handling unchanged.
