Yes, you can email users who have Apple's private relay email addresses, but there are specific requirements and considerations to ensure successful delivery. These addresses, often ending in privaterelay.appleid.com or @icloud.com (for Hide My Email), are designed to protect user privacy by masking their real email. For successful delivery, senders must be authorized by Apple to communicate with these addresses, typically by associating their sending domain with the app or service through which the user generated the relay address. Failing to meet these authentication and consent requirements can lead to email bounces and poor deliverability.
Email marketers often approach Apple Private Relay addresses with caution, balancing the desire to reach their audience with the need to respect user privacy and Apple's guidelines. The primary concern revolves around whether these masked addresses allow for continued engagement, especially for retargeting or promotional campaigns. Many realize that proper consent and technical setup are paramount to avoid deliverability issues.
Marketer view
Marketer from Email Geeks asks: If a list of users contains Apple Private Relay email addresses, can email still be sent to the actual user behind the masked address? This is a fundamental question for targeting campaigns. Understanding how these addresses function is crucial for list management and ensuring message delivery for ongoing engagement.
Marketer view
Marketer from DailyStory notes: While sending marketing emails to privaterelay.appleid.com addresses is technically possible, it is not recommended for general marketing purposes. Apple's design prioritizes user privacy, and broad, unsolicited campaigns can violate these principles. This approach may lead to negative deliverability outcomes, including emails being sent to spam folders or even blocklisted.
Email deliverability experts highlight the critical distinction between Apple Private Relay addresses obtained through Sign in with Apple and those created directly by users via Hide My Email. They stress that for Sign in with Apple, only the associated app should send messages, enforcing a strict consent model. Proper domain registration and verification with Apple are consistently emphasized as non-negotiable technical requirements to ensure message delivery and avoid being perceived as spam.
Expert view
Expert from Email Geeks explains: Apple Private Relay addresses are generated in two main ways. Firstly, users can create them via the "Hide My Email" feature, typically resulting in @icloud.com addresses. Secondly, Apple generates them as part of the "Sign in with Apple" feature, often using privaterelay.appleid.com. For the latter, only the specific app the user signed into should have consent to send mail. If you are not the owner of that app, you likely won't be able to email those contacts successfully. This is a strict privacy enforcement measure by Apple.
Expert view
Expert from SpamResource.com states: Achieving deliverability to Apple's Private Relay requires strict adherence to authentication protocols, including SPF, DKIM, and DMARC. These foundational email security measures are essential for any sender, but they are particularly critical for Apple, which prioritizes user security and privacy. Non-compliance will invariably lead to messages being rejected or routed to spam folders.
Apple's documentation outlines the technical requirements for communicating with users via the Private Email Relay Service. It emphasizes that apps and websites using Sign in with Apple must verify their sending domains. This ensures that only authorized entities can send emails to the unique, random addresses provided by Apple, thereby maintaining user privacy and reducing unwanted communication. The documentation provides clear guidelines on how to set up and manage this communication effectively.
Technical article
Apple Developer documentation states: To send email through the private email relay service, ensure your email sending domain is registered and verified with Apple. This crucial step links your domain to your developer account and grants the necessary permissions for Apple to relay your messages securely to the private email addresses. Without this registration, your emails will not pass through the relay.
Technical article
Customer.io documentation highlights: After completing all necessary authentication steps, you should be ready to send emails to customers utilizing Hide My Email addresses. Proper setup includes verifying sending domains, setting up SPF and DKIM, and ensuring DMARC policies are aligned. This comprehensive approach is essential for successful message delivery through Apple's privacy-focused system.
9 resources
What are the email deliverability impacts of Apple's Sign-in with Apple private relay service?
What are Apple's privaterelay.apple.com and hide my email and how should they be handled in email marketing?
Should I suppress Apple private relay addresses and how to handle them?
Why are emails sent through Apple Private Relay going to spam?
A simple guide to DMARC, SPF, and DKIM
Email Deliverability Issues: Getting Your Messages to the Inbox in 2025
How does Apple Private Relay encode email addresses and how does domain whitelisting affect deliverability?
What happens when your domain is on an email blacklist?
What causes '5.7.1 Email rejected due to transformation error' bounces from Apple's privaterelay.appleid.com and how to fix it?
Why Your Emails Fail: Expert Guide to Improve Email Deliverability [2025]