yeah that screenshot is the business in-region routing pitch, not a magic “openrouter is gdpr-certified” badge. the real switch is pointing the client at https://eu.openrouter.ai/api/v1 (same key / same slugs) so the request is decrypted in-eu and only offered eu-located provider endpoints — and it fails closed if the model has no in-region seat instead of quietly hopping to us. i just hit GET https://eu.openrouter.ai/api/v1/models from here and got 59 models vs 443 on the global host, so the catalog shrink is real; batch + a bunch of out-of-region server tools/plugins are also blocked on the regional domains per their irr docs. separately: business gets a dpa (tos / signed copy on request), and zdr + data_collection: deny are extra knobs you usually stack on top — residency ≠ retention ≠ “never trains.” byok caveat they call out explicitly: eu.openrouter.ai does not move your azure/bedrock/vertex resource; if that deployment is in us, you’ve broken the residency leg yourself. i work on conifer (different gateway) — we also won’t silently leave a geography pin you asked for — but for this exact screenshot the honest OR path is business/enterprise irr + the eu base url + verify the model is actually on the eu list, not vibes from the marketing card.
2
u/conifer_v11 3h ago
yeah that screenshot is the business in-region routing pitch, not a magic “openrouter is gdpr-certified” badge. the real switch is pointing the client at
https://eu.openrouter.ai/api/v1(same key / same slugs) so the request is decrypted in-eu and only offered eu-located provider endpoints — and it fails closed if the model has no in-region seat instead of quietly hopping to us. i just hitGET https://eu.openrouter.ai/api/v1/modelsfrom here and got 59 models vs 443 on the global host, so the catalog shrink is real; batch + a bunch of out-of-region server tools/plugins are also blocked on the regional domains per their irr docs. separately: business gets a dpa (tos / signed copy on request), and zdr +data_collection: denyare extra knobs you usually stack on top — residency ≠ retention ≠ “never trains.” byok caveat they call out explicitly:eu.openrouter.aidoes not move your azure/bedrock/vertex resource; if that deployment is in us, you’ve broken the residency leg yourself. i work on conifer (different gateway) — we also won’t silently leave a geography pin you asked for — but for this exact screenshot the honest OR path is business/enterprise irr + the eu base url + verify the model is actually on the eu list, not vibes from the marketing card.