Purpose strings and review rejection
Every iOS privacy prompt needs a written reason in the app, or the app is rejected or crashes.
In one line
Can't ask for iPhone access without a written reason shown in the prompt
Every iOS privacy prompt needs a written reason in the app, or the app is rejected or crashes.
The string is the only text the person sees about why. Apple reviewers reject vague ones, and a missing key crashes the app.
What it can and can't do
What the user does: Nothing. You see the reason when the app first asks for a camera, location or photos
It can
- Show you a sentence explaining why it wants an item, on iPhone
- Show its own explanation before an Android permission box
- Ask again later only if the reason text exists
It cannot
- Ask for a protected item on iPhone with no reason text; the app would close
- Pass App Store review with a vague reason such as We need this
- Change the reason text after release without a new app version
How it differs between platforms: iPhone requires the reason text in the app. Android has no system reason text; the developer fills a Data safety form in Play Console instead.
On Android and iPhone
| Android | iPhone | |
|---|---|---|
| Status | Supported | Supported |
| First version | Android 6.0 (API 23) | iOS 10 |
| Permission or entitlement | None; rationale UI optional | NS*UsageDescription keys in Info.plist |
| Protection level | none | prompt |
| How access is granted | none | prompt |
| What the user sees | Optional rationale shown by app | Prompt text comes from the key |
| How long it lasts | n/a | n/a |
| How to take it back | n/a | n/a |
| Store policy | Play: Data safety form and permission declarations | App Review 5.1.1 and 5.1.2 |
| API | shouldShowRequestPermissionRationale | Info.plist |
| Notes | No system purpose text; Data safety form is declared in Play Console | Missing key for a used API terminates the app; privacy manifests required from spring 2024 |
Data you get
What comes back: Info.plist string
Shape: none
How often: static
| Field | Type | Unit | Range | Precision |
|---|---|---|---|---|
keys | list | NS*UsageDescription | over 40 | Not listed |
Technical limits
- Apple may reject vague text
- Data safety form on Google Play
The story
What it is
A short written reason an iOS app must show before it asks for something private.
For you
The permission pop up has one sentence from the app explaining why it wants your camera, location or contacts. That sentence is often your only clue about what you are agreeing to.
For makers
Apple will reject an app if the reason is vague, and the app crashes if the reason is missing. Good makers write clear sentences that raise yes rates, because people say yes when they see a real benefit.
Where you see it
| Type | Example | Apps |
|---|---|---|
| maps | A rideshare app writes 'Your location is used to show nearby drivers' so the Allow button feels fair. | Uber, Lyft |
| social | A photo sharing app says 'We need camera access so you can post photos' and avoids a rejection. | Instagram, Snapchat |
| games | An AR game explains the camera use as 'to place creatures in your world', which lifts tap through on Allow. | Pokemon GO |
| dating | A dating app writes why it wants location before it shows matches nearby. | Hinge, Tinder |
| fitness | A running app writes 'We track your route while you run, even when the screen is off' for the background location prompt. | Strava, Nike Run Club |
| developer | An app review team bounces a build because the microphone string only said 'Microphone needed'. | None named |
Risks
- Vague wording tricks people
- Missing keys crash apps
Android and iPhone in short
- Android: Android has no required explanation text, though Google Play asks for a reason in review forms.
- iPhone: iOS requires one text key for each private feature and shows it in the system prompt.
What the platform says
- Apple: Purpose strings. Explain in plain words why your app needs access, so people can decide.
Good uses and abuse
Legitimate uses
- Informed consent
Known abuse
- Vague or misleading reasons
Scores
| Score | Value | Meaning |
|---|---|---|
| Sensitivity | 2 of 5 | How revealing the data is |
| Utility | 3 of 5 | How useful it is to honest apps |
| Friction | 1 of 5 | How much the user has to do |
| Fingerprint bits | Not rated | Rough identifying entropy, when known |
History
- 2016-09, iPhone iOS 10: Purpose strings required for privacy APIs, crash if missing
- 2024-05, iPhone iOS 17: Privacy manifests and required reason APIs enforced
Related capabilities
Related
- App Tracking Transparency. Can track you across other companies' apps and sites only if you tap Allow
Sources
How well checked: Based on official documentation.