Guideline 5.1.1 is one of the most common reasons for App Store rejections, and it usually has nothing to do with your code. It is about one page: your privacy policy. This guide covers what Apple actually asks for and how to fix the rejection without guessing.
What Guideline 5.1.1(i) requires
The guideline's own wording is short. Every app must link to a privacy policy in two places:
- In App Store Connect, in the Privacy Policy URL field on the App Information page.
- Inside the app, "in an easily accessible manner", for example on your settings or about screen.
"Every app" includes apps that collect no data at all. A one-screen utility with no analytics still needs a privacy policy, and it can simply say that no data is collected.
The three things the policy must say
Apple asks that the policy "clearly and explicitly" covers:
- What data the app collects, how it collects it, and every use of that data. If you use Firebase Analytics, Crashlytics, AdMob or RevenueCat, the data those SDKs collect counts as your app's data.
- That third parties protect the data equally. Any analytics tool, ad network, SDK or related company that receives user data must provide the same protection your policy promises.
- How long you keep data, and how people can revoke consent or ask for deletion. Include a real contact method, such as an email address or a contact form.
A policy copied from another app, or a generic template that never mentions your SDKs, often fails on the first point.
Common reasons for a 5.1.1 rejection
- The Privacy Policy URL returns a 404, a "coming soon" page, or a login wall.
- The link exists in App Store Connect but not inside the app.
- The policy doesn't mention data that your App Privacy label declares (or the other way round).
- There is no way to request data deletion or to contact you.
- The policy is only available as a PDF download or an image.
How to fix it, step by step
- List what your app and its SDKs collect. Go through every SDK in your project; their documentation usually lists the data types.
- Update the policy so it covers the three points above, in plain language.
- Host it on a stable URL that loads without JavaScript, sign-in or region restrictions.
- Add the link inside the app (settings or about screen), then paste the same URL into App Store Connect.
- Make sure the policy and the App Privacy label agree. Reviewers compare them. Our guide to filling in the App Privacy label explains the label side.
- Reply in Resolution Center describing what you changed, and resubmit.
Related requirements you may hit at the same time
- Support URL (Guideline 1.5): must include "an easy way to contact you". See what Apple expects from your Support URL and Privacy Policy URL.
- Account deletion (Guideline 5.1.1(v)): if users can create an account, they must be able to delete it in the app. See the account deletion requirement.
- Privacy manifest: separate from your policy and your label. See privacy manifest vs App Privacy label.
Doing this with AppSubmitKit
AppSubmitKit's privacy questionnaire asks which SDKs you use and what data you collect, then publishes a privacy policy on a stable URL and gives you matching answers for the App Privacy section, so the two stay consistent. It is free for up to two apps. It is a drafting tool, not legal advice: review the text before you publish it.