Skip to main content
This page complies with GDPR article 13 on international data transfers. For each model in the catalog we indicate where data is processed, whether the region is configurable, and under which legal framework the transfer is authorized. The table is generated from the catalog, so new providers appear automatically.
🇪🇺 ZDR + European endpoint noteWhen you enable Zero Data Retention and select a provider with an EU endpoint (today: Google Vertex AI region europe-west* and OpenAI Azure Europe), data never leaves the EU — neither during processing nor after, since ZDR guarantees no provider-side persistence. This combination drives the international-transfer surface to zero.
  • EU/EEA — data does not leave the EU/EEA. Default framework (no international transfer basis required).
  • EU-US DPF — EU-US Data Privacy Framework, adequacy decision adopted by the European Commission on July 10, 2023. Covers EU→US transfers to DPF-certified organizations.
  • SCC — Standard Contractual Clauses (Decision (EU) 2021/914), module 2 controller-to-processor. Geek Hub signs SCC with each provider not covered by an adequacy decision.

​
Table by provider

​
OpenAI

Default region us-east. Europe available via Azure OpenAI Service and Europe data residency on Enterprise plan.

​
Anthropic

Processes in US Tier-2 datacenters. EU residency announced for H2 2026.

​
Google

Default us-central1. Vertex AI lets you select europe-west1, europe-west4 (NL) and 30+ regions. ZDR + Vertex EU = data stays in EU.

​
DeepSeek

Processes in Chinese datacenters. Not DPF-covered. Geek Hub signs SCC module 2.

​
Moonshot

Processes in China. Not DPF-covered. SCC applicable.

​
xAI

​
fal.ai

Meta-provider; actual processing happens in the underlying provider’s region.

​
Activating European endpoints

For now, selecting an EU region for Google Vertex AI is a gateway routing config (contact us). A self-service selector is being built in /dashboard/settings to pin region per API key.