How Identified keeps the answer yes-or-no, and the data to yourself.
Four steps from passport scan to verified age. The raw birth date never leaves the device in plaintext; our server only ever sees opaque ciphertext and answers a single yes/no question.
15 MAR/MAR 1990Four steps. Nothing that looks like a user leaves the phone.
The user scans their passport
Our app on the user's phone reads the NFC chip in their passport or national ID and verifies the government-issued signature chain. Forged documents don't progress past this step.
Birth date is encrypted on device
The birth date is encrypted before it leaves the phone — on-device, with a key the user holds. Our server only ever sees ciphertext.
Age comparison runs on encrypted data
The server runs a single operation on the ciphertext. The answer that comes out is also ciphertext. We never see a plaintext date or even a plaintext yes/no.
Your service gets a yes or no
The encrypted result is decrypted locally on the user's device and digitally signed. Your backend receives proof that the person is old enough — and literally nothing else.
What stays with the user, and what we actually get.
The user keeps
- Full control — passport data is read, encrypted, sent and erased
- The private key used to encrypt and decrypt
- The plaintext answer
What we see
- Opaque ciphertext in, opaque ciphertext out
- A pseudonymous session id
- — that's it