Keychain and Block Store persistence across reinstall
A stored ID that survives uninstall, so a reinstalled app recognizes the person.
In one line
Can recognize you after a reinstall using an ID that stays behind on your phone
A stored ID that survives uninstall, so a reinstalled app recognizes the person.
iOS Keychain entries remain after the app is deleted. Android needs Block Store or Auto Backup. Used for fraud and abuse limits, and sometimes tracking.
What it can and can't do
What the user does: Nothing. The app saves it quietly the first time you use it
It can
- Keep an ID in the iPhone Keychain that stays after you delete the app
- Keep an ID in Android Block Store or Auto Backup that may come back
- Sync the saved item to a new device if iCloud Keychain or Google backup is on
- Tell the app you are a returning user
It cannot
- Share the ID with apps from other developers on iPhone
- Survive on Android without backup or Block Store; a normal uninstall clears app data
- Stay on a phone after a full wipe or reset
- Come back on Android if you turn off backup
How it differs between platforms: iPhone keeps Keychain items after uninstall by default. Android clears them unless backup or Block Store is used.
On Android and iPhone
| Android | iPhone | |
|---|---|---|
| Status | Supported | Supported |
| First version | Not available | Not available |
| Permission or entitlement | Not listed | Not listed |
| Protection level | none | none |
| How access is granted | none | none |
| 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 | Auto Backup (6.0), Block Store (Play services 2022), AccountManager | SecItemAdd with kSecAttrAccessible, Keychain Services |
| Notes | Cleared on uninstall otherwise; backups may restore app data on a new device. | Items stay after uninstall; iCloud Keychain sync is optional. Not shared across different teams. |
Data you get
What comes back: Opaque value
Shape: string
How often: persistent
No individual data fields. The signal is the access itself.
Technical limits
- Apple: only same team; Android: Block Store is per app
- Privacy label must declare any identifier collected
The story
What it is
A stored ID that stays after you delete and reinstall the app.
For you
You delete an app to start fresh, reinstall it, and it says Welcome back. You will not see the stored ID that told it who you were, and clearing it is not simple.
For makers
Makers use it to stop abuse like repeat free trials, and to keep a person signed in after a reset. Ad and analytics firms also use it to keep a stable ID when the ad ID is blocked.
Where you see it
| Type | Example | Apps |
|---|---|---|
| games | A game recognizes a banned cheater who deleted the game and reinstalled, and blocks them again. | None named |
| media | A streaming app limits a free trial to once per phone, even after you reinstall. | None named |
| shopping | A store sees your welcome coupon was already used on this phone and does not give it again. | None named |
| banking | A bank app keeps your device trusted after an update, without a new text code. | None named |
| dating | A dating app spots someone returning after a ban and stops the new account. | None named |
| ads | An ad partner joins your pre and post reinstall activity, so attribution stays accurate. | None named |
Risks
- Survives a clean start
- Hard for you to clear
Android and iPhone in short
- Android: Needs Block Store or Auto Backup. Data can also move to a new phone.
- iPhone: Keychain items often remain after the app is deleted, unless the developer clears them.
What the platform says
- Google: Block Store. Developer pitch: keep sign in data across app reinstalls and new devices, with no extra login steps.
Good uses and abuse
Legitimate uses
- Fraud limits on trials
- Restore session
Known abuse
- Re-linking after a person reset
Scores
| Score | Value | Meaning |
|---|---|---|
| Sensitivity | 3 of 5 | How revealing the data is |
| Utility | 4 of 5 | How useful it is to honest apps |
| Friction | 0 of 5 | How much the user has to do |
| Fingerprint bits | Not rated | Rough identifying entropy, when known |
History
- 2022-05, Android Play services: Block Store API released for credentials and IDs
Related capabilities
Related
- Shared Keychain access groups and app groups. Can share saved secrets and files between apps from the same developer on iPhone
- IDFV and App Set ID (developer-scoped IDs). Can recognise your phone across one company's apps, but not other companies' apps
Sources
How well checked: Based on official documentation.