Skip to Content
Platform.Ontology

Required Reason: system boot time

iOS uptime reads need 35F9.1, 8FFB.1 or 3D61.1.

Works without askingSpeed and timingPrivacy manifestsAndroid and iPhoneWhen the app opensWhile you use it

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

AndroidiPhone
StatusNot supportedBehind a flag
First versionNot availableiOS 17.0
Permission or entitlementnoneentitlement
Protection levelnoneentitlement
How access is grantednot-exposednone
What the user seesNot listedNot listed
How long it lastsNot listedNot listed
How to take it backNot listedApp Review: no off-device boot time
Store policyNone listedNone listed
APIAndroid has no gate: elapsedRealtime is open35F9.1 measure elapsed time in-app; 8FFB.1 absolute timestamps for in-app events; 3D61.1 optional bug report, shown to user
NotesAndroid analog: no reason neededNone

Data you get

What comes back: Reason codes
Shape: object
How often: At upload

FieldTypeUnitRangePrecision
reason_codeslistcode3 valuesexact

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

TypeExampleApps
gamesA game measures how long a level takes using the boot clock as a stopwatch.None named
videoA video app times buffering and playback using uptime.None named
analyticsAn analytics SDK stamps events with uptime and must declare it.None named
adsAn ad SDK could use boot time as part of a hidden device fingerprint, which is now restricted.None named
securityA fraud tool compares boot times to spot emulator farms.None named
developerA developer adds the right reason code to the privacy manifest before shipping.None named
fitnessA 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

Good uses and abuse

Legitimate uses

  • Timers

Known abuse

  • Cross-app ID until reboot

Scores

ScoreValueMeaning
Sensitivity1 of 5How revealing the data is
Utility2 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

  • 2024-05, iPhone iOS 17.x: Reason required to ship

Sources

How well checked: Checked against real behavior.

On this page