Device biometrics vs VULTid
Why a local biometric success and verification of an established human identity serve different purposes.
Device biometrics are useful for protecting a phone or releasing a credential held on it. Their result has a specific meaning: the device accepted its local authentication requirements. That result alone does not tell an outside organization which government-verified person is using the device or what external action they approved.
What a device check establishes
A phone compares the presented face or fingerprint with its locally enrolled data. An application receives an authentication outcome, not the biometric itself. The surrounding application may add other controls, but the local check by itself is tied to the device's enrollment and recovery rules.
Device authentication can therefore be a strong part of an account flow without independently establishing the person's legal identity to the organization. This distinction does not imply that device biometrics are insecure or that every device permits the same recovery paths.
What the VULTid model adds
VULTid starts with identity evidence: a government-issued document, a live face match, and a liveness check at enrollment. At a protected interaction, the model calls for fresh liveness and server-side comparison against that established identity's protected template. The device captures the interaction; its locally enrolled biometric is not the identity reference for that comparison.
When approval is required, Event-and-Identity-Bound Authorization adds the exact action and the person's explicit decision. A biometric match on its own is not an approval.
Compare the questions
| Question | Local device biometric | VULTid model |
|---|---|---|
| What is checked? | A factor enrolled on that device. | The live participant against an established verified identity. |
| Where does comparison happen? | On the local device. | Server-side against the established identity's template. |
| What does success mean? | Local authentication requirements were met. | The person linked to the identity is present for the protected interaction. |
| Does it inherently approve an external action? | No. | No; explicit event approval is a separate step. |
This is a condensed comparison of the two models. It does not cover storage or encryption; see Data handling in the Capabilities overview.
Read What is a verified human? for the enrollment and re-verification concepts.