Skip to Content
Platform.Ontology

App Attest and Play Integrity

Proves to a server that a request came from a genuine copy of the app on a genuine device.

Works without askingSign in and identityAttestationAndroid and iPhoneWhen the app opens

In one line

Can prove its requests come from the real app on a genuine phone

Proves to a server that a request came from a genuine copy of the app on a genuine device.

Anti fraud tool with a privacy angle: it is a device level key, not a user id.

What it can and can't do

What the user does: Nothing. It happens when you sign in, pay, or send something the app protects

It can

  • Get a signed statement that the app and device look genuine
  • Sign requests with a key held in the phone's secure chip (iPhone)
  • Check app license and device integrity (Android)
  • Reject requests from copies, emulators and tampered apps

It cannot

  • See who you are or other apps on the phone
  • Pass on a rooted or modified device at the stronger levels
  • Prove the phone is completely safe
  • Keep a flag beyond the 2 bits DeviceCheck offers

How it differs between platforms: iPhone uses App Attest and DeviceCheck. Android uses Play Integrity verdicts.

On Android and iPhone

AndroidiPhone
StatusSupportedSupported
First versionAndroid 4.4 (API 19)iOS 14
Permission or entitlementINTERNET (normal); Play Integrity API with Play servicescom.apple.developer.devicecheck.appattest-environment
Protection levelnormalentitlement
How access is grantedinstallentitlement
What the user seesNoneNone
How long it lastsPer tokenPer key
How to take it backn/an/a
Store policyPlay: Integrity API quotas (10,000 calls per day default)None listed
APIIntegrityManagerDCAppAttestService, DCDevice
NotesVerdicts for device, app and account licensingKey stays in the Secure Enclave; DeviceCheck stores 2 bits per device

Data you get

What comes back: Attestation or token
Shape: object
How often: per request

FieldTypeUnitRangePrecision
bitsintegerbits2 DeviceCheck bitsNot listed

Technical limits

  • Server must verify; clients cannot trust local result

The story

What it is

A server gets proof that a request came from the real app on a genuine phone.

For you

You do not see it. It sits behind a sign up, a purchase or a score upload and quietly says 'this looks real'. If your phone is jailbroken or rooted, an app may stop working.

For makers

Makers use it to block bots, cheats and cloned apps. It is a device level proof, not a person level ID, which helps with privacy. It still decides which phones are allowed and which are turned away.

Where you see it

TypeExampleApps
gamesA game server checks that a match result came from the real game, not a modified copy.None named
bankingA bank checks that a transfer request came from its real app before it moves any money.None named
shoppingA ticket seller blocks scripts that buy up concert seats by checking each purchase.Ticketmaster
socialA social app slows fake account creation by asking new devices to prove they are real.None named
adsAn ad platform removes fake installs by confirming the app and device were genuine.None named
developerAn AI app protects its paid server by only answering the true app.None named

Risks

  • Blocks rooted or jailbroken users
  • Device key can act as an identifier

Android and iPhone in short

  • Android: Android uses Play Integrity and gives a graded answer (basic, device, strong) about the device.
  • iPhone: iPhone uses App Attest, which is a hardware key per app install plus a signed statement from Apple.

What the platform says

Good uses and abuse

Legitimate uses

  • Fraud prevention

Known abuse

  • Blocking rooted users

Scores

ScoreValueMeaning
Sensitivity2 of 5How revealing the data is
Utility4 of 5How useful it is to honest apps
Friction1 of 5How much the user has to do
Fingerprint bitsNot ratedRough identifying entropy, when known

History

  • 2020-09, iPhone iOS 14: App Attest introduced
  • 2021-05, Android Play services: Play Integrity API launched

Same idea on the web

Sources

How well checked: Based on official documentation.

On this page