Required reason APIs
Apple lists APIs that can be used to fingerprint a device and requires the app to state an approved reason.
In one line
Can't use fingerprint prone phone details on iPhone without an approved reason
Apple lists APIs that can be used to fingerprint a device and requires the app to state an approved reason.
Five categories: file timestamp, system boot time, disk space, active keyboards, and UserDefaults. An unapproved reason is a rejection, so fingerprinting uses are fenced in.
What it can and can't do
What the user does: Nothing. Apple checks the reasons when the developer submits the app
It can
- Use file times, boot time, free disk space, active keyboards and saved settings for approved reasons
- Include these reasons for third party tools as well
- Show the reasons in a file Apple checks
It cannot
- Use these details to fingerprint your phone, even if you said yes
- Use them for any reason not on Apple's list, or the app is rejected
- Skip the reasons after 1 May 2024 and still get through review
- Apply on Android; Play bans some IDs in other ways
How it differs between platforms: This is Apple only, in force since 1 May 2024. Android has no required reason list.
On Android and iPhone
| Android | iPhone | |
|---|---|---|
| Status | Not supported | Supported |
| First version | Not available | iOS 17.0 |
| Permission or entitlement | Not listed | Not listed |
| Protection level | none | none |
| How access is granted | not-exposed | none |
| What the user sees | Not listed | Not listed |
| How long it lasts | Not listed | Not listed |
| How to take it back | Not listed | Not listed |
| Store policy | None listed | Approved reason codes per API category (for example CA92.1 for UserDefaults app own data) |
| API | Not listed | NSPrivacyAccessedAPITypes in manifest |
| Notes | Android has no required reason list; Play bans some identifiers instead. | Enforced 1 May 2024. Covers third party SDK use too. Apple has said it targets fingerprint inputs. |
Data you get
What comes back: Approved reason codes
Shape: list
How often: static
| Field | Type | Unit | Range | Precision |
|---|---|---|---|---|
NSPrivacyAccessedAPIType | string | None | Not listed | Not listed |
NSPrivacyAccessedAPITypeReasons | list | None | Not listed | Not listed |
Technical limits
- Reasons must match real use
- No cross-app tracking use allowed
The story
What it is
Apple's list of device clues that need a stated reason because they can fingerprint a phone.
For you
You do not see it. It means apps cannot quietly check things like how long your phone has been on and use that to follow you around.
For makers
The five groups are file timestamps, boot time, disk space, active keyboards and UserDefaults. Makers must pick an allowed reason, or Apple rejects the upload, which kills most casual fingerprinting.
Where you see it
| Type | Example | Apps |
|---|---|---|
| games | A game reads free disk space to decide whether to download high resolution art, and states that reason. | Genshin Impact |
| ads | An ad SDK that used boot time as part of an ID must stop or state a legitimate reason. | AppLovin, Unity Ads |
| analytics | An analytics SDK reads the system uptime to measure app launch speed only. | Firebase |
| security | A fraud tool lists the exact use of each API so Apple can check it against abuse. | None named |
| social | A photo app reads file creation dates to sort a gallery. | |
| developer | A developer finds an old library using UserDefaults for tracking and swaps it out. | None named |
Risks
- Reasons are self reported
- Workarounds keep appearing
Android and iPhone in short
- Android: Android has no direct counterpart. Google limits fingerprinting through policy and API changes.
- iPhone: Enforced when the app is uploaded to App Store Connect.
What the platform says
- Apple: Describing use of required reason API. Apps must state an approved reason for using certain APIs that could identify a device.
Good uses and abuse
Legitimate uses
- Limits covert fingerprinting
Known abuse
- Reason shopping
Scores
| Score | Value | Meaning |
|---|---|---|
| Sensitivity | 3 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
- 2024-05, iPhone App Store: Enforcement on 1 May 2024
Related capabilities
Related
- Privacy manifests (PrivacyInfo.xcprivacy). Can list what the app and its add on tools collect, in a file Apple checks
- Device and SDK fingerprinting. Can guess who you are by combining small facts about your phone, with no prompt
Same idea on the web
- Composite fingerprint (FingerprintJS, CreepJS). Can combine many device traits into one visitor ID that survives cleared cookies
Sources
How well checked: Based on official documentation.