Where your data lives, who can touch it, and what we promise.
A single page, plain language. The legal vault is below — DPA, sub-processors, AUP, retention. If you need anything else for procurement, ask.
Residency by region
Pin a model deployment to a specific region. We never replicate your traffic outside it. EU at launch — Lagos and Nairobi land H2 2026.
No-train by default
Your prompts and completions never train any model — ours, the provider's, anyone's. We don't log request/response bodies unless you opt in to debug logs.
Encrypted in flight + at rest
TLS 1.3 in flight. AES-256 at rest. Keys rotated quarterly via Cloud KMS. Customer data is not co-mingled across tenants.
Where models run
A model deployment lives in exactly one region. Inference traffic is pinned. We do not replicate weights or logs across borders.
Active and planned regions
Compliance
We don't claim what isn't audited. Status is live and links go to the report or registrar.
If we change any of this, you'll know.
- No training on customer data — ever, by anyone in our supply chain
- No silent model swaps — model versions are pinnable per request
- No data residency drift — once you pin a region, it stays pinned
- Sub-processor changes published 30 days in advance
- Logs auto-delete after 30 days; opt out for instant delete
- Right to export, right to delete, right to a real human on email
Legal & processor library
Anything missing? [email protected] — a real human reads it.