System logs
Blocked: apps can read only their own logs.
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
| Android | iPhone | |
|---|---|---|
| Status | Removed | Not supported |
| First version | Android 4.1 (API 16) | Not available |
| Permission or entitlement | READ_LOGS (signature, development) | none |
| Protection level | signature | not-exposed |
| How access is granted | not-exposed | not-exposed |
| 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 | None listed |
| API | logcat; only the caller's own logs | OSLogStore only for own process (iOS 15) |
| Notes | Own app logs only | Own 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
| Type | Example | Apps |
|---|---|---|
| developer | A developer wanted to read the full phone log to debug a crash, and now uses their own logging. | Sentry, Firebase Crashlytics |
| security | A security app wanted to watch other apps' logs for malware. | None named |
| ads | An ad SDK wanted to read other apps' logs for hints and is blocked. | None named |
| games | A game studio wanted device logs for cheating checks and uses its own server checks. | None named |
| analytics | A measurement SDK wanted system events and uses its own events. | None named |
| enterprise | A device fleet tool wanted logs to diagnose faults and uses MDM channels. | None named |
| health | A 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
| Score | Value | Meaning |
|---|---|---|
| Sensitivity | 4 of 5 | How revealing the data is |
| Utility | 1 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
- 2012-07, Android 4.1 (API 16): READ_LOGS limited to own logs
Sources
How well checked: Based on official documentation.