Legal

Privacy policy

Last updated 2026-10-10

Who we are

Tessio is operated by Triple Down AB, a Swedish company (org. no. 559333-6091, VAT no. SE559333609101, registered address Skeppargatan 55, 114 59 Stockholm). We are the data controller for the processing described on this page. You can reach us at hello@tessio.eu.

This policy covers tessio.eu, labs.tessio.eu and the Tessio.Cloud dashboard and API at cloud.tessio.eu and api.tessio.eu.

The short version

The product is built so that identity data never reaches us. An age check returns a yes or no proved from the EU Digital Identity Wallet, and the credential involved carries no name, no date of birth, no document number and no portrait. What remains is ordinary operational data: your account email, our correspondence, aggregate website statistics and, for our customers, a technical record of each check, kept for their plan’s period and short lived counters per network address that limit abuse.

Website visitors

Our websites use self hosted, cookieless analytics (Umami, running on our own EU infrastructure). It records aggregate page statistics and does not build visitor profiles, use cookies or share data with third parties. Legal basis: our legitimate interest in understanding how the sites are used.

If you email us, we keep the correspondence for as long as the conversation is relevant. Legal basis: legitimate interest.

Tessio.Cloud accounts

If you have a dashboard account we process your email address and password (stored as an Argon2id hash; we never see the plaintext), plus an audit log of administrative actions in your organisation. Legal basis: performance of the contract with you or your employer. If your organisation is billed, we also hold its billing details (legal name, address, VAT and registration numbers, billing email and any purchase reference) to invoice it. We keep this data for as long as the account exists, except as the next section says for when it closes.

People who take an age check

If you proved your age to one of our customers through Tessio: we received no name, no date of birth, no document number and no photo. The credential your wallet presented contains age booleans and nothing else, and you approved exactly what was disclosed on your own device.

What we hold afterwards is the outcome (a yes or no), a reference chosen by the customer, timestamps and the technical record of how the check went: which issuer signed the credential, what type of credential it was and which trusted list and certificate vouched for it; which method and channel were used and the browser family rather than the full browser string; and each step of the check with its time, including every failed attempt with its error codes and a short reason such as “the wallet declined”. If you use a wallet app on the same device that opened the check, the check page also sets a short lived cookie that ties the wallet’s answer to your browser; the cookie policy describes it. The check itself also keeps how many attempts failed and the error codes of the most recent one, for as long as the check is kept. To limit abuse, the pages and endpoints a check uses count requests per network address (an IPv6 address by its /64 block). The address is stored only as a hash, which is pseudonymised rather than anonymous, and is deleted an hour after the last request. Never a name, a date of birth, a document or a photo. We process this on the customer’s behalf as their processor, under a data processing agreement. For questions about a specific check, the customer you verified with is the controller and your first point of contact.

If you try the demo on this site, we are the controller of that check instead. It holds the same technical record with no customer reference, and we delete it a day later. Legal basis: legitimate interest in showing you the service you chose to try.

Where data lives, and who else touches it

Everything runs on servers in Helsinki, Finland (Hetzner), inside the EU, over TLS. We list the few external services we use, and the conditions, on the subprocessors page. We do not sell or share personal data with anyone for their own purposes.

How long we keep things

Account data lives as long as the account. Check records belong to the customer and are deleted once the period of the customer’s plan has passed: 30 days on Free and Starter, 90 days on Growth and a year on Platform and on Self host where we host it, counted from the check. The record of each step inside a check is kept for 7, 7, 30 and 90 days respectively (90 on Self host where we host it). When a customer moves to a plan with a shorter period, the period of the longest plan it moved from keeps applying for 30 days after the change, and a further change of plan within those 30 days starts them again. When a customer’s account is closed, its check records, keys, webhooks and its users’ dashboard accounts (unless they belong to another organisation) are deleted within 30 days. We keep what accounting law needs: the organisation’s name and billing details, its invoices and the usage they bill, the names of the projects billed and a record of the account’s creation and closure and of what we did to it. For each verified live check, billing keeps a row with its id, the project and the time it completed, as part of our accounting records. Demo checks are deleted a day later. Backup copies, and the storage snapshots that hold them, are deleted on a rolling schedule, within 25 days in normal operation. If you ask us to delete your data, we do, and the deletion reaches backups as they expire.

Your rights

Under the GDPR you can ask for access, correction, deletion, restriction and portability, and you can object to processing based on legitimate interest. Write to hello@tessio.eu and we will answer within a month. You can also complain to the Swedish supervisory authority, Integritetsskyddsmyndigheten (imy.se), or to your local authority.

We do not use automated decision making or profiling in our own processing. An age check itself is automated, but it happens on the instructions of the customer you verified with, and its only output is the yes or no you approved in your wallet.

Related: cookies · subprocessors · security · terms · questions to hello@tessio.eu