Rejection guides / Guideline 5.1.1(i): Privacy policy and permission strings
Guideline 5.1.1 - Data Collection and Storage: privacy policy and permissions
5.1.1 rejections usually come down to a missing or thin privacy policy, or permission prompts that don't explain why the app needs access.
"All apps must include a link to their privacy policy in the App Store Connect metadata field and within the app in an easily accessible manner."App Review Guideline 5.1.1(i), Apple
Get your own rejection explained
Paste the message from App Store Connect or Play Console. Free, no account, about ten seconds.
What the privacy policy must cover
- What data the app or service collects, how it collects it, and all the ways it's used.
- That any third party you share data with, such as analytics, ad networks and SDKs, gives the same or equal protection as your policy.
- How long you keep data, how you delete it, and how a person can withdraw consent or ask for deletion.
These follow the three points 5.1.1(i) lists. The link has to be in App Store Connect and also easy to find inside the app.
Permission prompts (5.1.1(ii) to (iv))
- Purpose strings, the text in the system permission alert, should clearly and completely describe how the app uses the data. "We need access to your camera" doesn't explain why.
- Ask only for data relevant to the app's core function. Use the system photo picker or a share sheet where it works instead of full library access.
- Don't block the app, or paid features, because someone declined a permission. Offer a fallback, such as typing an address when location is declined.
- Don't push people to grant access with screens that pressure or trick them.
How to fix it
- Publish a privacy policy that covers the three points above, and link it in App Store Connect and in the app, for example in Settings and on the sign-up screen.
- Rewrite each purpose string as what you use it for and why, for example "Your camera is used to scan receipts so you don't have to type them."
- Check the app works when each permission is declined.
- Make sure your privacy policy, App Privacy answers in App Store Connect and actual SDKs all agree.
Common questions
- Does a privacy policy link on my website count?
- The guideline asks for a link in the App Store Connect metadata field and within the app in an easily accessible manner. A link only on your website isn't enough on its own.
- What's a purpose string?
- It's the explanation you set in Info.plist for each permission, such as NSCameraUsageDescription, shown in the system alert. Apple wants it to clearly describe your use of the data.
Get your own rejection explained
Paste the message from App Store Connect or Play Console. Free, no account, about ten seconds.
Related guides
- Guideline 5.1.2(i): Data Use and Sharing (tracking, ATT, third-party AI)
- Guideline 5.1.1(v): Account sign-in and deletion
- ITMS-91053: Missing API declaration (privacy manifest)
Apple decides every review. These guides explain what the guidelines say and what usually helps. They can't promise an approval.
Sources: App Review Guidelines (Apple)