Skip to content
siati.ai docs

Policies

Sub-processors

Who touches what. The complete list of third parties to which siati.ai passes data, and the line that matters: for processing your requests, nobody.

Last updated: 2026-11-03

This document lists all the third parties to which siati.ai passes data. We publish it because it is the difference between saying "there is nobody in the middle" and letting you check it.

It also serves a concrete obligation: the European data protection regulation (art. 28) and Swiss law (art. 9 FADP) require that whoever processes your data knows to whom else it goes. Whoever works with a supervised bank needs the same for margin number 33 of FINMA Circular 2018/3, which requires knowing subcontractors by name.

The line that matters

No third party is involved in processing your requests.

Your messages, the answers, the documents you upload, the vectors we derive from them and the audio transcriptions do not leave the machines we run. Every machine that serves siati.ai is run by SIATI, in Switzerland, in the zone of your key.

To be explicit about what we do not use:

  • no API from OpenAI, Anthropic, Mistral, Cohere, Google or Microsoft: the models are open-weight and we run them ourselves;
  • no large cloud provider for compute or storage: no AWS, Google Cloud or Azure;
  • no content delivery network in front of the service.

If that ever changes, this page changes first.

The providers below handle e-mail and DNS. None of them sees your requests. siati.ai sells nothing on the site, so no payment provider or app store appears here.

The providers involved

Provider What for What it receives Where Status
Google (Google Workspace) The mailboxes of siati.ai (privacy@, support@, info@): what you write to us there Your e-mail and its attachments Ireland (EU) and the United States, under the EU-US Data Privacy Framework and standard contractual clauses active
Cloudflare, Inc. DNS: tells browsers at which address siati.ai is. The service's traffic does not pass through Cloudflare The name looked up and the resolver's address United States, under the EU-US Data Privacy Framework and standard contractual clauses active

What is not in this list, and why:

  • Connectivity. It is not a sub-processor. The network the service runs on belongs to the institute: the prefix is announced by an autonomous system number registered to SIATI (AS43141), verifiable in the European address registry. Whoever carries the packets sees them encrypted and does not process data on our behalf.
  • Error diagnostics. We use no external error-collection service. If we ever enabled one, it would appear here before receiving its first byte.
  • The source code repository. It is on an installation of our own and contains programs, not customer data. It is a work tool, not a sub-processor.

We count visits ourselves

Visit counting runs on the same machines as the rest of the service. No external provider, and nothing that starts from the reader's browser.

  • No script. Counting happens on the server after the page is served. There is nothing to load and nothing to block.
  • No cookie. That is why the site has no consent banner: the only two cookies are the token against request forgery and the session one. Those do not require consent.
  • No IP address kept. To estimate how many distinct people pass by in a day we compute a fingerprint that changes every day and does not allow anyone to be recognised the next day.
  • No full referrer address. Of the referrer we keep only the domain, never the full address, which could contain the search terms.

Data processing agreements

Provider Agreement
Google Workspace Standard contractual clauses, in Google's data processing terms
Cloudflare Standard contractual clauses, in Cloudflare's data processing terms

How we tell you if it changes

If we add a provider that receives customer data, we update this page before the provider receives anything, and we tell everyone with an active contract by email. Whoever has a business contract can object and leave in an orderly way: it is written in the contract.


Review: yearly, and every time a provider is added or removed. Owner: the technical management.

Search the docs

Type to search…