Data Residency

Choose where requests from everyone in your organization may be processed, and see which models a region would cost you before you switch

Some organizations can send prompts anywhere their AI provider serves them. Others have data or contracts that require processing in a particular country. Data residency sets where requests from everyone in your organization are processed. It applies to every user and every key at once, and Dispatch shows you which models a region would take away before you commit.

Data residency is on the Data residency tab of the Organization page.

You're responsible for this choice. In the console's words: "With Global, requests may be processed in DarcyIQ's approved countries outside the U.S. If your data or contracts require U.S. processing, choose U.S. only."

The Options

Option	What it means
Global	Requests may be processed in DarcyIQ's approved countries, including outside the U.S. The full model catalogue is available.
U.S. only	Requests are processed and stored only in U.S. data centers.
EU only	Requests are processed and stored only in EU data centers. Marked Coming soon and not yet selectable.

The Trade-Offs

Choosing a region narrows what your organization can do on its very next request. When you choose U.S. only, the confirmation says:

Requests will be processed and stored only in U.S. data centers. Some models may be unavailable and costs may be higher, which can reduce your savings. Applies to new requests right away. Requests through your own provider keys follow your provider agreements.

• Fewer models: A tier with no models in the region stops being available. A tier with only some of its models in the region keeps working on fewer of them.

• Possibly higher costs: Region-restricted processing can cost more, which can reduce your savings.

• Your own provider keys: Requests that run on a provider key you've brought follow your agreement with that provider.

When you switch back to Global, the full model catalogue becomes available again. That change also applies to new requests right away.

Changing the Region

1

Click the option you want Dispatch opens a confirmation, for example Switch to U.S. only?, explaining what the change means.

2

Review what you'd lose For a region, Dispatch checks your organization's tiers and lists them by name under Will become unavailable and Will run on fewer models. If nothing changes, it says "Every model your team uses stays available." If the check can't run, it warns that some models may stop working once the region is on.

3

Click Accept New requests from everyone in the organization follow the new setting straight away.

The Model Access tab and the Models page follow the new setting, so tiers that aren't available in your region drop off them.

History

Every change is recorded under History, with who made it, what it changed from and to, and when. Until the first change, the tab says "This setting has never been changed."

Next Steps

Goal	Documentation
See which models are still available	Model Access
Use your own provider accounts	Provider Keys
Check what your team can call	Models