Under the GDPR, a face used to identify someone is special-category data. JERIX verifies identity against the document, then deletes the images and biometrics, so there is no face database for you or for us to protect.
Privacy law treats biometric data differently from an email address or a username, and the risk follows whoever holds it.
Biometric data processed to uniquely identify a person is one of the special categories of personal data. Processing it is prohibited unless a specific condition applies, and it usually brings stricter documentation and security expectations. Other regimes, including Israel’s Amendment 13, also treat biometric data as especially sensitive.
A database of faces and document images is valuable to an attacker and cannot be reissued after a breach. Every year it is kept, it has to be secured, audited and justified. Read more in the biometric honeypot.
Identity fraud is stopped at the check. What made the check possible is deleted right after it.
Face images, face templates, document images and chip data are not kept. Deletion is part of the architecture, not a retention setting that someone can change later.
A minimal identity record remains, encrypted at rest. The full list, and how long each item is kept, is in the privacy notice.
An integration can be limited to a verified yes or no and an age answer. The face, the document and the date of birth stay out of your systems.
Two clients receive different tokens for the same person, so neither can join its user base to the other’s. See the security page for the tests behind each claim.
The full flow, with what each step proves, is on the how it works page.
The person scans their document and takes a selfie on their phone. With a passport, the app reads the chip and its signed photo.
The passport chip signature is checked to the issuing state’s root, offline, and the live selfie is matched to the chip’s own photo. Other documents use photo-based verification.
Your platform receives a verified yes or no and an age answer. Face images, face templates, document images and chip data are deleted once the check completes.
Article 9 of the GDPR lists biometric data processed for the purpose of uniquely identifying a person among the special categories of personal data. Processing it is prohibited unless a specific condition applies, such as explicit consent. Which condition fits your case is a question for your counsel.
No vendor can make that promise for you. Compliance depends on your whole processing, your lawful basis and your documentation. What JERIX changes is the data: no images or biometrics are retained, so you do not hold a face database that would have to be protected.
No images or biometrics are retained. A minimal identity record remains, encrypted at rest, and it is listed in full in the privacy notice.
It does not have to. An integration can be limited to a verified yes or no and an age answer, so no name, ID number, date of birth or image has to cross into your systems.
This page is general information, not legal advice. Consult your own counsel about how the GDPR and other privacy laws apply to your platform.
We walk your privacy and security team through what is deleted, what is kept, and how to check it yourselves.
Book a demo