Skip to Content
Platform.Ontology

System logs

Blocked: apps can read only their own logs.

Blocked for appsSystem controlSandboxAndroid and iPhoneWhen the app opensWhile you use it

In one line

Can't see other apps' logs, only its own

Blocked: apps can read only their own logs.

System logs once leaked other apps' data. Android 4.1 limited apps to their own logs; iOS gives a normal app only its own process logs.

What it can and can't do

What the user does: Nothing. The phone limits each app to its own logs

It can

  • See the app's own log messages
  • Check its own process logs on iPhone (iOS 15 and later)

It cannot

  • See logs from other apps
  • Use the old log permission as a normal app; it is for the system and developers only
  • Unlock them with a prompt

How it differs between platforms: Android keeps the old log permission for the system; iPhone offers only own process logs.

On Android and iPhone

AndroidiPhone
StatusRemovedNot supported
First versionAndroid 4.1 (API 16)Not available
Permission or entitlementREAD_LOGS (signature, development)none
Protection levelsignaturenot-exposed
How access is grantednot-exposednot-exposed
What the user seesNot listedNot listed
How long it lastsNot listedNot listed
How to take it backNot listedNot listed
Store policyNone listedNone listed
APIlogcat; only the caller's own logsOSLogStore only for own process (iOS 15)
NotesOwn app logs onlyOwn logs only

Data you get

What comes back: None
Shape: none
How often: N/A

No individual data fields. The signal is the access itself.

Technical limits

  • ADB required for system logs

The story

What it is

A block that stops apps from reading the phone's system logs, so they can only read their own.

For you

You never see it. Apps cannot read logs from other apps or the system, so your messages and the pages you open stay private.

For makers

System logs once leaked other apps' data, including tokens and messages. Apps wanted them to debug problems and spot fraud. Today they get only their own logs, or use official crash reports.

Where you see it

TypeExampleApps
developerA developer wanted to read the full phone log to debug a crash, and now uses their own logging.Sentry, Firebase Crashlytics
securityA security app wanted to watch other apps' logs for malware.None named
adsAn ad SDK wanted to read other apps' logs for hints and is blocked.None named
gamesA game studio wanted device logs for cheating checks and uses its own server checks.None named
analyticsA measurement SDK wanted system events and uses its own events.None named
enterpriseA device fleet tool wanted logs to diagnose faults and uses MDM channels.None named
healthA health app wanted to see what other apps were doing on the phone and cannot.None named

Risks

  • Leaks in the past
  • Debugging is harder
  • Carriers may see more

Android and iPhone in short

  • Android: Since Android 4.1 an app reads only its own logs, with a rare system exception.
  • iPhone: On iPhone an app sees only its own logs and there is no system log permission.

Good uses and abuse

Legitimate uses

  • None

Known abuse

  • Data leaks

Scores

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

  • 2012-07, Android 4.1 (API 16): READ_LOGS limited to own logs

Sources

How well checked: Based on official documentation.

On this page