Rejection guides / Guideline 5.1.1(i): Privacy policy and permission strings

Updated November 2026 · Appflight

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.

Explain my rejection

What the privacy policy must cover

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))

How to fix it

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.

Explain my rejection

Related guides

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)