What the message means

Guideline 5.1.1 has ten numbered parts, (i) to (x). Each covers one part of how the app collects and keeps personal data. Start with the part Apple cites.

Common causes

  • The privacy policy is missing or incomplete (5.1.1(i)). Apple wants a link in the App Store Connect metadata and inside the app where people can find it easily. The policy must say what data the app collects, how it collects it and every use of it. It must confirm that third parties such as analytics or ad SDKs protect the data equally, and explain retention, deletion and how to revoke consent.
  • Purpose strings are vague (5.1.1(ii)). They must clearly and completely describe how the app uses the data. A missing purpose string is a separate upload error, covered in ITMS-90683.
  • A paid feature only works if people grant data access (5.1.1(ii)). Apple says paid functionality must not depend on it.
  • The app asks for more than it needs (5.1.1(iii)), for example full Photos or Contacts access where the out-of-process picker or a share sheet would do.
  • The app tries to force or trick people into unnecessary access (5.1.1(iv)), or offers no alternative where one is possible. Apple's example: if someone will not share Location, let them enter an address by hand.
  • The app requires a login but has no significant account-based features (5.1.1(v)).
  • The app supports account creation but does not let people start deleting the account in the app (5.1.1(v)). Apple's deletion guidance says this also applies when the account is created in a web browser or automatically, as a guest account.
  • The app requires personal information that is neither core to the app nor required by law (5.1.1(v), (x)).
  • The submitter is an individual for an app in a highly regulated field such as banking, healthcare, gambling, air travel or crypto exchanges (5.1.1(ix)).

Fix it step by step

  1. Find the numbered part Apple cited and fix that first.
  2. Update the privacy policy so it covers each item in 5.1.1(i), including your SDKs. Link it in App Store Connect and from a screen people can reach easily, such as Settings.
  3. Rewrite every purpose string so it says what the app does with the data and why. A string like "We need access" does not say what the data is for.
  4. Remove permissions the core feature does not need, and switch to the system picker or share sheet where you can.
  5. Where possible, give people a way forward when they decline: manual entry, a limited mode or a skip button.
  6. Let people use the app without a login if it has no significant account features. If it supports account creation, add account deletion.
  7. Make deletion complete. Apple's account deletion guidance asks that people can start it in the app, that it is easy to find (usually in account settings), and that it deletes the whole account record with the related personal data. Only deactivating the account is not enough. If people finish on your website, link directly to that page. If the law requires you to keep some data, tell people what you keep. Outside highly regulated industries, people should not have to call, email or use a support chat to finish.
  8. Check the privacy manifest and third-party SDKs if the rejection mentions required reason APIs. See the privacy manifest checklist.

Reply in Resolution Center

Resolution Center is the App Review section of your app in App Store Connect. Point to each fix by screen, so the reviewer can confirm it without searching.

Hello App Review team,

Thank you for the note about Guideline 5.1.1([part]).

What we changed in build [number]:
- Privacy policy: [URL], linked from [screen] and in App Store Connect
- Purpose strings: [permission] now reads "[new text]"
- Account deletion: [Settings > Account > Delete account], removes [what is deleted]
- Sign-in: [e.g. the app can now be used without an account; sign-in is only needed for sync]

How to check it:
1. [step]
2. [step]

Demo account: [username] / [password]

Thank you,
[name]

Before you resubmit

  • The privacy policy link is in App Store Connect and easy to find inside the app.
  • The policy covers collected data, uses, third parties, retention, deletion and consent withdrawal.
  • Every purpose string says what the data is used for.
  • The app asks only for data the core feature needs, never forces unnecessary access, and offers an alternative where one is possible.
  • Paid features do not depend on granting data access.
  • People can use the app without a login unless it has significant account features.
  • People can start deleting their account in the app, and deletion covers the whole account and its personal data, apart from what the law requires you to keep.