> For the complete documentation index, see [llms.txt](https://doc.batch.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://doc.batch.com/guides-and-best-practices/email-deliverability/email-authentication-and-sending-structure/sending-subdomain-setup-and-troubleshooting/how-to-set-up-email-delivery-to-apples-private-relay.md).
# Setting Up Email Delivery to Apple’s Private Relay
Here is what you need to do to be able to reach users who signed up using the "Sign in with Apple" feature.
## About “Sign in with Apple”
Since iOS 13, the “[Sign in with Apple](https://support.apple.com/en-gb/HT210318)” feature allows developers to offer a new single sign-on (SSO) option. Just like Google / Facebook SSO, it allows users to create an account that will be tied to their Apple ID. Developers must include that option in their app if the app already offers other third-party SSO solutions.
When logging in, users can choose to:
1. Share their email address (e.g. ).
2. Or to hide it using the “Hide My Email” feature. That feature relies on Apple's private email relay service. It creates a unique, random email address that forwards emails to the users’ personal email address. Here is an example:
## Sending an Email to an Address Behind Apple’s Private Relay
Whether users decide to share their email addresses with the service or not, an additional setup is required to deliver emails to these email addresses.
You will need to declare to Apple the subdomain you are using, so Apple can whitelist it when forwarding the emails to the users.
To do so, you need to take the following steps:
{% stepper %}
{% step %}
Go to the [Apple Developer console](https://developer.apple.com/account/), click “Certificates” and then go to “Services” in the left panel.
{% endstep %}
{% step %}
Click “Configure” in the “Sign in with Apple for Email Communication” block.
{% endstep %}
{% step %}
Then, click “**+**”, type the list of bounce subdomains set up with Batch and save.
* **Strict alignment setup (default)**: Type your subdomain name (e.g. `subdomain.domain.com`):
* **Relaxed alignment setup**: In this case, SPF is evaluated on the bounce subdomain. Type your bounce subdomain name (e.g. `bounce.subdomain.domain.com`).
{% endstep %}
{% step %}
From the subdomain list, click “(Re)Verify SPF” if it is not already green.
{% endstep %}
{% step %}
If the SPF is validated, send a test to an email address tied to an Apple account from the Batch dashboard:
{% endstep %}
{% endstepper %}
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://doc.batch.com/guides-and-best-practices/email-deliverability/email-authentication-and-sending-structure/sending-subdomain-setup-and-troubleshooting/how-to-set-up-email-delivery-to-apples-private-relay.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
