Privacy and security
Zatoona Labs is built for sensitive data. It runs on Zatoona Cloud in the EU or entirely inside your institution, and in both every analysis is sealed, its model calls pass one gateway, and no model keeps or trains on your data.
What leaves your environment, and what never does
Analyses run next to the data, in a sealed sandbox. Their model calls go out through one gateway, and answers come back the same way.
- Your data, files and results stay inside
- Models receive only what a step needs, and keep nothing
Zatoona CloudEU
Inside your institution
- EU-hosted modelszero retention
- Scientific sourcesPubMed, ChEMBL, Open Targets
Two ways to run it
The same product and the same safeguards. What differs is where the boundary sits and who runs it.
| Zatoona Cloud EU | Inside your institution | |
|---|---|---|
| Where it runs | Zatoona Cloud, in the EU | Your environment, such as a digital research environment (DRE) or a group server |
| Who runs it | Zatoona | Your IT team, with our help |
| Each project's analyses | Its own virtual machine | Its own container |
| Models | EU-hosted, zero retention, through the gateway | The same, or your own hosted models and approved endpoints |
| Your data | Stored in the EU | Stays inside your environment |
| Audit log | In the deployment's database, in the EU | In a database inside your environment |
| Access by Zatoona staff | For support, at your request. During early access, also your sessions, unless you opt out | None |
How it is set up
The details a privacy officer or data manager usually asks about first.
A sealed sandbox for each project
Analyses run in an isolated sandbox for their project: its own virtual machine on Zatoona Cloud, its own container inside your institution. It gets only that project's files and no platform keys, has set limits on compute and memory, and shuts down shortly after the work ends.
One gateway, both ways
Every model call an analysis makes, and every answer that comes back, passes one gateway. Each run gets a short-lived key with a budget, and provider keys never enter the sandbox. Which models and limits it allows is set per deployment.
Models in the EU
Zatoona Labs uses EU-hosted model providers with zero data retention and no training on your data, so model calls stay in the EU. Inside your institution the gateway can instead point to your own hosted models or other approved endpoints.
Evidence and the record
The files behind a finding are frozen with their hashes when it is registered, and tests run on a copy. Logins, file activity and runs are logged in a database that sits with the deployment, and every model call is recorded at the gateway.
Questions we often get
Is my data used to train models?
No. Zatoona Labs only uses model providers that do not retain or train on your data.
What does sovereign mean here?
That your data stays under your control and your jurisdiction. On Zatoona Cloud, the app, its database, every analysis and every model call run in the EU, on a hyperscaler's EU region, and nothing is transferred outside it. For full sovereignty, run Zatoona Labs entirely inside your institution: then we have no access at all, and the gateway can point to your own hosted models.
Where is Zatoona Cloud hosted?
In the EU. The app, its database and every analysis run on infrastructure in the EU, and model calls go to EU-hosted providers.
Can we use it with sensitive or patient data?
Yes, that is what it is built for. During early access on Zatoona Cloud, please keep identifiable patient data out. When patient-level data must not leave your institution, run Zatoona Labs inside your environment through a pilot.
How does Zatoona Labs fit with GDPR?
Your institution stays the controller of its data. Your data and analyses stay in the EU, and the few providers outside it are covered by the EU Standard Contractual Clauses or the EU-US Data Privacy Framework. The sandbox, gateway and audit log support the security your DPIA will ask about. On Zatoona Cloud we sign a data processing agreement and publish our sub-processors; inside your institution we have no access to the data at all.
Can the Zatoona team see our data?
On Zatoona Cloud, Zatoona staff can technically reach the deployment's storage. We open your files only for support, at your request. During early access, the team also reviews sessions (prompts, conversations, the AI's steps and results) to improve Zatoona Labs, unless you turn this off in your account settings. Sessions are never used to train models. Inside your institution we have no access at all.
Can we choose the language model?
Yes. The gateway is configured per deployment to match your governance rules: which EU-hosted, zero-retention providers and models are allowed, and inside your institution your own hosted models or other approved endpoints.
Where is the audit log kept?
In a database that sits with your deployment: inside your environment when Zatoona Labs runs there, in the EU on Zatoona Cloud.
How do we get approval in our institution?
We work through your process with your privacy officer and information management, and share the architecture and data flows they need for review.
Talk to us about your data environment
We can walk your privacy officer and IT team through the architecture before a pilot starts.