Skip to Content
Platform.Ontology

Required Reason APIs and privacy manifest

Apple requires apps to declare why they use 5 fingerprint-prone API groups, in a privacy manifest file.

Works without askingAds and install trackingPrivacy manifestsAndroid and iPhoneBefore you install

In one line

Can only use five fingerprint prone phone details with an approved reason on iPhone

Apple requires apps to declare why they use 5 fingerprint-prone API groups, in a privacy manifest file.

Apps must list approved reasons per group in PrivacyInfo.xcprivacy or App Store Connect rejects the upload. Reasons limit use; fingerprinting is banned even with consent.

What it can and can't do

What the user does: Nothing. Apple checks the reasons when the developer uploads the app

It can

  • Use file times, boot time, disk space, active keyboards and saved settings, with a listed reason
  • List the reasons in the privacy manifest file
  • Pass review when reasons match how the app works

It cannot

  • Use these details to fingerprint you, even with consent
  • Be uploaded to the App Store with missing reasons
  • Apply on Android; Play uses Data safety and reviews instead

How it differs between platforms: iPhone only (iOS 17 and later). Android has no required reason list.

On Android and iPhone

AndroidiPhone
StatusNot supportedBehind a flag
First versionNot availableiOS 17.0
Permission or entitlementnoneentitlement
Protection levelnot-exposedentitlement
How access is grantednot-exposednone
What the user seesNot listedNot listed
How long it lastsNot listedNot listed
How to take it backNot listedApp Review 5.1.2: fingerprinting banned
Store policyNone listedNone listed
APINo equivalent; Play data safety form is looser5 categories (file timestamp, boot time, disk space, active keyboards, user defaults) and 17 reason codes; enforced 2024-05-01
NotesPlay uses the Data safety section and policy reviews, not per-API reasonsNone

Data you get

What comes back: Manifest
Shape: object
How often: At upload

FieldTypeUnitRangePrecision
categoriesintegercount5exact
reason_codesintegercount17exact

Technical limits

  • Third-party SDKs need their own manifests

The story

What it is

The rule that iOS apps must declare why they use certain fingerprint prone APIs, in a privacy file.

For you

You do not see it. It is a rule that makes apps declare why they check things like how much disk space you have.

For makers

Apps must list approved reasons per group in PrivacyInfo.xcprivacy, or App Store Connect rejects the upload. Reasons limit use, and fingerprinting is never an approved reason.

Where you see it

TypeExampleApps
gamesA game states that it reads free space only to decide which art to download.Genshin Impact
adsAn ad SDK drops a check of boot time to avoid a rejection.AppLovin
analyticsAn analytics SDK says it uses uptime only for app speed numbers.Firebase
socialA photo app states it reads file dates only to sort a gallery.Instagram
securityApple reviewers compare declared reasons with real use.None named
developerA developer runs the privacy report in Xcode to find missing reasons.None named

Risks

  • Self reported
  • Reasons can be loosely stated

Android and iPhone in short

  • Android: Android has no equal. Policy and API limits handle it.
  • iPhone: Enforced when the build is uploaded.

What the platform says

Good uses and abuse

Legitimate uses

  • Compliance

Known abuse

  • None

Scores

ScoreValueMeaning
Sensitivity1 of 5How revealing the data is
Utility3 of 5How useful it is to honest apps
Friction3 of 5How much the user has to do
Fingerprint bitsNot ratedRough identifying entropy, when known

History

  • 2023-06, iPhone iOS 17: Privacy manifests and Required Reason APIs announced at WWDC
  • 2024-05, iPhone iOS 17.5: Missing reasons cause App Store rejection from 2024-05-01

Sources

How well checked: Checked against real behavior.

On this page