Geo-location routing
Geo-location routing
Restrict routing to vendors in specific countries or regions for data-sovereignty
Geo-location routing limits which vendors serve your requests, by location or by vendor. Use it for EU-only routing, to exclude CN-hosted vendors, or to keep a vendor out until its sub-processors are approved.
How vendors are tagged
Each vendor has a country_code (ISO 3166 alpha-2, such as US or FR) and a geo_region (such as NA, EU, APAC, or CN). A region token matches either tag. Vendor terms lists each vendor’s tags; the dashboard offers only tokens current vendors carry.
Configure restrictions
In Configure → Request settings → Routing restrictions (dashboard), vendors and regions each offer All, Only selected, or All except selected. Changes need Manage organization settings and are recorded in the audit trail as ORG_SETTINGS_UPDATED.
A list can’t share entries with its opposite, and unknown vendor slugs or region tokens are rejected on save. Restrictions apply to every model a request or routing policy tries, including BYOK traffic. They restrict where data is sent, not where requests come from.
Per project and customer
Projects and end customers can override these lists and zero data retention on their Controls tab or with PUT /v1/projects/{id}/controls and PUT /v1/customers/{id}/controls. {"allowed_regions": ["EU"]} makes one project EU-only. An override replaces the organization’s list rather than merging. Scoped controls covers resolution order, who can relax a control, and the request format.
The controls API also accepts vendor_routing_preference, a preferred-vendor list that reorders eligible vendors without excluding any, so it never fails a request.
When no vendor matches
If restrictions leave a model with no eligible vendor, Gateway returns:
In a fallback or intelligent routing policy, that target is skipped for the next. With ZDR on, this can return zdr_vendor_unavailable instead.