DocsPrivacy and security
Privacy and security
PlannedThe design goal is that your site learns yes or no, and nobody learns who. This page lists what that means in practice, so your own advisers can assess it.
What is and is not stored
Kept, per customer
- Monthly counts of passed, failed and cancelled checks
- The method used (mdoc, zero knowledge proof, OpenID4VP) and the age threshold
- Your account, API keys and allowed origins
Never stored
- The credential or anything inside it
- Birth date, name, document number, photo, issuing country
- Visitor IP address, browser fingerprint or cookies
- Any identifier that links two checks of the same person
Ageseal also does not log request bodies. Error reports carry codes, never payloads. Cloudflare, which runs the edge network, necessarily handles IP addresses in transit; Ageseal does not retain them.
The website and dashboard have their own, separate policy: Privacy.
What is in a token
A result token holds the answer and the facts needed to verify it, and nothing derived from the credential except the yes or no.
| Contains | Does not contain |
|---|---|
Who issued it (iss) and which site it is for (aud) | Name, birth date or age |
The threshold (over), the answer (result) and the key mode (mode) | Document number, photo or issuing country |
How the proof was made (method) | The issuer of the credential, or any certificate |
When it was issued and when it expires (iat, exp) | A subject identifier, or anything that links two checks of one person |
A random token id (jti) | The visitor IP address, browser details or cookies |
The claims are explained on Verify tokens.
Data flow
| Step | What moves | What stays behind |
|---|---|---|
| Wallet to browser | An encrypted answer to one question: over 18 | Everything else in the wallet. The visitor approves the request first. |
| Browser to Ageseal | The encrypted wallet response, with your publishable key | Nothing is written to cookies or storage by the SDK. |
| Inside Ageseal | The response is decrypted and verified in memory, and then dropped | The decrypted response is never written anywhere. |
| Ageseal to browser | A signed token | Counts per site, with no visitor data. |
| Browser to your server | The token | Your own logs follow your own policy. |
How tokens and sessions are protected
- Every check starts with a session that has a fresh random nonce and an ephemeral key, and it lasts 5 minutes.
- A session can be used once. A second submission is rejected.
- The wallet response is bound to your origin and to the session nonce, so a response captured on another site does not verify.
- The issuer signature is checked against the EU age verification trusted list before any answer is returned.
- Tokens are signed with ES256. You verify them with public keys, so there is no shared secret in your page.
- Tokens are short lived, 10 minutes in the current draft. For strict single use, redeem them with your secret key.
All of these are planned behaviour. The values, such as the session and token lifetimes, may change before the first release.
Standards
- W3C Digital Credentials API: the browser asks the wallet.
- OpenID4VP 1.0: the wallet presents the proof.
- ISO mdoc: the credential format.
- The W3C Digital Credentials API is how the browser asks the wallet and how the wallet answers. It is a working draft.
- OpenID4VP 1.0 describes the presentation request and response between verifier and wallet.
- ISO mdoc (ISO/IEC 18013 part 5, with the web presentation profile in part 7 Annex C) is the credential format. The EU age verification attestation is an mdoc that carries the age over 18 attribute.
- The EU age verification trusted list tells Ageseal which issuers to trust.
Limits
- Ageseal proves that a valid credential bound to a device answered this request. It cannot prove who is holding the phone. Every wallet based method shares this limit.
- Ageseal asks for an age threshold and nothing else. It does not verify identity.
- Whether using Ageseal meets your legal obligations depends on your sector and country. Confirm it with your own advisers.
- Ageseal is an independent product. It is not affiliated with or endorsed by the European Commission, any government or any wallet provider.
Report a security issue
Write to support@ageseal.eu with the details. Please do not include personal data of third parties.