Guideline 5.1.1 Rejections: Privacy, Permissions & AI Data Consent

App ReviewUPDATED 2026-08

Quick answer: 5.1.1 rejections come from collecting data without proper in-app consent or from blocking users who deny a permission. If your app sends photos, text or audio to an AI service, Apple expects an explicit consent screen — inside the app, before the data flows — naming what's collected and who processes it. A privacy policy URL alone is not consent.

The two failure modes

Mode one: consent theater. The app has a privacy policy somewhere, but the actual flow uploads a user's selfie to a third-party AI API without an in-app explanation. Apple increasingly rejects this pattern explicitly for AI-powered apps: the consent must be contextual and precede the upload.

Mode two: permission walls. The app requests camera/photos/location, the user declines, and the app becomes unusable or nags them to Settings. Apple expects a functional alternative path — for example, letting users pick a photo instead of requiring live camera, or manual entry instead of location.

A consent flow that passes

Before the first sensitive action: a plain-language screen — 'Your photo is sent to [provider] to generate your result. It isn't stored after processing.' — with an explicit accept button, plus the same disclosure in your privacy policy and accurate Privacy Nutrition Labels in App Store Connect. Mismatches between what the labels claim and what network traffic shows are themselves a rejection trigger.

Reviews are the rawest product feedback there is. Read any app's in 20 seconds.

Analyze an app →

More from the library

Why Is My App Stuck in Review? Timelines & What Actually Helps The Most Common App Store Rejection Reasons (and How to Fix Each)Guideline 4.3(b) Rejections How to Respond to Negative App Store Reviews (Templates That Work)