Rejection Decoder
Home / Guidelines / 5.1.1

Guideline 5.1.1 rejection: privacy (data collection and storage)

What it means, why it happens, and how developers get through it.

Subject line you may see: Guideline 5.1.1 - Legal - Privacy - Data Collection and Storage

In one line: Privacy policy, permission purpose strings, access scope, forced consent, or account deletion.
Usual next move: Fix, new build, then replySomething in the binary has to change. Fix it, bump the build, resubmit, and reply with what changed and how to verify.Based on how this guideline is usually resolved, not a prediction for your app.
Paste your rejection to check
On this page: CausesFixReplyReal casesQuestions

Common real causes

How to fix it

  1. Rewrite purpose strings to name the feature
  2. Add in-app account deletion
  3. Use the system photo picker instead of full library access
  4. Add privacy policy URL in App Store Connect and in the app

What to put in your reply

Thank them and name Guideline 5.1.1.
Say exactly what changed, and in which version and build.
Give a numbered path the reviewer can follow.
Attach proof: screenshots or a screen recording.

The full fill-in-the-blanks reply for 5.1.1 is in the Rescue Kit.

Real cases: others who got 5.1.1

No public cases logged yet.

Questions developers ask about 5.1.1

What does a Guideline 5.1.1 rejection mean?

Privacy policy, permission purpose strings, access scope, forced consent, or account deletion.

Why do apps get rejected under Guideline 5.1.1?

The most common real causes: vague purpose strings like 'needs camera access'; no in-app account deletion; forced login for an app with no account features; missing privacy policy link.

How do I fix a Guideline 5.1.1 rejection?

1. Rewrite purpose strings to name the feature. 2. Add in-app account deletion. 3. Use the system photo picker instead of full library access. 4. Add privacy policy URL in App Store Connect and in the app.

Do I need a new build for Guideline 5.1.1?

Fix, new build, then reply. Something in the binary has to change. Fix it, bump the build, resubmit, and reply with what changed and how to verify. This is how the guideline is usually resolved, not a prediction for your app.

How should I reply to App Review about Guideline 5.1.1?

Reply in App Store Connect. Thank the reviewer and name Guideline 5.1.1, say exactly what changed and in which version and build, give a numbered path the reviewer can follow, and attach proof such as screenshots or a screen recording.

Stuck on 5.1.1?

Do it yourself, faster

App Store Rejection Rescue Kit: the full decoder, 12 reply templates, Notes for Review templates, and a 60-point preflight checklist.

Get the kit, $12

Have it written for you

Send your rejection, get a reply drafted for your exact case. Kit buyers get $10 off.

AI-assisted, built on Apple's App Review Guidelines. Not a guarantee of approval. If we do not deliver within 24 hours, you get a full refund.

Reply service, $29

Related rejections

5.1.2 Data use, sharing, tracking, third-party AI2.1(a) App Completeness2.1(b) In-app purchases not found2.5.2 Downloading or executing code

Source: Apple's App Review Guidelines, section 5.1.1, as revised October 16, 2026. Last checked . Always read the current official text. How we write these guides.