How DeviceBound Works
Live, device-bound verification in ten steps. If it's not green, don't proceed.
- 1A verification is requestedSomeone needs to verify a person: before a meeting, at a door, before sharing something sensitive.
- 2They enter the person's mobile numberThe mobile number identifies who is being verified. Nothing is sent until the request is created.
- 3DeviceBound sends a secure verification linkA one-time link is delivered by SMS or email, or shared in person as a QR code. It expires in 30 minutes.
- 4The recipient opens the link on their phoneNo app to install, no account to create. The link works in the browser they already have.
- 5The device authenticates them locallyFace ID, Touch ID, or the device PIN runs on the phone itself. Biometric data never leaves the device and is never sent to DeviceBound.
- 6A cryptographic key pair is generatedThe device creates a public/private key pair for this verification. The private key never leaves the user's device.
- 7The verification is cryptographically bound to that deviceCompleting the biometric ceremony signs a one-time challenge minted for this exact request. It cannot be replayed or transferred.
- 8DeviceBound stores only public verification informationStatus, timestamps, the DeviceBound ID, and the audit record. No secrets, no biometrics.
- 9The requester's screen turns greenIn real time, with no refresh. Red means not verified. Green means the holder of that mobile number completed a live biometric verification on their trusted device.
- 10Future checks confirm the same trusted deviceRepeat verifications can confirm both the record and the originating verified device.
Questions about the technology? See the Security page and Trust Center, or write to support@devicebound.us.
Powered by DEVICEBOUND™