Security you don't have to take our word for.
Every verification session moves a government ID and a live selfie through our systems. Here's exactly what protects that data, and the math behind why it holds.
Your data is protected with AES-256 encryption, the same standard used by banks, governments, and every major cloud platform. It has a key space of 2²⁵⁶ possible combinations, and no practical attack against it has ever been published. That's not a marketing line; it's the accepted cryptographic baseline for data at rest and in transit.
Winning nine consecutive Powerball jackpots isn't "unlikely." Nobody in history has ever won even two in a row. That's roughly the company this encryption keeps. So take a breath: the part of this that's math isn't the part you need to worry about.
It's not one lock. It's four.
Encryption is the core, but it's not the only thing standing between your users' data and anyone who shouldn't see it.
Encryption at rest
Document images and personal data are encrypted the moment they're stored, never sitting anywhere in plain form.
Encryption in transit
Every request between your app, the hosted verification session, and our servers runs over TLS-encrypted connections.
Access controls
Verification data is scoped and permissioned. Access is logged, limited to what's needed, and never broad by default.
Data minimization
We keep what's needed for the verification report and compliance window. Nothing is retained "just in case."
Real trust starts with real privacy.
The practices behind the four commitments you've probably already seen, explained in full.
PII encrypted at rest
All personal data and document images are encrypted end-to-end with AES-256, always, whether they're mid-session or archived for a compliance window.
Programmatic deletion
Delete or redact user verification data on request at any time, by you or by the end user, through the API, not a support ticket.
Explicit consent flow
Users see exactly what's being captured and why before a session starts, and control exactly who their verified identity is shared with.
Data never sold
Unlike some identity networks, your users' data is never for sale, never brokered, and never repurposed for anything but the verification you asked for, full stop.
Single-use, short-lived sessions
Every verification session is single-use with a configurable expiry. There's no standing session left open for someone to hijack later.
Logged, auditable access
Every access to verification data is logged, so if a case ever gets questioned, there's a clear record of who saw what, and when.
Try to break it. We'll wait.
Security isn't bolted on after the fact here. It's the foundation everything else is built on.