Skip to content
siati.ai docs

Concepts

Sovereignty

For siati.ai the machines, the data, the copies and the control plane are all in Switzerland. What is kept, for how long, and how to check it.

Last updated: 2026-11-03

Four questions decide whether a service is sovereign, and each answer can be checked: who runs the machines, where they are, which law governs the service, and who could be ordered to hand over the data. For siati.ai:

Question Answer
Who runs the machines SIATI, a Swiss institute. siati.ai offers only Swiss zones (CH-n). Every machine that serves siati.ai is run by us, in Switzerland.
Where they are In Switzerland.
Which law governs the contract Swiss law.
Who could be ordered to hand over the data SIATI, which holds them. It is not a US organisation and has no subsidiary in the United States.

Everything in Switzerland

The platform is split in two parts that do not mix.

  • The control plane keeps the inventory of the machines, the catalogue of models and the zones. It never sees a customer: no accounts, no keys, no texts.
  • The data plane of siati.ai keeps everything that concerns you: accounts, keys, usage records, conversations, uploaded documents, copies of the database. The API you call is part of it.

For siati.ai both are in Switzerland, and so are its zones. The data plane downloads its configuration every minute and works from its own copy. Once an hour it sends the control plane numbers, and only numbers: for every hour, model, machine, endpoint and zone, the count of calls and errors, the tokens and the average time. No user, no key, no text, no IP address.

What goes abroad is listed in Sub-processors: the mail you write to our mailboxes (Google) and DNS (Cloudflare). Nothing of what you send to the API.

Where your requests go

Every key has the zones it may use. On siati.ai those are only Swiss zones (CH-n).

  • A text generation request goes only to the machines of the key's Swiss zones.
  • If the chosen machine fails before the first token, the request moves to another machine of the same zone.
  • If no machine is available, the answer is 503 and names the zone. The request is never sent anywhere else.

Only text generation goes through zones on siati.ai today: /v1/chat/completions, /v1/completions and /v1/responses. Embeddings, rerank, transcription, speech synthesis and the reading of the documents you upload run on dedicated machines that do not go through zones yet; for siati.ai they are machines we run, in Switzerland. A brand with a transcription machine in its zones transcribes whisper-1 there: siati.ai has none.

What is kept, and for how long

All of it in Switzerland.

What How long
Account, keys, invoices while the account exists; invoices also after
Usage records: time, endpoint, model, tier, zone and site, tokens, time taken, outcome, and the user field if you send it while the account exists
Request log: endpoint, model, tokens, time taken, outcome. The text of requests and answers only for the keys where you turn on "keep messages" in the dashboard, for debugging, encrypted 30 days
Conversations kept by the chat app, the mobile app or the chat sessions API: messages encrypted, titles not until you delete them
Documents you upload, their pieces and their vectors until you delete them
Copies of the database one every night; the last 30 are kept

"Encrypted" means encrypted by the application before it is written to the database, on top of whatever protects the disk. What you delete stays in the copies of the database until they rotate out, after 30 days.

Technical logs, that is errors and requests with the IP address of the client, stay on the same machines for 14 days.

Deleting

  • A document: its file, its pieces and its vectors are deleted at once.
  • A knowledge base: in the dashboard. The files, pieces and vectors of all its documents are deleted at once, with it.
  • A conversation: deleted at once, with all its messages.
  • The account: in the dashboard, under Account. It is disabled at once, and for 30 days the deletion can be undone by writing to privacy@siati.ai. After 30 days conversations, knowledge bases with their files and vectors, keys, the request log and the usage records are deleted, and the account is anonymised.

What stays after the account is deleted: the invoices, for the 10 years the law requires, and a record of the request (email address, time, IP address and browser), kept 12 months as proof that the deletion was carried out.

How to check

  • X-Zona on every chat completion carries the Swiss zone code (CH-n) where it was processed.
  • X-Siati-Region: CH-TI on every response of siati.ai is the region the service declares: the canton of Ticino.
  • Usage records keep the zone and the site of every request. The dashboard does not show them yet: ask support@siati.ai for an extract.
  • The catalogue lists the countries of every model: Models catalogue.
  • Who else touches your data: Sub-processors.

Contract documents

The data processing agreement is drafted under article 9 of the Swiss Federal Act on Data Protection and article 28 of the GDPR, and is sent on request: write to privacy@siati.ai. More in nLPD and NIS2.

Search the docs

Type to search…