OLLETOllet connects a live person to an identity credential. The app checks the credential during setup and uses its verified portrait as the reference for subsequent face checks. The requesting service verifies the resulting proof before using it in an account or approval workflow.
Credential authentication
During passport setup, Ollet reads the electronic chip and checks its digitally signed data against trusted issuer certificates. This establishes the origin and integrity of the identity information and portrait used by the app. ICAO's ePassport guidance explains how digital signatures support this check.
Verified identity data remains stored locally on the user's device. The user can complete subsequent verification requests using the identity already set up in Ollet.
Liveness and face matching
When the user completes a verification, Ollet evaluates a live camera capture for evidence that a person is present. A separate face comparison checks whether that person matches the portrait from the verified credential.
Liveness detection and face matching run on the device. The comparison uses the person's own credential as its reference; it does not search a central face database. These checks are designed to reduce impersonation through substituted photos, recordings, or another person's identity document.
App attestation and proof verification
The device produces cryptographic evidence of the verification. App attestation helps the verifier assess whether the response came from a legitimate instance of Ollet. Apple's App Attest service supports this assessment; attestation is a security signal rather than a guarantee that every compromised device can be detected.
The verifier checks the response's signatures, attestation evidence, and request context, including the challenge and intended recipient. Binding the response to a request helps prevent a result from being substituted into another session. The service must validate the response before accepting its identity attributes or outcome.
Credential issuer certificates establish trust in the document data. Device attestation supports trust in the app's response. These serve distinct roles in the verification process.
Information shared with a service
The request specifies the identity attributes needed for the action. The user reviews and approves sharing those details in Ollet. The response can include limited attributes such as given names, surname, or date of birth; the exact result depends on the integration.
Identity documents and biometric images are processed locally and are not uploaded to Ollet's servers. Verification requests, cryptographic proofs, and approved identity attributes do travel between the device and services. The online workflow therefore requires a connection even though the identity and biometric checks take place on the phone.
The Privacy Policy describes local processing, operational information, and the responsibilities of services receiving verification results.
The organization's decision
The organization connects the verified identity to its employee, candidate, or customer record. It then applies its own authorization rules to the requested action. Identity verification supplies evidence about the person; the organization's records establish their relationship to the account and their permission to act.
The Product overview explains these responsibilities for Okta and custom integrations. The demo displays a verified passport name and examples of where to request verification.