For compliance, legal and DPOs
Age verification that stores no identity data
Tessio stores no documents or dates of birth, so a breach has none to expose. A user proves they are over 18 with the EU age verification app (the EU Digital Identity Wallet follows once our access certificate is issued). Here is what that means for your compliance work.
A document scan or a database match adds data risk, because you now hold identity data you have to secure, minimise and justify. Tessio works the other way. The user proves one claim (that they are over 18) and you get a signed yes or no. There is no date of birth, no document image and no selfie, on your systems or ours.
That posture lines up with the rules. GDPR asks you to minimise personal data, and Article 28(3) of the DSA says protecting minors does not oblige online platforms to process more personal data to check age. A single over 18 boolean is about as data minimal as an age check gets.
You store no documents or dates of birth
The result is an over 18 yes or no, not a date of birth or a document. You cannot leak what you do not hold, so a breach of your systems exposes no ID data.
Data minimisation
One question and one answer, which fits the GDPR principle of data minimisation.
Auditable results
Each result is signed, so you keep verifiable evidence that you ran a real check for your regulator, without keeping any identity data behind it.
Self host for data residency
When check data cannot go to a hosted service, our self host plan runs Tessio on your own hosts with the trust layer delivered to it.
The compliance posture
- No document image, no selfie and no date of birth stored.
- An over 18 result instead of identity data, so your GDPR footprint and breach exposure stay low.
- A signed, auditable result you can keep as evidence of a real check.
- Built to the standards the EU wallets use: OpenID4VP, SD-JWT VC and ISO 18013-5 mdoc.
- The verification core is open source under Apache-2.0, so teams that cannot send check data to a third party cloud can run it themselves.
Frequently asked
What do you store about the people you check?
The outcome, a yes or no, plus your reference and a technical record of how the check went. There is no date of birth, no document image and no selfie, on your systems or ours. The privacy page lists every field.
Is it GDPR compliant?
We check one claim and keep the yes or no, your reference and how it was verified, never a document or a date of birth. That is the data minimisation posture GDPR and the EU Digital Identity framework are built for. You stay in control of your own processing, and if you need the check inside your own boundary you can self host the open source core.
Where is verification processed?
Tessio is EU based with EU data residency. If your obligations mean check data cannot leave your environment at all, you can self host the .NET verifier and keep processing in your own boundary.
Keep exploring
Age verification for dating apps
Dating and matchmaking
Age verification for adult platforms
Adult content
Age verification for social and UGC platforms
Social and user content
EU Digital Services Act and age assurance
EU regulation
UK Online Safety Act age assurance
UK regulation
The EU Digital Identity Wallet, for relying parties
EU Digital Identity
Tessio for developers
For developers
Developer docs
The age verification API
For compliance, legal and DPOs
Talk through your posture
Tell us your sector and the duties you're meeting. We'll walk through how a wallet based over 18 check fits when no document or date of birth is stored. Signup is open and a test project works as soon as you create one.