Apple is moving Sign in with Apple and Hide My Email to private.icloud.com (June 2026)

Original announcement (source): Apple Developer News - “New domain for Sign in with Apple and iCloud+ Hide My Email” (June 15, 2026)

• https://developer.apple.com/news/?id=sus6t6ab

What’s changing

Later this summer, Apple says it will unify the email domains used by:

• Sign in with Apple relay addresses (previously issued on privaterelay.appleid.com), and
• iCloud+ Hide My Email addresses (previously issued on icloud.com)

…under a single domain: private.icloud.com.

Important: Apple says existing addresses will keep working and forward mail “without interruption”. This is about newly generated addresses.

Why growth and product teams should care

This is one of those changes that only shows up as “random” problems:

• login/signup flows rejecting a valid email
• support tickets (“I’m not getting emails”) that look like deliverability issues
• lifecycle/CRM messages quietly suppressed because of domain-based rules
• fraud / risk systems flagging a “new” domain unexpectedly

What to update (tiny win)

If you do anything domain-specific today, add private.icloud.com.

1. Email validation and allowlists

• Accept private.icloud.com in addition to privaterelay.appleid.com and icloud.com.
• If you block disposable/relay domains by default, make sure you are not accidentally blocking Apple’s relay.

2. ESP filtering, suppression lists, and routing

• If you have rules that explicitly enumerate relay domains, include private.icloud.com.
• Check any “domain-level suppress” logic (common in CRM tooling when teams try to reduce bounces).

3. Instrumentation and QA

• Add a basic test case to your signup/login QA checklist: create a new Sign in with Apple account, confirm the address can be stored, and verify at least one triggered email reaches it.

Read the original: https://developer.apple.com/news/?id=sus6t6ab