Skip to Content
Platform.Ontology

App and device identifiers

IDs the OS gives an app to recognize an install or a vendor's apps.

Gets silentlyDevice detailsIdentifiersAndroid and iPhoneWhen the app opensWhile you use itAfter you uninstall

In one line

Can use IDs your phone gives it to recognize this install or the developer's apps

IDs the OS gives an app to recognize an install or a vendor's apps.

Lets a company recognize the same install across sessions and link sessions without login. Some survive reinstall (iOS Keychain, backups).

What it can and can't do

What the user does: Nothing. The app can get them as soon as it opens

It can

  • Use Android ID to recognize you across the same developer's apps
  • Use the iPhone vendor ID to recognize you across the same developer's apps
  • Use a Firebase install ID to tell one install from another
  • Save an ID in the iPhone Keychain so it can stay after a reinstall

It cannot

  • Match you across different developers with these IDs
  • Show your name or phone number
  • Stay the same after a factory reset on Android
  • Be turned off with a prompt; the person can only reset or delete apps

How it differs between platforms: Android ID and iPhone vendor ID work the same way but have different reset rules.

On Android and iPhone

AndroidiPhone
StatusSupportedSupported
First versionAndroid 8.0 (API 26)iOS 6
Permission or entitlementNot listedNot listed
Protection levelnonenone
How access is grantednonenone
What the user seesNo promptNo prompt
How long it lastsANDROID_ID per app signing key; resets on factory resetIDFV persists across apps of one vendor; resets when all vendor apps are removed
How to take it backClear dataReinstall all vendor apps
Store policyPlay: Device ID policyApp Review 5.1.2
APISettings.Secure.ANDROID_ID, FirebaseInstallationsUIDevice.identifierForVendor, Keychain
NotesNoneNone

Data you get

What comes back: Identifier
Shape: string
How often: stable

FieldTypeUnitRangePrecision
idstring64 or 128 bitn/an/a

Technical limits

  • Hardware IDs are not available to normal apps

The story

What it is

IDs the phone gives an app so it can recognize an install or a company's apps.

For you

You never see them. They quietly let an app know it is the same phone as yesterday. Some reset when you reinstall, some are shared across one company's apps, and some are hidden if you refuse tracking.

For makers

Makers need an ID to save progress, count users and fight fraud. Ad firms want a stable ID to link activity. The phone makers now limit which IDs apps can read and when.

Where you see it

TypeExampleApps
gamesA game saves your progress against an install ID so a quick restart does not lose your level.None named
adsAn ad network counts how many different phones saw an ad, so one person is not counted ten times.None named
analyticsA product team counts daily users and joins crash logs to one install without asking for a login.None named
securityA bank links a new login to a device ID it has seen before and skips extra checks.None named
shoppingA store gives a welcome coupon once per install ID.None named
messagingA chat app uses an install ID as the address for push notifications.None named

Risks

  • Lets apps recognize you silently
  • Some IDs outlive a reinstall

Android and iPhone in short

  • Android: Includes the resettable ad ID, the per signing key Android ID and app set IDs.
  • iPhone: Includes the vendor ID and the ad ID, which needs your tracking permission.

What the platform says

  • Google: User data IDs. Developer guide: Android's guidance on which IDs to use, which reset, and which need consent.
  • Apple: identifierForVendor. Developer guide: an ID shared by one vendor's apps on a device, reset when they are all deleted.

Good uses and abuse

Legitimate uses

  • Session continuity
  • Fraud checks

Known abuse

  • Cross-app linkage

Scores

ScoreValueMeaning
Sensitivity3 of 5How revealing the data is
Utility4 of 5How useful it is to honest apps
Friction0 of 5How much the user has to do
Fingerprint bits20Rough identifying entropy, when known

A real example: LinkedIn

Policy 1.5: LinkedIn receives a device identifier and features. Play Data safety lists Device or other IDs; Apple label lists Device ID and User ID as Linked to You.

History

  • 2013-09, iPhone iOS 7: UDID and MAC address blocked; IDFV introduced
  • 2017-08, Android 8.0 (API 26): ANDROID_ID scoped per app signing key

Same idea on the web

Sources

How well checked: Checked against real behavior.

On this page