Skip to Content
Platform.Ontology

Block Store and credential restore

Google Play services can hold a small token that follows a person to a new phone or a reinstall.

Works without askingHome screen and system linksBackupAndroid and iPhoneAfter you uninstallWhen you are signed in

In one line

Can keep a small sign in token that follows you to a new Android phone

Google Play services can hold a small token that follows a person to a new phone or a reinstall.

Lets an app restore sign-in without a password. The data is end to end encrypted when a screen lock is set and can survive a reinstall; iOS has no direct equivalent apart from iCloud Keychain.

What it can and can't do

What the user does: You set up a new phone or reinstall the app and approve the restore

It can

  • Store a few small items through Google Play services
  • Restore them when you set up a new phone
  • Let you stay signed in after a reinstall

It cannot

  • Store large files; only small pieces of data fit
  • Work on iPhone, which has no Block Store
  • Restore without your device setup prompt

How it differs between platforms: Block Store is Android only. On iPhone the closest tools are iCloud Keychain and Keychain persistence.

On Android and iPhone

AndroidiPhone
StatusSupportedNot supported
First versionAndroid 6.0 (API 23)Not available
Permission or entitlementNone (Play services)Not listed
Protection levelnonenone
How access is grantednonenot-exposed
What the user seesRestore prompt on new device setupNone
How long it lastsStored by Play services; survives reinstall when end to end backup is onn/a
How to take it backClear via Play services or device wipeNot listed
Store policyNone listedNone listed
APIGoogle Play services Block Store API (BlockstoreClient)Not listed
NotesSmall byte arrays only; limit about 16 entries of about 4 KB each (unverified)Closest iOS analogs are iCloud Keychain and Keychain persistence

Data you get

What comes back: Restore token
Shape: binary
How often: On demand

FieldTypeUnitRangePrecision
max_bytes_per_itemintegerbinaryabout 4096 (unverified)approx

Technical limits

  • Needs Play services
  • Needs end to end encryption for cross device

The story

What it is

A tiny token Google keeps that follows you to a new phone so an app can sign you in.

For you

You move to a new phone and the app is already signed in. You did nothing. It feels like magic, and it needs a screen lock.

For makers

Makers keep users signed in across a phone change and avoid the cost of a new login. It can also keep an identity alive across reinstalls.

Where you see it

TypeExampleApps
bankingA bank app restores your device link so you only confirm with a fingerprint.None named
gamesA game keeps your account on a new phone with no login.None named
mediaA streaming app signs you in after you restore.Netflix
shoppingA store app keeps you signed in after switching phones.None named
analyticsA team sees one person move devices without losing the thread.None named
adsA marketer keeps a stable ID across reinstalls.None named
securityA fraud tool links an old device to the new one to spot account takeover.None named

Risks

  • Persistent identity across installs
  • Hard to see or clear

Android and iPhone in short

  • Android: Holds small byte arrays. Restore happens during new phone setup.
  • iPhone: iOS has no direct match. iCloud Keychain and the keychain come closest.

What the platform says

  • Google: Block Store. Google pitches Block Store as a way to restore sign in on a new device without extra steps.

Good uses and abuse

Legitimate uses

  • Silent sign in after restore

Known abuse

  • Persistent identity across installs

Scores

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

History

  • 2022-05, Android Play services: Block Store API launched

Same idea on the web

Sources

How well checked: Inferred from related behavior.

On this page