Security
What is actually true, with the gaps left visible.
Security pages are usually a wall of badges. This one describes how the thing is built, and says plainly where a claim would need a certificate we do not hold.
- 2processing regions
- Per sessionencryption keys
- 0biometric templates retained
Controls
The ones that matter to an integrator
- In transit
- TLS 1.3, HSTS
- At rest
- AES-256, keys per session
- Biometrics
- Not retained
- Access
- Least privilege, reviewed
- Secrets
- Never in the client
- Evidence
- Immutable once sealed
No downgrade path offered for any endpoint, including the capture upload.
A captured payload is scoped to the check it belongs to.
The template exists for the comparison and is discarded at the decision.
Access to production data is role-scoped and logged; the log is part of the evidence trail, not separate from it.
API keys are server-side; the client receives step tokens valid for fifteen minutes and one check.
A bundle cannot be edited after the fact, which is what makes it worth retrieving.