Regions and data residency¶
"Where do our prompts go?" is usually answered from a wiki page, and checked by nobody. In Vidai, where a call may be processed is a rule the gateway applies to every call: region rules keep calls from a team, environment, application or agent within an area, approved destinations set the models any call may reach at all, and provider agreements can be required before a call reaches a provider. A call that would leave the area is refused, and the refusal says why.
Where a model runs¶
Every provider is placed: you say where it runs, and areas (such as the European Union) group those places. A model
runs where its provider is placed, unless the model says otherwise (an Amazon Bedrock inference profile starting
eu. or us. decides it, and a global. one meets no regional rule). A provider placed global, or not placed at
all, meets no region: "may run anywhere" isn't "runs in the EU".
Approved destinations¶
Models › Approved for use is the organisation's ceiling: the models any call may reach.
- While the list is empty, it does nothing.
- Once it has entries, a key may call only the models its model access allows and the list holds. A call to any other model is refused at the gateway.
- Rules that would send content to a model off the list pause: routing rules, A/B arms, fallback entries, budget routes and guardrail redirects. An emergency override never lifts it.
- Changing it needs the Manage approved destinations permission, which Compliance officers have by default.
Region rules Enterprise¶
A region rule says "calls from here stay within this area" on the organisation, an environment, a team, an application, a person or agent, or a key. What Enterprise includes depends on the features your licence includes.
- Only models that run within the area are offered or used at that level. Model pickers list the others as "Runs outside the area a region rule allows".
- A lower level can only tighten the area above it.
- Also require these agreements keeps calls to providers that hold each chosen agreement today: a HIPAA business associate agreement, a PCI DSS attestation, a GDPR data processing agreement. An agreement past its end stops counting.
- A refused call says both places in Request logs: "Refused: processed in US, outside EU."
- You can set one where you make things: a new team, agent or environment has Keep calls in a region.
A compliance route sends one model to an approved deployment (gpt-5 → the EU deployment, say) always, beats every
other rule, and can't be exempted from. If a key can't use its target, that key's calls are refused, never sent
elsewhere.
After a downgrade, nothing leaks. Region rules that already exist are kept and enforced when a licence lapses or an installation moves to Community, so calls that had to stay in the EU still do.
flowchart LR
Call[Call from a key] --> Approved{On the approved list?}
Approved -->|no| R1[Refused]
Approved -->|yes| Region{Runs within the<br/>area a region rule allows?}
Region -->|no| R2[Refused: processed<br/>outside the area]
Region -->|yes| Agree{Provider holds the<br/>agreements required?}
Agree -->|no| R3[Refused]
Agree -->|yes| Go[Sent to the provider]

These rules reach AI requests sent through the gateway only, not your other systems or AI calls that don't go through Vidai.
Related¶
- Providers and models: placing providers, and their agreements
- Routing and fallback: routing only ever sends a call inside the allowed area
- Policies and regulations: region rules as parts of a named policy
- Guardrails: what a call may contain, the other half of data governance
- Rules at levels