Apple just moved to tidy up one of its more fragmented privacy offerings. Later this summer the company will begin issuing new addresses for both Sign in with Apple and its iCloud+ Hide My Email feature from the same domain: private.icloud.com.
The change ends a split that has long distinguished the two tools. Sign in with Apple has routed masked emails through privaterelay.appleid.com. Standalone Hide My Email addresses created via iCloud+ have used icloud.com. Now new ones from either path will share the fresh domain. Apple Developer News spelled out the details in a brief post dated June 15, 2026.
Existing addresses stay untouched. Mail sent to legacy domains will keep forwarding without interruption. Users notice nothing. Developers and email providers, however, face homework.
Those building apps or sites that accept Sign in with Apple must expand their validation logic, account systems and allowlists to embrace private.icloud.com alongside the older ones. Email services need to adjust any hard-coded filtering, suppression lists or routing rules that list specific relay domains. Fail to update and some masked emails could bounce or land in spam.
And that’s the rub. What looks like a housekeeping move on Apple’s side carries real operational weight for partners. MacRumors reported the announcement within hours, noting that service providers may need to revisit domain-based rules. The story echoed the official guidance without adding speculation.
Hide My Email has grown popular since its debut. iCloud+ subscribers can generate random forwarding addresses on demand, whether through Safari autofill or the dedicated settings panel. The addresses forward mail to the user’s real inbox while shielding the actual address from marketers, trackers and data brokers. Replies work too, within limits. But users cannot initiate new outbound messages from the alias itself, a restriction that has drawn occasional complaints on forums.
Sign in with Apple takes a different route. When a user chooses to hide their email during account creation, Apple generates a unique relay address tied to that specific app or site. The service authenticates via Apple ID yet never shares the real email unless the user opts in. This built-in masking has appealed to privacy-conscious consumers tired of signing up with personal details.
Until now the separate domains created a visible distinction. Tech observers could sometimes tell at a glance whether an address came from a one-off Hide My Email creation or a Sign in with Apple session. The unified private.icloud.com domain blurs that line. It also streamlines Apple’s backend. One relay infrastructure, one set of domain reputation concerns, one brand to defend.
The timing feels deliberate. Apple has spent years positioning privacy as a competitive edge. Its marketing hammers home how the company avoids selling user data. Features like App Tracking Transparency, on-device processing and now this domain consolidation reinforce the message. Yet the change also hints at scale. Millions of masked addresses exist. Managing them under two or three domains adds unnecessary complexity.
Developers have mixed feelings. Some welcome fewer domains to track. Others worry about spam filters that already treat Apple’s relay addresses with suspicion. One forum commenter on the MacRumors story put it bluntly: “This will make it much easier to block. Not a fan.” The remark captured a practical anxiety. If private.icloud.com becomes the default, bulk blockers could sweep up legitimate mail from services using the feature.
Apple offers documentation to ease the transition. Its page on communicating using the Private Email Relay Service already outlines best practices for handling these addresses. The company urges developers to treat them like any other customer email while respecting the forwarding rules. No sender verification beyond the designated relay is allowed.
From a user perspective the update brings welcome consistency. A single domain may reduce confusion when managing multiple aliases in the iCloud settings. It also aligns the free masking available through Sign in with Apple with the paid iCloud+ version. The distinction between free and subscription tiers remains intact. Sign in with Apple masking stays free for supported logins. Full Hide My Email management and unlimited aliases require the paid plan.
Industry analysts see the move as part of broader efforts to make privacy tools less cumbersome. When features feel fragmented they see lower adoption. A cleaner architecture could encourage more users to choose masking over sharing real addresses. That in turn starves data brokers of fresh personal information.
But success depends on execution. If developers drag their feet on updates, some users could face delivery problems. Email providers that ignore the new domain risk false positives in their filtering. Apple has given no exact date beyond “later this summer,” leaving partners to monitor for rollout notices.
The 9to5Mac report that first surfaced widely on social media captured the practical stakes. Its coverage highlighted the need for allowlist changes and noted that legacy addresses would continue forwarding normally. The piece spread quickly on X, where developers posted reminders to update validation code before the change hits production systems.
Privacy advocates applaud the direction even if they quibble with details. A unified domain simplifies explanation to non-technical users. It also signals that Apple views these relay services as permanent fixtures rather than experiments. The company has expanded Hide My Email access over time, integrating it deeper into Safari, Mail and system settings.
Still, limitations persist. Users cannot easily send from these addresses. Support for custom domains or labels varies. And the entire system depends on Apple’s willingness to maintain the relay. Should the company ever alter forwarding policies, users with dozens of aliases could face disruption.
For now the announcement represents incremental progress. Apple took two overlapping but distinct privacy features and removed an artificial separation. The result looks cleaner. Whether it proves more effective at protecting users will show up in adoption numbers and complaint volumes over the coming year.
Developers who act early will avoid headaches. Those who wait risk silent failures when new masked emails start arriving from private.icloud.com. The window is short. Summer arrives fast in the tech calendar.
Apple has built its reputation on thoughtful friction. This domain consolidation removes a small one. In doing so it may remove barriers that kept some users from embracing its privacy tools altogether. The real test comes when the first addresses bearing the new domain land in inboxes worldwide.
WebProNews is an iEntry Publication