Arizon Id
TermsPrivacy

Terms of Service

Last updated 29 October 2026

These terms cover the use of Arizon Id — the age verification API, the developer portal, and the sandbox — by the organisation that signs up and by the people it invites.

The service

Arizon Id checks whether a person holds a credential attesting they are over a given age, and returns that answer to you. It does not tell you who they are, and it is not an identity service.

Accepting these terms

An organisation accepts these terms when it is created in the portal. The person creating it accepts them on its behalf, and confirms they are authorised to. We record who accepted, when, and which version — the date at the top of this page — and keep that record for as long as the organisation exists. People invited into an organisation afterwards act under the terms it accepted.

Your organisation and its members

An account belongs to an organisation, not a person. Owners and admins may invite others, and anyone they invite can act within the role they were given. You are responsible for who you invite and for removing them when they should no longer have access.

API keys

Each environment has its own key. Treat it as a credential: anything done with your key is treated as done by you. Keys expire, and we email before they do; rotating leaves the previous key working for a short overlap so you can deploy in your own time.

A production key is shown once, when it is created or rotated, and cannot be read back afterwards — we keep only a hash of it. A sandbox key can be read again by anyone in your organisation, because the portal uses it to demonstrate the API from the browser. If that is not what you want for a sandbox, do not put anything through it that you would mind a colleague seeing.

Sandbox and production

Sandbox environments exist for development. They accept credentials from our own test issuer and from Member States' test issuers, which production does not: a test credential is never accepted as proof of age in production. Do not treat a sandbox result as a real verification, and do not put real customers' data through one.

Limits

Requests are rate limited per environment, per minute and per day, and the limits are visible in the portal. Retention is bounded too — 30 to 365 days in production, 1 to 30 in sandbox — and data past its period is deleted whether or not you have read it.

Using it properly

You agree not to:

  • use the service to profile or track people across verifications;
  • attempt to obtain attributes beyond the age answer you asked for;
  • present a verification result as an identity check, or as proof of anything else;
  • share API keys outside your organisation, or work around the rate limits.

Availability

We do not promise uninterrupted service, and there is no agreed service level yet. Where a verification cannot be completed — because a trust list is unreachable, or an issuer cannot be checked — the service fails the verification rather than passing it. An outage will never turn into a wrongly granted answer.

Your obligations as a controller

Where you use Arizon Id to check your own customers, you decide why, and the law puts the corresponding duties on you: having a lawful basis, telling people what happens, and answering their requests. Our privacy policy describes what we do on your behalf.

Ending it

You may delete your organisation at any time, and an owner or admin may delete any of its applications or sandbox environments. What you delete stops at once: its API keys stop working, no more webhooks are sent, and nobody in your organisation can see it or bring it back — not by signing in again, nor by registering again with the same address.

We keep what was deleted, with its verification data, for 90 days, so that a deletion made by mistake can be undone: within that time only our support can restore it. After that it is deleted for good. The record of how many verifications were made, which billing needs, is kept; it identifies no one.

We may suspend an account that is being used in breach of these terms.

Changes

We will say here when these terms change, and date the change, rather than revise them quietly. The date at the top is the version an organisation accepts.

Contact

Arizon AB — contact@arizon.se.

Arizon AB · contact@arizon.se