Arizon Id
TermsPrivacy

Privacy Policy

Last updated 29 October 2026

Arizon Id answers one question about a person — whether they are over a given age — and is built so that answering it reveals as little as possible. This page says what that means in practice.

Who is responsible for what

Arizon AB provides the service. Where a business uses Arizon Id to check the age of its own customers, that business decides why the check happens and is the controller of it; Arizon AB processes on its behalf. For the developer portal — accounts, organisations, API keys — Arizon AB is the controller.

What a verification actually discloses

When a holder presents a credential, their wallet is asked for a single attribute: whether they are over the age the business asked about. The request sets limit_disclosure, which tells the wallet to release that attribute and nothing else, and marks every field intent_to_retain: false.

We do not receive a date of birth, a name, a document number, a photograph or an address. They are not withheld after the fact — they are never sent.

What is recorded

  • Whether the answer was yes or no, and the age asked about.
  • Which issuer vouched for the credential: the name it signs under, the fingerprint of the certificate it signed with, the accredited provider and country behind it, and the trust anchor we accepted it on. This is about the issuing authority, not about the person.
  • When the check happened, and which application and environment it belonged to.
  • A record of the attempt itself: its status, and an error code and reason when it failed.

There is no identifier here that follows a person between checks. Two verifications by the same holder are not linked, by us or by anyone reading this data.

How long it is kept

Each environment sets its own retention period, and the service will not accept one outside these bounds: 30 to 365 days for production, 1 to 30 days for sandbox. A sweep runs hourly and deletes verification sessions, results and audit events past that period. Deletion here is not a flag — the rows go.

Deleting an organisation, an application or an environment stops it at once, but we keep its data for 90 days, so that a deletion made by mistake can be undone through our support. The retention above keeps applying meanwhile, so nothing is kept longer than it would have been had the deletion not happened, or longer than those 90 days. Then everything goes, except a count of the verifications made, which billing needs and which identifies no one.

Portal accounts

Signing in to the developer portal uses GitHub, Google or a Microsoft account. We receive your email address and display name from whichever you choose, and store them alongside your role in your organisation. We never see your password. Invitations are held as a pending membership against the address they were sent to and expire after fourteen days.

Creating an organisation asks for its name and its line of business — what kind of organisation it is, chosen from a list — which we use to understand who uses the service and what they need from it. We also record that the person creating it accepted the terms of service and read this policy: their email address, the time, and which version of each. That record is kept for as long as the organisation exists, and deleted with it — 90 days after the organisation is deleted, as everything else of it is.

Where it is processed

The service runs on Microsoft Azure in Sweden Central, and verification data stays there. Three processors act on our behalf:

  • Microsoft Azure — hosting and databases, in the EU.
  • AhaSend — sending portal email, such as invitations and expiry notices.
  • GitHub, Google and Microsoft — signing in to the portal, if you use them.

Your rights

Under the GDPR you may ask for a copy of your personal data, ask for it to be corrected or erased, object to processing, or ask for it to be restricted or ported. Write to contact@arizon.se.

One honest limitation: for a verification, there is usually nothing to look up. We hold no name or identifier for the person checked, so we cannot find their record from their identity — the same design that protects them also means we cannot single them out on request. If you know the session id, we can.

You may also complain to a supervisory authority. In Sweden that is Integritetsskyddsmyndigheten (IMY).

Changes

If this page changes in a way that matters, we will say so here and date it rather than change it quietly.

Arizon AB · contact@arizon.se