The Impending Obsolescence of "Hide My Email"

By Arseniy Shestakov | Published: June 16, 2026

🚨 The Announcement

On June 15, 2026, a seemingly minor update was posted within the Apple developer news feed. The update concerned a New domain for Sign in with Apple and iCloud+ Hide My Email.

"Now both Sign in with Apple and Hide My Email aliases are going to be issued on the @private.icloud.com subdomain."

What is actually changing?

Previously, aliases were blended in a way that made them harder to distinguish from standard accounts. Now, Apple is segregating them.

Feature	Previous State	New State
Domain	Mixed/Standard	`@private.icloud.com`
Visibility	Blended with iCloud mail	Clearly identified as a relay
Blockability	Difficult to target specifically	Extremely easy to blacklist

📉 The Impact on Privacy

This shift is a ~~major improvement~~ significant blow to iCloud privacy. In the past, the "plausible deniability" of using an iCloud address, backed by Apple's reputation, made it expensive for services to ban aliases without risking the loss of legitimate users.

The Logic of the Ban

With the new subdomain, services can now implement a simple filter:

if email.endswith("@private.icloud.com"):
    reject_registration("Temporary/Relay emails not allowed")

Visualizing the Blocking Process

⚠️ The Consequences

The primary risk is that these aliases will now be treated exactly like free temporary mailboxes.

Loss of Anonymity: Services can instantly flag you as a "privacy-seeking" user.
Service Refusal: Many platforms will simply refuse to accept any email ending in the new subdomain.
Reduced Utility: The "Hide My Email" feature becomes effectively useless if the destination won't accept the address.

🛠️ Action Plan for Users

If you rely on iCloud+ for your privacy, you should act immediately before this change is fully deployed.

Identify critical services requiring aliases.
Generate as many @icloud.com aliases as possible.
Verify that the aliases are active.

Note on Rate Limits: The current capacity for creating these aliases is defined by the following limit: $\text{Creation Rate} \ge 30 \text{ aliases} / \text{hour}$

Privacy Warning

Hopefully, this feedback reaches Apple's decision-makers so they can reconsider this architectural shift.