Sign in with Apple sends user data to Apple Inc. only at first sign-in — your app receives the user's name and email (or an Apple private relay address) and a stable user identifier, and that transfer of personal data into your systems must be disclosed for App Store review, Google Play and the GDPR. Generate a full privacy policy with this clause built in →
Does Sign in with Apple need a privacy policy disclosure?
Yes — but for a different reason than an analytics or attribution SDK. Apple does not track users across apps or websites when they use Sign in with Apple, and Apple shares data with you only once: on the very first authorization your app receives the user's full name and email address (or a @privaterelay.appleid.com forwarding address if the user chose Hide My Email), plus a stable, app-scoped user identifier and identity tokens. Every later sign-in returns only that identifier and the tokens — no name, no email. So the disclosure you owe is about the account data you store, not about data Apple collects from your app.
Sign in with Apple is App Functionality, not tracking, and needs no App Tracking Transparency prompt. If your app uses any other third-party or social login (Google, Facebook, X, LinkedIn, etc.) to set up the user's primary account, App Store Guideline 4.8 requires you to also offer an equivalent privacy-friendly option — one that limits collection to name and email, lets the user keep the email private, and does not collect app interactions for advertising without consent. Sign in with Apple satisfies all three; a compliant custom email login also works.
What data does Sign in with Apple collect?
| Data type | Purpose | Linked to the user? | Used for tracking? |
|---|---|---|---|
| Full name (first authorization only, user-editable) | Account creation, personalization | Yes | No |
| Email address, real or Apple private-relay forwarding address (first authorization only) | Account creation, transactional email | Yes | No |
Apple user identifier (the sub claim, stable and unique per developer account) | Recognize the returning user | Yes | No |
| Identity token (JWT) and authorization code | Verify the sign-in, obtain refresh/access tokens | Yes | No |
| Real user status indicator (likelihood the account is a real person) | Fraud / bot mitigation | Yes | No |
Apple does not give you a device identifier, IP address, location, contacts or usage data through Sign in with Apple. The exact data you hold depends on what you request and store: if you only ask for the identifier you never receive name or email; if the user picks Hide My Email you store a relay address and must register your outbound sending domains and addresses with Apple to email them.
Copy-paste privacy policy clause for Sign in with Apple
Sign in with Apple. We offer Sign in with Apple, provided by Apple Inc.,
as a way to create and access your account. The first time you sign in,
Apple provides us with your name and the email address you choose to
share -- either your real address or a private relay address that
forwards to you -- together with a unique identifier that lets us
recognize you on future sign-ins. On later sign-ins we receive only that
identifier and short-lived authentication tokens. Apple does not track
your activity in our app when you use Sign in with Apple. We act as the
controller of the account data you provide and use it only to operate
your account and send service communications. If you delete your
account, we delete this data and revoke your Apple tokens. Learn more at
https://www.apple.com/legal/privacy/.Adapt this: if you request only the identifier scope, remove the name and email sentence. You are responsible for making the wording match your implementation; this is a starting point, not legal advice.
App Store "App Privacy" label answers
Declare the data you store from Sign in with Apple, in App Store Connect:
- Contact Info > Name — purpose "App Functionality". Linked to the user: Yes. Used to Track You: No.
- Contact Info > Email Address (real or private-relay) — purpose "App Functionality". Linked: Yes. Used to Track You: No.
- Identifiers > User ID — the Apple user identifier. Purpose "App Functionality". Linked: Yes. Used to Track You: No.
- Do not declare Device ID, Location, Usage Data or Diagnostics for Sign in with Apple — none of it is provided.
If you request only the identifier and never receive name or email, declare just Identifiers > User ID.
Google Play Data Safety answers
Sign in with Apple is primarily an iOS feature, but if you ship an Android or web build using Sign in with Apple JS, declare in the Play Console Data Safety form the data you collect through it:
- Personal info > Name — Collected: Yes. Shared: No. Purpose: Account management, App functionality. Users can request deletion.
- Personal info > Email addresses — Collected: Yes. Shared: No. Purpose: Account management, App functionality.
- Personal info > User IDs — the Apple identifier. Collected: Yes. Shared: No.
- Nothing here is "processed ephemerally"; mark deletion as available.
Apple itself does not publish a Data Safety entry because it is not distributing an Android SDK for this; your declaration covers only what your own code stores.
Sign in with Apple-specific gotchas
- Name and email arrive exactly once. If you fail to persist them on the first authorization, you cannot get them again from Apple — you must ask the user to revoke access in their Apple ID settings and sign in again. Store them immediately.
- Account deletion requires token revocation. Apple Guideline 5.1.1(v) requires that deleting an account also revokes the user's Apple tokens:
POST https://appleid.apple.com/auth/revokewithclient_id, a signed-JWTclient_secret, thetoken, andtoken_type_hint. See Apple's technote TN3194. Build the flow with the account deletion page generator. - Private relay needs domain registration. To email a Hide My Email user you must register and verify your sending domains and from-addresses in the Apple Developer portal, or your mail bounces.
- Relay addresses can be deactivated. A user who turns off email forwarding or deletes their Apple ID breaks your only contact channel; do not treat the relay address as a permanent identifier.
- Guideline 4.8 is about the primary account. It triggers only when a third-party or social login sets up the user's main account — a "connect your calendar" style secondary login does not trigger it.
- Handle the server-to-server revoke notification. Apple sends notifications when a user disables or deletes their Apple ID; process them to disable or delete the corresponding account, and note this in your policy. You are responsible for accuracy.
Related
See the sibling clauses for Firebase Authentication, AppsFlyer, Adjust and Branch. Build the deletion and token-revocation flow with the account deletion page generator, produce the full document with the privacy policy page generator, and see the Firebase privacy policy generator guide if you use Firebase Auth for Apple sign-in.