Trust Center
Our compliance and sovereignty posture — GDPR alignment, data residency, encryption, and transparency.
GDPR posture and data residency
Three things carry our sovereignty claim: the region your GPU is pinned to, the fact that the control plane is not in the inference path, and a subprocessor list that names every company by what it processes. Each is checkable. The fourth item below is not a claim at all — it is what we have not finished.
What makes us sovereign:
- Where the machines are: Every machine we run for you is in an EU region you picked, and a deployment is never moved out of it. We do not route or store your inference content anywhere.
- The inference path: Your client calls your GPU's own address directly. No machine of ours sits between the two, so on our side of that request nothing leaves the EU — and there is nothing for us to read. Where your own client runs is yours to decide.
- Who runs the hardware: An EU infrastructure provider, in France. The subprocessor list says what each provider processes and where.
- Not done yet — the legal entity: The EU company is being filed and does not exist yet. We will name it here once it does, rather than describing the plan as a credential.
Data Processing Agreement (DPA)
DRAFT — awaiting counsel review
We will provide a written Data Processing Agreement covering:
- Data processor/controller roles and responsibilities
- Data processing security measures
- Data subject rights handling
- Breach notification procedures
- Data transfer mechanisms (within the EEA)
You will get it as part of signing up, once counsel has settled the wording.
Subprocessor list
DRAFT — awaiting counsel review
We publish every company involved in delivering Ratel. The rules we hold that list to:
- Every machine that touches customer data runs in an EU region
- Your prompts and completions reach only the company running your GPU — they never leave that machine, so no other subprocessor sees them
- You are told before a subprocessor changes
- Each one is under a contract carrying GDPR data-protection terms
The list is drafted and under legal review. It is on the subprocessors page today; it becomes contractual when the DPA does.
EU sovereignty levels (CADA)
A proposal, not law — we claim Level 1 only
The Cloud and AI Development Act (CADA) is a European Commission proposal from June 2026. It would let public buyers ask for one of four sovereignty levels:
- Level 1, data in the EU: every Ratel deployment runs in one EU region, and its data path stays there. This is the level we claim.
- Levels 2 to 4 add independence from non-EU suppliers, EU ownership and control, staff who are generally EU citizens, and an EU certificate. Ratel does not meet these today, so we do not claim them.
No CADA certificate exists yet. If the act passes, this section will say which level we meet and how we know.
EU AI Act transparency
Posture and roadmap — not certified
The EU AI Act's transparency obligations apply in stages from August 2026, and most of them fall on whoever puts an AI system in front of users — which is you, not us. What we can do is make sure you can describe what you are running:
- What each build publishes: Its license, its context length, the GPU it runs on, its quantization and our throughput estimate — all of it on the models page before you deploy. We do not write capability or limitation assessments for third-party models, and we would not want you to rely on ours if we did.
- Training data: We do not publish training-data provenance. These are third-party open-weight models and we have no independent knowledge of what they were trained on; the model card from whoever released the weights is the source, and it is the one to cite.
- What you can see: The hours each deployment ran and what they cost, in the portal. Not what you sent it — we cannot see that, so we cannot report it either.
- No inference content logging: We do not log or store customer inference prompts or responses. This is a hard guardrail built into our architecture.
We are not EU AI Act certified, and no certification scheme for this exists yet to be certified against. What we do is publish what we know and say plainly where we do not know.
Encryption at-rest and in-transit
Attestation
What is encrypted today, and what is not:
- In transit: Model endpoints are not yet served over TLS. A request to a deployment reaches the machine's own address in the clear, guarded by a per-deployment credential rather than by encryption. The TLS-terminating ingress that replaces this is built and not yet deployed. Internal service-to-service traffic is not separately encrypted.
- At rest: Our infrastructure provider encrypts the physical disks our volumes sit on and manages the lifecycle and rotation of those disk keys. We do not add volume-level encryption on top — under the provider's shared responsibility model that is ours to do, and we have not done it yet. What lives on those volumes is model weights and each instance's own endpoint credential. Your prompts and completions are not among them: they are never written to our disks at all.
- Key management: We run no key management service and hold no encryption keys of our own. The keys behind the provider's disk encryption are the provider's to manage. The one secret we generate per deployment is that deployment's model-endpoint credential, which is shown to you because you need it to call your own machine.
This attestation is based on our current architecture and infrastructure. A formal independent assessment is planned for a later phase.
Posture summary
What we are: A GPU you rent in an EU region, with an architecture that keeps your inference content out of our systems entirely, and a habit of writing down what we have not built.
What we are not: SOC 2 certified, ISO 27001 certified, or EU AI Act certified. We describe our practice and roadmap — we never claim certifications we do not hold.
Roadmap: The certifications above need independent audits, and none is booked yet. The legal work — the company, the DPA and this subprocessor list — is running alongside the engineering rather than after it.
Questions about compliance?
Ask us anything on this page and we will answer it in writing, including where the answer is "not yet".
Contact us