App Store rejection: Guideline 5.1.1 data collection, and how to fix it
What App Store Guideline 5.1.1 says
Apple's Guideline 5.1.1 (Data Collection and Storage) has several parts.
5.1.1(i) Privacy Policies requires a privacy policy link in your App Store Connect metadata and within the app, in an easily accessible place. The policy must identify what data the app collects, how it collects it, and all uses; confirm that any third party you share data with provides equal protection; and explain data retention and deletion and how a user can revoke consent or request deletion.
5.1.1(ii) Permission requires user consent for collecting user or usage data, even if anonymous, and an easy way to withdraw consent. Apple says to ensure your purpose strings clearly and completely describe your use of the data.
5.1.1(iii) Data Minimization says apps should only request access to data relevant to the core functionality and only collect what is required.
5.1.1(iv) Access says apps must respect the user's permission settings and not trick or force people into consenting to unnecessary data access.
5.1.1(v) Account Sign-In says if your app supports account creation, you must also offer account deletion within the app, and apps without significant account-based features should let people use them without a login.
The full text is on the App Store Review Guidelines page.
Why apps get rejected under 5.1.1
Common triggers:
- A missing privacy policy, a privacy policy URL that does not load, or a policy that does not actually describe the data the app collects.
- An app that supports account creation but has no in-app way to delete the account.
- Vague permission purpose strings such as "This app needs access to your camera" with no real reason.
- Requesting permissions the app does not need for its core features, such as contacts access in an app that has no contacts feature.
- Forcing a login for an app whose core features are not account-based.
Apple frames 5.1.1 around user control over data, so the reviewer checks whether you collect only what you need, explain it honestly, and let users opt out and delete.
How to fix it
- Publish a real privacy policy. Write one that lists the data you collect, how, and why, covers third-party SDKs and sharing, and explains retention, deletion, and revoking consent. Link it in App Store Connect and inside the app.
- Add account deletion. If users can create an account, add a clear in-app path to delete it that actually removes the account and its data. Place it where a user can find it.
- Write honest purpose strings. For every permission, write an Info.plist usage string that states specifically why the app needs it and how the data is used.
- Minimize what you request. Remove any permission the app does not need. Where possible, use the system photo picker or a share sheet instead of full library access.
- Make login optional when it can be. If the core features are not account-based, let people use the app without signing in.
Submitted is not approved. A resubmission goes back through review, and the reviewer will check the privacy policy, the prompts, and the deletion path again.
How AppFlight helps
AppFlight wires backends through one-click integrations such as Supabase for database and auth, with public keys shipping in the app and backend secrets kept server-side in your own Supabase, which keeps credential handling on the right side of the line. When Apple returns a 5.1.1 rejection, AppFlight reads the rejection reason, works on the fix, and resubmits, for example adjusting permission prompts, surfacing account deletion, or scoping data requests in the generated Swift. You are still responsible for writing and hosting an accurate privacy policy and for what your app actually collects. AppFlight does not guarantee approval. Apple reviews every app and every resubmission.
FAQ
What does App Store Guideline 5.1.1 mean?
It governs how apps collect, use, and store user data. It requires a clear privacy policy, user consent for data collection, data minimization, honest permission purpose strings, and in-app account deletion if your app supports account creation.
Why was my app rejected for missing account deletion?
Under 5.1.1(v), if your app supports account creation it must also offer account deletion from within the app. A rejection usually means the reviewer could create an account but found no way to delete it inside the app.
Do I need a privacy policy to pass 5.1.1?
Yes. Apple requires a privacy policy link in your App Store Connect metadata and inside the app. It must identify what data you collect, how, and why, cover third-party sharing, and explain data retention, deletion, and how to revoke consent.