Required Reason: system boot time
iOS uptime reads need 35F9.1, 8FFB.1 or 3D61.1.
In one line
Can check how long the phone has been on; iPhone needs an approved reason
iOS uptime reads need 35F9.1, 8FFB.1 or 3D61.1.
Boot timestamp is a stable fingerprint until reboot. 35F9.1 measures in-app intervals, 8FFB.1 stamps in-app events, 3D61.1 adds it to a user-submitted bug report.
What it can and can't do
What the user does: Nothing. It happens when the app measures time or logs an event
It can
- Measure time between actions inside the app (reason 35F9.1)
- Stamp events inside the app (reason 8FFB.1)
- Add it to a bug report that you send (reason 3D61.1)
- Check uptime with no gate on Android
It cannot
- Check it on iPhone without one of the three approved reasons
- Be used as a fingerprint on iPhone; it stays steady until a restart
- Use it on iPhone for ads or tracking
How it differs between platforms: iPhone requires one of three approved reasons; Android has no gate.
On Android and iPhone
| Android | iPhone | |
|---|---|---|
| Status | Not supported | Behind a flag |
| First version | Not available | iOS 17.0 |
| Permission or entitlement | none | entitlement |
| Protection level | none | entitlement |
| 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 | App Review: no off-device boot time |
| Store policy | None listed | None listed |
| API | Android has no gate: elapsedRealtime is open | 35F9.1 measure elapsed time in-app; 8FFB.1 absolute timestamps for in-app events; 3D61.1 optional bug report, shown to user |
| Notes | Android analog: no reason needed | None |
Data you get
What comes back: Reason codes
Shape: object
How often: At upload
| Field | Type | Unit | Range | Precision |
|---|---|---|---|---|
reason_codes | list | code | 3 values | exact |
Technical limits
- Boot time itself may not leave the device (except 3D61.1 reports)
The story
What it is
An iOS rule: apps must give a reason before reading how long the phone has been on.
For you
You never see it. Apps that read the phone's boot time must tell Apple why. This makes it harder for them to use a hidden number that stays the same until a restart.
For makers
The boot time can stitch together separate apps and sessions. Apple now limits its use to timers, in app event stamps and a bug report. Makers must describe their use in a privacy manifest or risk store rejection.
Where you see it
| Type | Example | Apps |
|---|---|---|
| games | A game measures how long a level takes using the boot clock as a stopwatch. | None named |
| video | A video app times buffering and playback using uptime. | None named |
| analytics | An analytics SDK stamps events with uptime and must declare it. | None named |
| ads | An ad SDK could use boot time as part of a hidden device fingerprint, which is now restricted. | None named |
| security | A fraud tool compares boot times to spot emulator farms. | None named |
| developer | A developer adds the right reason code to the privacy manifest before shipping. | None named |
| fitness | A run tracker times intervals with the system clock. | None named |
Risks
- Fingerprinting until reboot
- App Store rejection if undeclared
- Workarounds exist
Android and iPhone in short
- Android: Android has no gate for reading uptime, so no reason is needed.
- iPhone: iOS 17 added the rule with three allowed reasons, for in app intervals, in app event stamps and a user submitted bug report.
What the platform says
- Apple: Required reason APIs. Apple requires apps to declare why they use certain system timers and data in their privacy manifest.
Good uses and abuse
Legitimate uses
- Timers
Known abuse
- Cross-app ID until reboot
Scores
| Score | Value | Meaning |
|---|---|---|
| Sensitivity | 1 of 5 | How revealing the data is |
| Utility | 2 of 5 | How useful it is to honest apps |
| Friction | 3 of 5 | How much the user has to do |
| Fingerprint bits | Not rated | Rough identifying entropy, when known |
History
- 2024-05, iPhone iOS 17.x: Reason required to ship
Related capabilities
Related
- Required Reason APIs and privacy manifest. Can only use five fingerprint prone phone details with an approved reason on iPhone
- Boot time and uptime. Can see how long your phone has been on, and on Android its restart count
Sources
How well checked: Checked against real behavior.