Apple has announced a Sign in with Apple email domain change that developers—and users who choose Hide My Email—should understand. Starting later in 2026, newly created private relay addresses for Sign in with Apple will use @private.icloud.com instead of @privaterelay.appleid.com.
The good news is that Apple says existing relay addresses will keep working and forwarding email without interruption. For most iPhone, iPad and Mac users, no immediate action is required. Developers, however, need to check email validation rules and allowlists before the rollout begins.
What is the Sign in with Apple email domain change?
In an Apple Developer update published on 24 August 2026, Apple confirmed that new addresses generated through Sign in with Apple will move to the private.icloud.com domain later this year.
Here is the change in simple terms:
- New Sign in with Apple relay addresses: will use
@private.icloud.com. - Existing relay addresses: will remain on
@privaterelay.appleid.comand continue forwarding messages. - iCloud+ Hide My Email addresses: will continue using the
@icloud.comdomain.
Apple has not given a precise public switchover date beyond saying the new domain will begin appearing later in 2026. The update applies globally, including to users and developers in Australia.
How Sign in with Apple private email relay works
When an app or website offers Sign in with Apple, a user can share their real email address or select Hide My Email. Choosing the privacy option creates a unique relay address. Messages sent by an approved app or website are forwarded to the verified email address attached to the user’s Apple Account.
This means the service can deliver account notices, receipts and password-reset messages without revealing the user’s personal inbox address to the developer. Apple’s Hide My Email support guide also explains that relay messages receive standard spam filtering and are deleted from Apple’s relay servers after delivery.
Why the new private.icloud.com domain matters
For everyday users, the visible difference is small: a newly generated address will have a different ending. The privacy purpose and forwarding behaviour remain the same. Users should not replace or delete existing @privaterelay.appleid.com addresses because Apple says they will continue to operate.
The larger impact is on apps, websites and customer-management systems. Some systems only accept email addresses from known domains or contain a hard-coded check for privaterelay.appleid.com. If those rules are not updated, a new private.icloud.com address could be rejected during registration or account recovery.
That could also affect transactional email. A service may successfully create an account but fail to recognise the new relay domain when sending login codes, order updates or support replies. Preparing early reduces the risk of broken sign-ups and missed messages.
What developers need to do
Apple specifically advises developers with Sign in with Apple integrations to accept the new domain. A practical readiness checklist includes:
- Add
private.icloud.comto email-domain allowlists while keepingprivaterelay.appleid.com. - Review email validation code and avoid rules that assume only one Apple relay domain.
- Test account registration, sign-in, password recovery and email-change flows.
- Check customer-support and CRM tools that may identify relay addresses by domain.
- Confirm that approved outbound sender addresses are correctly configured for Apple’s private email relay service.
- Monitor bounced messages and failed sign-ups when the new addresses begin appearing.
Developers should treat the two domains as valid in parallel rather than migrating old users. This is a compatibility update, not a requirement to rewrite existing customer addresses. Teams tracking broader platform policy updates may also want to read our recent guide to Apple Developer Agreement changes.
Do Apple users need to take action?
Most users do not need to change anything. Continue using Sign in with Apple normally, and expect new hidden addresses to look slightly different later this year. Existing app accounts should continue receiving forwarded mail through their current relay addresses.
If messages from an app stop arriving, first check junk mail and confirm the app’s forwarding status under Settings > your name > Sign in with Apple on iPhone or iPad. You can select an app to see whether Hide My Email is in use. On a Mac, open System Settings > your name > Sign in with Apple.
Be cautious if any message claims you must urgently “upgrade” a relay address or asks for your Apple Account password. Apple’s announcement does not require users to follow an emailed migration link.
Final thoughts
The Sign in with Apple email domain change is designed to be seamless for users, but it creates an important compatibility task for developers. Supporting both private.icloud.com and privaterelay.appleid.com now should prevent avoidable account and email-delivery problems when the rollout starts.
FAQs
When will Apple start using private.icloud.com?
Apple says new Sign in with Apple relay addresses will move to private.icloud.com later in 2026, but it has not announced an exact date.
Will my existing privaterelay.appleid.com address stop working?
No. Apple says existing addresses will continue to work and forward messages without interruption.
Does this change iCloud+ Hide My Email?
No. Apple says iCloud+ Hide My Email addresses will remain on the icloud.com domain. The new domain applies to newly issued Sign in with Apple relay addresses.
Should developers replace users’ old relay addresses?
No. Developers should accept both domains. Existing addresses should be preserved, while validation and allowlist rules should be updated for the new domain.
Leave a Reply