NIST FRTE since 2021
Evaluated under Seventh Sense's own name since 2021. The report card lists the evaluated algorithm, track and dates.
Trust centerTHE EVIDENCE / OPEN TO SCRUTINY
Trust starts with a person.
Verify faces without requiring a face-image or biometric-template database. Here is exactly what each product keeps, how we answer seven questions every biometric vendor should face, and the evidence you can check before you talk to us.
01Data accounting
What each product retains.
Each SenseCrypt product keeps different records. This table is the reference the rest of the site links to: what is kept and where, what is never kept, and the limits that apply.
| Product | Kept, and where | Never kept | Lifecycle and scope |
|---|---|---|---|
| SenseCrypt IdPLaunched |
|
| Each successful face ceremony spends the current face token and stores its replacement. The licensed on-premises webcam method processes captures inside the customer deployment, on secure terminals, because unsecured terminals expose webcam capture to injection attacks. |
| SenseCrypt eIDAvailable |
|
| A prepared verifier checks the credential and live holder locally using trusted issuer material. Offline revocation assurance depends on the verifier's last update. Revoking a credential does not delete personal data held elsewhere. |
| SenseCrypt PKIAvailable |
|
| Private keys exist only in process memory during face sign or face decapsulate and are never stored. Public keys, signatures and decapsulated shared secrets go directly to the relying party's endpoint. The IdP brokers the ceremony without receiving those results. |
| SenseCrypt ZKPDesign partnerships |
|
| Presentations are unlinkable by default; optional consented linkage is a separate configuration, and disclosed attributes can still link. |
| SenseCrypt KYAEarly access |
|
| This is the proposed KYA architecture. Early access delivers a record of who authorized an agent, its scope and its expiry, which your applications enforce; the per-action signing chain is designed to work this way. The consuming application enforces each agent's authorized scope. |
| Lume AuthAvailable |
|
| Restore your vault on a new phone using the supported encrypted backup and recovery process; keep your recovery material, because your face alone cannot restore unavailable data. |
02Seven questions for any biometric vendor
Seven questions to ask any biometric vendor.
01Is a biometric template ever stored?
No. A sealed artifact is kept instead. SenseCrypt IdP keeps a quantum-safe, sealed, biometric-free, disposable face token per user: rotating, single-use and containing no PII. SenseCrypt eID and ZKP keep a sealed SensePrint, which may carry issuer attributes. Both are designed to be unlinkable across services and cannot be reversed into a face. The retention table lists every record each product keeps.
02Does a plaintext private key ever exist at rest?
Not your SenseCrypt PKI signing key. A live face match generates your SenseCrypt PKI private key in memory for each face sign or face decapsulate operation, and the key is never saved. Public keys are stored. Issuer, CA, IdP tenant signing and device keys are different: they have their own custody lifecycles and are stored.
03Is the cryptography post-quantum?
In SenseCrypt PKI, yes, and we name the exceptions. SenseCrypt PKI offers ML-DSA (FIPS 204) signatures and ML-KEM (FIPS 203) key encapsulation, alongside classical secp256k1. SenseCrypt IdP federation is classical: ES256 ID and access tokens and RSA for SAML.
04Can credentials be linked across services?
They are designed not to be. IdP face tokens and SensePrints are designed to be unlinkable across services. SenseCrypt ZKP presentations are designed to be unlinkable by default; optional consented linkage is a separate configuration. Disclosed attributes, account records, public keys and integration metadata can still identify a person.
05Is liveness enforced before key material is created?
Yes, for your SenseCrypt PKI key. Presentation-attack detection runs on the capture before SenseCrypt PKI generates the key. Presentation-attack detection is tested by iBeta to ISO/IEC 30107-3 Levels 1 and 2; injection attacks are assessed separately. This does not describe how device or infrastructure keys are created. We publish no PAD performance numbers.
06Are there public developer docs?
Yes. docs.sensecrypt.com documents Python, Android and iOS SDKs plus a REST API.
07Has the recognition been evaluated by NIST under your own name?
Yes. Seventh Sense's face recognition has been evaluated in NIST FRTE under Seventh Sense's own name since 2021. FRTE evaluates the recognition algorithm; it does not certify the whole product.
03Proof inventory
Evidence you can check.
Patent-pending face tokenization
Multiple SenseCrypt patent families filed (PCT) and granted.
Public docs
Python, Android and iOS SDKs plus a REST API, readable before you talk to sales.