Biometric availability and enrollment change
Reads if biometrics are enrolled; iOS also exposes a token that changes when enrollment changes.
In one line
Can check whether you set up fingerprint or face unlock, but not who you are
Reads if biometrics are enrolled; iOS also exposes a token that changes when enrollment changes.
Reveals device security setup. The iOS domain state changes when a new finger or face is added, so it is a weak device-state fingerprint.
What it can and can't do
What the user does: Nothing. It happens when the app decides whether to offer biometric sign in
It can
- Check if the phone has fingerprint or face unlock hardware
- Check if you have enrolled at least one fingerprint or face
- On iPhone, notice that your enrolled fingerprints or faces changed since last time
- Decide whether to show a biometric sign in button
It cannot
- See your fingerprint, face scan, or any biometric data
- Tell which finger or face is enrolled, or how many
- Unlock anything without the system scan prompt
How it differs between platforms: iPhone also gives a change marker when someone adds a new finger or face. Android gives only a status such as none enrolled or no hardware.
On Android and iPhone
| Android | iPhone | |
|---|---|---|
| Status | Supported | Supported |
| First version | Android 10 (API 29) | iOS 8.0 |
| Permission or entitlement | USE_BIOMETRIC (normal) | prompt |
| Protection level | normal | none |
| How access is granted | install | 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 | BiometricManager.canAuthenticate(BIOMETRIC_STRONG) | evaluatedPolicyDomainState changes when enrollment changes; Face ID needs usage string only when authenticating |
| Notes | Result codes: SUCCESS, NONE_ENROLLED, NO_HARDWARE, HW_UNAVAILABLE | None |
Data you get
What comes back: Availability
Shape: enum
How often: On check
| Field | Type | Unit | Range | Precision |
|---|---|---|---|---|
status | enum | None | SUCCESS, NONE_ENROLLED, NO_HARDWARE | 3 values |
Technical limits
- No template data exposed
The story
What it is
An app can quietly check whether you have set up a fingerprint or face unlock.
For you
You never see this check. You just notice that an app offers 'Use Face ID' or 'Use fingerprint' only when you have set one up. If you add a new face or finger, some apps may quietly ask you to log in again.
For makers
Makers need to know whether to show the biometric button or fall back to a password. Banks also watch for the enrollment change on iPhone, because a new face added right before a big transfer can mean someone else has the phone.
Where you see it
| Type | Example | Apps |
|---|---|---|
| banking | A bank app checks that you have fingerprint unlock set up, then offers a one tap login instead of a long password. | Chase, Revolut |
| security | A bank notices a new face was added to a phone an hour ago and asks for a full password and a code before it allows a large transfer. | None named |
| productivity | A password manager shows an 'Unlock with Face ID' toggle only when the phone can actually do it. | 1Password, Bitwarden |
| payments | A payments app skips the biometric prompt on a phone with no enrolled finger and asks for a PIN instead. | PayPal |
| enterprise | A work app checks that biometrics are set up so company data is protected by more than a 4 digit code. | Microsoft Intune |
| analytics | An ad or fraud tool adds the enrollment state to a quiet device profile, which helps tell one phone from another. | None named |
Risks
- Weak fingerprint bit
- Reveals security setup
Android and iPhone in short
- Android: Android only says whether strong biometrics are ready (yes, none enrolled, no hardware). It does not give a change token.
- iPhone: iPhone apps can read a token that changes whenever someone adds or removes a face or finger, which acts as a small device state signal.
What the platform says
- Google: BiometricManager. Android tells apps whether strong biometric sign in is ready on the device before offering it.
Good uses and abuse
Legitimate uses
- Offer biometric sign-in
Known abuse
- Fingerprint bit
Scores
| Score | Value | Meaning |
|---|---|---|
| Sensitivity | 2 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 | 2 | Rough identifying entropy, when known |
History
- 2019-09, Android 10 (API 29): BiometricManager.canAuthenticate for strong biometrics
Related capabilities
Related
- Device lock and passcode state. Can tell if your phone has a screen lock and whether it is locked now
Sources
How well checked: Based on official documentation.