Other apps' data
Each app's files and memory are sealed from other apps on both platforms.
In one line
Can't open another app's files, messages or saved logins
Each app's files and memory are sealed from other apps on both platforms.
Sandboxing keeps one app from reading another's messages, tokens or files. Only user-picked files, shared groups or content providers cross the line.
What it can and can't do
What the user does: Nothing. It is blocked by the phone itself
It can
- See a file you pick through the file picker and share to it
- Share data through a group or shared area that the same company set up
- Receive what another app sends on purpose
It cannot
- See another app's messages, tokens or files on its own
- Browse another app's storage
- Break the barrier between apps without rooting or jailbreaking the phone
How it differs between platforms: Android shares through content providers or the file picker. iPhone shares through app groups or file pickers.
On Android and iPhone
| Android | iPhone | |
|---|---|---|
| Status | Not supported | Not supported |
| First version | Not available | Not available |
| Permission or entitlement | none | none |
| Protection level | not-exposed | 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 | App-private storage; scoped storage since Android 10, enforced 11 | App sandbox container; app groups only for the same team |
| Notes | Sharing needs content providers or the Storage Access Framework | Sharing needs app groups or file pickers |
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
- Same-signature or same-team exceptions
The story
What it is
Blocked: one app cannot read another app's files, messages or saved logins.
For you
You do not see anything. It is the reason a game cannot read your banking app or your messages. Only things you pick, like a photo, cross between apps.
For makers
Makers want to read other apps' data for ads, fraud scoring and rich features, but the system blocks it. They use approved bridges instead: share sheets, file pickers, shared app groups and sign in tokens.
Where you see it
| Type | Example | Apps |
|---|---|---|
| banking | A budgeting app asks you to log in through your bank's own sign in because it cannot reach the bank app's data. | YNAB, Monarch Money |
| messaging | A photo editor cannot read your WhatsApp chats. You must choose a picture to share. | Photoshop Express |
| games | A game cannot copy your save from a rival game. Players must use cloud saves or accounts. | Clash of Clans |
| ads | An ad SDK wanted other apps' ad history, but sandboxing forces it to use only its own data. | None named |
| security | Malware that infects one app cannot jump into a password manager's vault. | 1Password |
| productivity | Two apps from the same maker share data through a special shared container, with the person's knowledge. | Google Docs |
Risks
- Shared containers are a loophole
- Rooted phones break the wall
Android and iPhone in short
- Android: Android runs each app as its own user and added scoped storage in 10 and 11.
- iPhone: iOS keeps each app in a sealed container and only allows shared groups from one developer.
What the platform says
- Apple: App Sandbox on iOS. Each app runs in its own protected space so it cannot access other apps' data.
Good uses and abuse
Legitimate uses
- None
Known abuse
- Data theft
Scores
| Score | Value | Meaning |
|---|---|---|
| Sensitivity | 5 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
- 2020-09, Android 11 (API 30): Scoped storage enforced
Sources
How well checked: Based on official documentation.