An alias changes the address you disclose
Hide My Email can generate a random address that forwards messages to a personal inbox. The broad address-creation feature described here requires iCloud+. It reduces the need to reveal your usual email address to each website, but it does not hide the other information you provide, erase an existing account or stop a service from recognizing a signed-in customer.
There is also a Hide My Email option associated with Sign in with Apple. That belongs to a particular sign-in relationship and should not be confused with every manually created iCloud+ alias. Before changing or disabling an address, identify which feature created it and which account depends on it.
Create one address for one recognizable purpose
On iPhone, open Settings > your name > iCloud > Hide My Email. Choose Create New Address and follow the prompts. Give the address a label that identifies the service, such as Museum newsletter, and add a short note if the purpose would otherwise be unclear. The label is for your management; it is not a claim that the service will display the same name.
Copy the generated address into the intended sign-up form. Check that it is complete and has not been replaced by your usual address through another autofill suggestion. After signing up, confirm that the expected verification or welcome message reaches the forwarding inbox. Do this before relying on the alias for an important account.
Know where forwarding goes
The Hide My Email settings include a Forward To choice from eligible addresses associated with your Apple Account. Inspect that destination if messages seem absent. Then check the receiving mailbox's spam or filtering rules. An alias can be configured correctly while the forwarded message is being sorted somewhere unexpected.
For an important service, record the alias as that service's login address in your password manager. The address you use to sign in may be the generated alias, not the inbox where messages arrive. Confusing those two addresses can make an account look missing when you simply entered the wrong identifier.
| Use case | Helpful management habit | Before disabling the alias |
|---|---|---|
| Newsletter | Label with the publication's name | Decide whether unsubscribing is more appropriate |
| Online purchase | Keep the alias with the merchant's login | Preserve receipt, delivery and return communications |
| Long-term account | Store the exact login address with credentials | Change the service's email and verify the replacement |
| One-off enquiry | Note the subject or organization | Ensure the conversation is genuinely complete |
Work through a purchase example
You use a new alias for a small shop's account. Save that alias with the shop's password entry and confirm the order receipt arrives. If the shop later sends unwanted promotions, first distinguish marketing from order and account messages. Use a legitimate unsubscribe route where appropriate rather than cutting off the only address the shop uses for delivery problems or password recovery.
After the order and any return period are settled, you might choose to deactivate the alias if you no longer need the relationship. If you intend to keep the shop account, change its contact email through the shop's trusted account settings and verify the new address before deactivation. The alias manager cannot update the shop's account records for you.
Deactivate deliberately and understand the effect
In Hide My Email settings, select an address and use Deactivate Email Address when that is the intended outcome. A deactivated address stops forwarding. It does not delete the account that used it, cancel a subscription, remove a payment method or tell the sender to stop retaining information.
If an expected message stops arriving after a change, inspect whether the alias is active and whether the forwarding destination is correct. Apple's management tools can offer reactivation for eligible deactivated addresses. Avoid permanent deletion while you are still investigating which accounts depend on an address.
Reply and test through the intended mail workflow
When replying to a message received through an alias, use the supported reply workflow and inspect the addressing if the conversation is sensitive. Do not manually start a new message from your personal address and assume the old alias will hide it. Creating a fresh outgoing message and replying through a forwarding relationship can behave differently.
For a new recurring use, a harmless test message can establish whether delivery and reply behavior fit the task. Check both the account settings and the actual received message. This is more reliable than treating the presence of an alias in Settings as proof that every mail client and sender will use it correctly.
Keep address privacy separate from account security
Use a strong unique password or a supported passkey and the account's appropriate additional protections. An alias is not a substitute for those controls. If a message claims that your Apple Account is locked, inspect it through the phishing workflow rather than trusting it because it arrived at a private alias.
A small, well-labeled set of aliases is easier to manage than many anonymous entries you cannot connect to services. The aim is controlled disclosure with a dependable way back into the accounts you still use. The Passwords guide explains how to keep that login record distinct from the forwarding inbox.
Sources & further reading
Apple’s documentation supports the feature details. The scenarios and decision sequences above are CJVV’s editorial guidance.