Apple reverses plan to move Hide My Email addresses from @icloud.com to @private.icloud.com

Apple’s decision to abandon the @private.icloud.com domain for Hide My Email addresses resolves a practical problem for users and developers. The original plan would have created a visible distinction between disposable and regular iCloud addresses, undermining the feature’s privacy-by-obfuscation design. Services or scripts that filter or reject sign-ups based on domain patterns could have systematically excluded these addresses, breaking workflows for users who rely on them. By reverting to @icloud.com, Apple ensures the addresses blend in with standard iCloud accounts, maintaining the feature’s effectiveness.

The reversal also highlights the trade-offs in privacy tool design. The @private.icloud.com domain was likely intended to improve transparency or internal routing, but it introduced a new attack surface: websites could trivially block or deprioritize these addresses. For engineers, this underscores the importance of testing privacy features against real-world adoption barriers, not just technical specifications. The backlash suggests users prioritize seamless integration over marginal improvements in backend clarity, a lesson applicable to any service handling anonymized identifiers.

Apple’s silence on the reasoning behind the reversal leaves open questions about internal decision-making. Reports of employee objections suggest the change was contentious, but the lack of public justification may reflect broader tensions between privacy goals and operational constraints. The earlier bug that leaked real email addresses via spam rejections further complicates the narrative, as it revealed a failure in the feature’s core promise. For engineers, this serves as a reminder that privacy tools must be resilient to edge cases, like bounced emails, to avoid undermining user trust.