Data Residency & Zero Data Retention
A call through Mizan touches exactly two systems before the answer comes back to you: Mizan's own gateway, and whichever provider serves the model you called. This page covers both halves of that journey — where each one runs, and what, if anything, gets kept along the way.
How your data flows
You send a request to Mizan. Mizan routes it to the provider behind the model you asked for. The provider generates a response and sends it back. Mizan returns that response to you. That's the whole path — your data passes through two points, Mizan and the provider, and nowhere else.
You
Your app or user
Mizan
EU today — KSA, UAE, US coming soon
Provider
EU, US, KSA or UAE — your choice
Your prompt and the provider's response pass through exactly these two points — nowhere else.
| Touchpoint | Location | Retention |
|---|---|---|
| Mizan (the gateway) | EU today. KSA, UAE and US hosting are coming — you'll pick where your traffic transits. | Never stores prompts or completions by default. Only metrics (tokens, cost, latency, model) are kept. |
| Provider (the model) | Your choice — EU, US, KSA or UAE, filterable in the model list. | Zero data retention by default on every provider Mizan routes to. |
Where Mizan runs
Mizan itself is currently hosted entirely in the EU — every request you send is processed by infrastructure that never leaves the EU before being routed onward to a provider. KSA, UAE and US hosting are coming next: once they ship, you'll be able to choose which region Mizan itself runs in, the same way you already choose a provider's region today.
Choosing your provider's region
The model list includes providers based in the EU, US, KSA and UAE, so you can pick where the second half of the trip happens too. Choose an EU-based provider and your data never leaves the EU; choose a KSA-based provider and it stays in KSA — the model you route to determines the region the call is actually served from, not just a label. See Vertex AI (EU) and Scaleway (EU) for two concrete EU-pinned examples, or browse Models and filter by data residency directly.
Zero data retention, by default
By default, Mizan never retains your data. A prompt arrives, gets routed, and the response comes back — nothing about that exchange is written to disk. We never store your prompts, your completions, or anything else about the content of a call. The only thing we keep is the metrics needed to power your dashboard — cost, tokens, latency, model, provider — never the content itself. See Data Retention for the full schedule of what's kept and for how long.
Opt-in features that store content
Three features are the exception, and all three are off by default, configured per Mizan API key: Response Caching (stores a completion so it can be replayed verbatim next time), Souq (mines captured traffic into a weekly usage report), and Tracing (captures the full prompt, completion, and tool calls for browsing later). Turning any of these on for a key means Mizan stores that key's prompts and outputs — currently in the EU, with multi-region storage coming alongside multi-region hosting. Leave all three off, and nothing about your calls is ever stored beyond the metrics described above.
Provider-side retention
Every provider Mizan routes to runs with zero data retention by default — your prompts and completions are not retained by the provider once the response has been returned to Mizan and back to you.
Working in a sensitive field?
If you need an extra layer of control — regulated data, an internal compliance requirement, or just peace of mind — connect your own provider account with BYOK. The call still goes through Mizan the same way, but it's served with your own credential against your own provider account rather than Mizan's platform credential.