Android ID (SSAID)
A 64-bit ID per app signing key and user on Android; changes on factory reset.
In one line
Can recognize your Android phone with a long ID, separate for each app maker
A 64-bit ID per app signing key and user on Android; changes on factory reset.
Gives a stable per-developer device ID with no prompt. Since Android 8 apps signed by different developers see different values.
What it can and can't do
What the user does: Nothing. Any Android app can ask for it with no prompt
It can
- Use a 16 character ID to tell your phone and user profile apart
- Keep recognizing you across restarts and app updates
- Link your activity across apps signed by the same developer
It cannot
- Match you across apps from different developers on Android 8 and newer
- Survive a factory reset; a new ID is made
- Exist on iPhone; the closest match is the vendor ID, which works differently
How it differs between platforms: Android only. iPhone has no Android ID; its closest match is the vendor ID.
On Android and iPhone
| Android | iPhone | |
|---|---|---|
| Status | Supported | Not supported |
| First version | Android 1.5 (API 3) | Not available |
| Permission or entitlement | Not listed | none |
| Protection level | none | not-exposed |
| How access is granted | none | not-exposed |
| What the user sees | Not listed | Not listed |
| How long it lasts | Until factory reset or signing key change | Not listed |
| How to take it back | Factory reset | Not listed |
| Store policy | Play: use the advertising ID for ads, not this | None listed |
| API | Settings.Secure.ANDROID_ID | No ANDROID_ID equivalent |
| Notes | 64-bit value as 16 hex characters; scoped to signing key, user and device since Android 8 | Closest analog is identifierForVendor (separate entry) |
Data you get
What comes back: 64-bit ID
Shape: string
How often: Static
| Field | Type | Unit | Range | Precision |
|---|---|---|---|---|
android_id | string | hex | 16 characters | 64 bits |
Technical limits
- Resets on factory reset
- Different value per signing key
The story
What it is
A long ID Android keeps for each developer's apps on one phone.
For you
You never see it and it asks nothing. It lets one company recognize your phone across its apps, and it changes only if you factory reset or the developer changes signing keys.
For makers
Gives developers a stable ID without any permission. It is used for saved accounts, fraud checks and tying installs together, though Google tells developers to prefer other IDs for ads.
Where you see it
| Type | Example | Apps |
|---|---|---|
| games | A game restores your progress on a re-installed copy of the game because it sees the same ID as before. | None named |
| security | A payments app counts how many accounts used one phone ID and blocks the tenth. | Google Pay |
| ads | An ad attribution tool uses it to tie an install to a click when the ad ID has been turned off. | None named |
| shopping | A coupon app makes sure a one time welcome offer is not redeemed again on the same phone. | None named |
| analytics | A product team counts unique devices over months without asking for a login. | None named |
| enterprise | A company device manager uses it to know which phone is which in its fleet. | None named |
Risks
- Stable fingerprint without consent
- Easy to join with other data
Android and iPhone in short
- Android: Per app signing key and user since Android 8, so different developers see different values.
- iPhone: iPhone has no SSAID; the closest is the vendor ID.
What the platform says
- Google: Android ID (SSAID). Developer guide: a 64 bit value that is unique per app signing key and user, and resets on factory reset.
Good uses and abuse
Legitimate uses
- Per-install analytics
- Fraud checks
Known abuse
- Cross-session tracking
Scores
| Score | Value | Meaning |
|---|---|---|
| Sensitivity | 3 of 5 | How revealing the data is |
| Utility | 3 of 5 | How useful it is to honest apps |
| Friction | 0 of 5 | How much the user has to do |
| Fingerprint bits | 64 | Rough identifying entropy, when known |
History
- 2017-08, Android 8.0 (API 26): ANDROID_ID scoped per signing key, user and device
Related capabilities
Related
- Identifier for Vendor (IDFV). Can recognize you across apps from the same developer on iPhone, but not other developers
- Advertising ID (IDFA and AAID). Can use a resettable ad ID, by default on Android and only after Allow on iPhone
Sources
How well checked: Checked against real behavior.