Trust Center

Trust is the product. Here is how DeviceBound earns it.

Device-Bound Cryptographic Verification

Every DeviceBound verification is bound to a specific physical device. The device generates a cryptographic key pair during verification; completing the ceremony proves the person holds that trusted device, right now. There is no password to share, guess, or steal.

Secure Audit Trail

Each verification is recorded with a unique DeviceBound ID, precise timestamps, and its final outcome. Audit records are immutable and available to support disputes, compliance, and investigations.

Encryption in Transit

All communication with DeviceBound uses HTTPS/TLS encryption. See the Security page for the full picture.

Device Authentication

Verifications require the device's built-in authenticator: Face ID, Touch ID, Windows Hello, or the device PIN. Authentication happens locally on the device. DeviceBound never receives biometric data.

Fraud Prevention

One-time verification links, single-use cryptographic challenges, automatic expiration, and payment-gated requests make verifications expensive to fake and impossible to replay.

Data Retention

We retain information only as long as necessary to provide the service, comply with legal obligations, resolve disputes, and maintain audit records. Details are in the Privacy Policy.

Privacy Commitment

DeviceBound stores verification status, not secrets. We do not collect or store biometric data, and mobile information is never shared with third parties or affiliates for marketing purposes.

Responsible Disclosure

Security researchers are welcome. Report vulnerabilities to support@devicebound.us and we will investigate promptly.

System Status

All systems operational. A public status page is coming soon; for urgent issues contact support@devicebound.us.