Security
What happens to an ID after it is sent.
How photos, workspaces, results and people are protected across Verify, Access and Shield.
Photo storage
Photos are encrypted with AES-GCM before they are stored, with the check they belong to bound into the encryption.
Separate workspaces
Every API key belongs to one workspace and carries its own permissions, and every lookup stays inside that workspace. The capture page on the person's phone uses a short-lived token for that one check, never a workspace key.
Signed results
Every webhook carries an HMAC-SHA256 signature over its timestamp and its exact body. Your system confirms the signature and the timestamp before it acts on the result.
Clear answers when evidence is missing
A check that could not be completed is treated as not proven. Your policy decides whether that means Caution or Fail.
The person agrees first
Every check starts with the person's own link and a signed authorization. Record sources that are not connected show as not connected, and never pass.
Access at the door
A person agrees to face-based entry when they enroll. At the door, a face only opens the way for someone holding a pass for that place. Staff can admit a person by hand, and the reason is recorded.
Shield evidence records
With Shield, every completed Verify is kept as a tamper-evident record linked to its order, with the authorization and a log of everyone who opened it. When a chargeback arrives, the dispute package and PDF are ready to send.
Built with care, described plainly.
This page describes how the product is built. It is not a certification, and Identity Entry makes no claim of SOC 2, ISO, regulatory compliance, uptime, accuracy or speed. Independent assurance for a deployment is gathered separately.
Ask about your deploymentStart checking IDs with confidence.
Run a check on yourself first and see exactly what your customers will see.
Get started