A site rejects the @private.icloud.com address during Sign in with Apple registration.
Fastest answer: there is no universal acceptance guarantee. Apple has asked developers to support the new domain, but each site controls its own address rules. Check the site’s instructions, then choose an email you can keep accessing for the account’s lifetime.
This guide is for you if you’re choosing Hide My Email during Sign in with Apple and want to know where messages go. It also helps if you already use an Apple relay address and are worried about rejection or missed messages, or if you’re comparing an Apple relay with a temporary inbox.
Last updated October 28, 2026. Checked against Apple’s developer announcement and current Apple Support guidance; confirm the target site’s own registration instructions before changing an address.
Start by separating the address from the delivery path
“Will Sign in with Apple’s private.icloud.com address be rejected?” has two different answers to check:
- Will the site accept the address? The site’s form validation and account policy decide. Apple’s developer guidance is not a promise that every site will accept the address.
- If the site accepts it, will its email reach you? That depends on the Apple relay configuration, the destination address associated with your Apple Account, and whether the sender is allowed to use the relay correctly.
Those checks are related, but they are not interchangeable. A site can accept an address and still fail to deliver a message. Or its form can reject the address before Apple’s forwarding system has any message to relay.
Apple’s developer announcement, updated August 24, 2026, says new Sign in with Apple addresses are planned to use private.icloud.com. It also says existing privaterelay.appleid.com addresses will continue to work and forward email. The same announcement says iCloud+ Hide My Email addresses will continue to use icloud.com. That announcement describes Apple’s stated plan; it does not establish that every account has already moved to the new domain. (Apple Developer’s update on private relay addresses)
| Address or service | What it does | What the domain alone tells you |
|---|---|---|
| Sign in with Apple relay address | Gives an app or site an address to use instead of your personal email; Apple relays eligible messages to an associated verified address. | It is part of a relay arrangement, not proof that a particular site accepts it or that you can use it as a separate inbox. |
| Temporary email address | Provides a separate address for receiving messages under the service’s own conditions. | Its lifetime, privacy model, and ability to receive a particular sender’s messages depend on that service. |
| iCloud+ Hide My Email address | Hides your personal address using an address created through Apple’s Hide My Email feature. | Apple’s announcement distinguishes these addresses from Sign in with Apple addresses: they continue to use icloud.com. |
So, is private.icloud.com a temporary email domain? Not by itself. A Sign in with Apple relay address is tied to Apple’s sign-in and email-relay arrangement. The domain does not tell you that it is a disposable inbox, how long it lasts, or who can view messages. Do not infer the address’s lifetime or privacy settings from its spelling.
Apple’s explanation of hiding your email when using Sign in with Apple describes the choice between sharing a personal email address and using a private relay address. That is a choice about what address the app or site receives. It is not the same thing as creating a new standalone mailbox.
Compare options by the job the address must do
A useful selection criterion is not simply “which address is most private?” Ask instead whether the address must receive one registration message, ongoing notices, or account-recovery mail. The right option changes with that dependency.
| Option | Best fit | Ongoing access | Main limitation |
|---|---|---|---|
| Sign in with Apple relay address | You want to sign in through Apple without giving the app or site your personal email. | Depends on the Apple relay and the verified destination address associated with your Apple Account. | A site may not accept the address; the relay is not a separate inbox that bypasses site rules. |
| Long-term personal email | The account matters, needs recovery, or may send important notices over time. | You can keep access as long as you maintain the mailbox. | The site receives your personal email address unless another supported privacy option is used. |
| Email alias or forwarding address | You want to separate messages by service while keeping an address you control. | Depends on the alias or forwarding setup remaining active. | Setup and provider controls vary; an alias may still be rejected by a site. |
| Temporary receiving address | You need a short-lived address for a low-stakes registration and the site allows it. | Do not assume continued access unless the service clearly documents it. | Poor fit for account recovery, ongoing contact, or messages you cannot afford to miss. |
Apple’s relay is not equivalent to a temporary email website. With Sign in with Apple, the app or site sends email to the relay address, and Apple forwards eligible messages to the verified email associated with your Apple Account. A temporary inbox instead relies on the temporary-mail service’s own receiving and retention conditions. Neither option forces a site to accept a particular address.
For a broader explanation of how Apple relay addresses differ from temporary email, compare the address’s purpose and ongoing access requirements, not just whether both can hide a personal inbox.
Check what the target site accepts
The site’s registration form is the authority on its own acceptance rules. Apple’s developer compatibility recommendation is aimed at developers; it cannot guarantee a result for every user on every site. A site may validate email syntax, apply account policies, or restrict certain categories of address. The cause of a rejection may not be visible from the address alone.
| What you see | What it tells you | Safe next action |
|---|---|---|
| The form says the address format is invalid | The site’s input check did not accept what was entered. | Recheck for typing errors and follow the site’s stated email requirements. |
| The site says the address type is not allowed | The site appears to restrict that type of address. | Use an address type the site permits; do not try to disguise or bypass the restriction. |
| The form accepts the address, but no message arrives | Acceptance and delivery are separate; the message may not have reached the relay or destination inbox. | Check the Apple relay settings and the destination inbox, then consult the site’s support guidance. |
| A registration link arrives, but later notices do not | Initial verification does not prove that future messages will always arrive. | Confirm the relay remains enabled and use an address you can keep accessing for important accounts. |
If a site does not accept an Apple relay address, what should you do? Read the exact message and the site’s published instructions. If it requires an address you can access directly, use an eligible address that meets that requirement. If the site offers its own supported Sign in with Apple option, follow that flow rather than entering a relay address into a separate email-registration form. If the site explicitly disallows relay or disposable addresses, do not try to evade the rule by cycling domains or disguising the address.
That distinction matters for the term Sign in with Apple email relay. The relay affects how a message may be forwarded after the site sends it. It does not change the site’s account policy. A domain change on Apple’s side also does not automatically mean every website has updated its validation rules—or that every user has already received a new-domain address.
Check where messages go and who forwards them
When you choose Hide My Email in Sign in with Apple, the app or site receives a relay address instead of your personal email. Messages sent to that relay can be forwarded to the verified email associated with your Apple Account, according to Apple’s relay setup and rules. In practical terms, the relay address is the destination the site sees; it is not necessarily the inbox where you open the message.
Apple’s Support guidance explains the Hide My Email choice, while its account settings guidance shows how to review apps using Sign in with Apple and manage related settings. (Manage your Sign in with Apple settings) If delivery stops, check whether the relevant app’s forwarding setting is active and whether the destination mailbox can receive messages. Also check the destination inbox’s spam folder and any filters.
The developer-facing private email relay documentation describes requirements for sending through Apple’s relay. This is one reason a missing message does not automatically prove the address is invalid: the sender’s configuration, the relay, and the receiving mailbox are separate parts of the route.
For reader-side troubleshooting, check the settings rather than assuming the domain itself is the problem:
- Confirm which sign-in method was used. Check whether the account was created with Sign in with Apple or with a conventional email-and-password form. Those may use different addresses.
- Find the address shown for that app or site. Review the Sign in with Apple settings associated with your Apple Account. Do not substitute an iCloud+ Hide My Email address for a Sign in with Apple relay address without checking which one the account uses.
- Check the forwarding destination and status. Make sure the relay is set to forward to an email inbox you can access. If that destination mailbox is closed, full, or filtered, the relay cannot make it useful to you.
- Check the destination inbox, including spam and filters. Search for the sender or the site’s name. A message placed in a filtered folder can look like a delivery failure.
- Request a new verification message only through the site’s normal flow. Follow the site’s own resend instructions; avoid creating repeated accounts or trying to circumvent an address restriction.
- Ask the site for an allowed alternative if the address is rejected. Use the email type it explicitly permits, especially when the account will need future recovery.
These checks do not promise that a particular message will arrive. They help identify whether the block is at the site’s registration form, the sender’s relay configuration, the Apple forwarding settings, or the destination inbox.
Choose by future access, not by the first verification message
The immediate registration email is only one part of the decision. The more important question is what happens when the account sends a password-reset link, a security notice, a receipt, or a message that requires a reply. An address that works for initial verification may still be a poor choice if access is difficult to maintain.
Use this decision list before you continue:
- If the account is important, stores personal or financial information, or may need recovery later, choose a long-term email address that you can keep accessing and that the site accepts. Do not depend on a temporary receiving address for recovery.
- If you want to hide your personal email and the site supports Sign in with Apple, use the Apple flow and verify that the relay forwards to an inbox you control. Keep that destination inbox available.
- If the site rejects the Apple relay address, follow its stated requirements and choose an allowed address type. Do not attempt to bypass the restriction by changing the address’s appearance.
- If you only need a low-stakes registration and the site permits a temporary address, assess whether the service’s current page clearly explains its receiving and access conditions. If those conditions are unclear, use an address you can reliably reach instead.
- If you need to send replies or maintain a continuing email conversation, choose an address and service that explicitly support that use. Do not assume that a relay or temporary inbox can send mail simply because it can receive it.
The Apple Support overview of Sign in with Apple is useful when you need to confirm how the sign-in option works. The address option should be treated as part of an account-access plan, not as a guarantee that every site will accept the same address format.
There is a practical difference between “I can receive one code” and “I can recover this account next year.” A registration code is a short-term task; recovery depends on continued access to the address and on the site still recognizing it. For accounts that matter, a stable mailbox or a supported Apple relay with a working forwarding destination is safer than an address chosen only to finish the form quickly.
Use temporary receiving only when its limits fit
A temporary address can be useful when the registration is low-stakes, the site permits that address, and future messages are not important. It is not a universal substitute for Apple’s relay, an account-recovery mailbox, or an address the site requires you to maintain.
Before using any temporary email service, check its current page for the functions that matter to the specific task: whether you can create an address, whether registration is required, whether forwarding is offered, which domain suffixes are available, and how long the address and messages remain accessible. These details vary by service and can change. No specific address lifetime, message-retention period, domain count, or delivery time should be assumed unless the service clearly states it.
For a time-sensitive verification, review the current email-arrival guidance and the live service information before relying on a temporary inbox. A feature being available on a service page does not mean the target website will accept its address, and it does not make the address suitable for long-term recovery.
The same caution applies to privacy. Hiding your personal address from a site is not the same as making every message private from every party in the delivery chain. Check who operates the address, where messages are delivered, and what the service says about access and retention. ForwardEasy’s privacy policy is the place to review its stated privacy practices; those practices should be considered separately from Apple’s relay rules.
If the only goal is to avoid exposing a personal email during an ordinary, low-risk signup, a temporary receiving address may be worth considering after checking the site’s rules and the current capabilities shown by ForwardEasy. If the account needs ongoing notices, replies, or reliable recovery, use an address you can keep accessing instead. That distinction—not the domain name alone—should decide whether a temporary inbox is appropriate.
Start with an address that has a countdown
A three-hour default window, extendable before expiry; use a sustainable address for important long-term relationships.