Data residency & compliance
GDPR does not literally require EU storage — it requires an adequate level of protection, and EU storage is the simplest way to prove it. Here is where data lives by default, and the three levers that move it into the region you need: EU, USA or Asia.
↑ these are the defaults — the three levers below move each one into your region
Three levers to put data where you need it
BYO storage (S3)
Point FodyChat at your own S3-compatible bucket (AWS / MinIO / R2 / B2) in any region — eu-central-1, us-east-1, ap-southeast-1 — and files are written straight there, never to our bucket.
BYOK (bring your own AI)
Route the model calls to a provider and region you choose — Azure/OpenAI in the EU or US, Anthropic, or your own OpenAI-compatible endpoint in your data centre.
Self-host
Run the whole stack — worker, database, storage, embeddings — on your own Cloudflare account or infrastructure, in your region, with your keys. Maximum control for regulated markets.
EU · USA · Asia
| Region | Files | AI | Full control |
|---|---|---|---|
| EU | BYO S3 eu-central-1 | BYOK (EU provider) | Self-host in EU |
| USA | BYO S3 us-east-1 | BYOK (US provider) | Self-host in US |
| Asia | BYO S3 ap-southeast-1 | BYOK (local provider) | Self-host in-country |
EU
Works out of the box: R2 files are placed in the EU (location hint) and D1/Vectorize/KV are Cloudflare-managed. For strict data residency add BYO S3 (eu-central-1) + BYOK, or self-host in the EU.
USA
No single federal privacy law — California's CCPA/CPRA plus sectoral rules (HIPAA, GLBA). Keep files in the US with BYO S3 (us-east-1) and AI with a US provider (BYOK); EU→US transfers ride the EU-US Data Privacy Framework for certified providers.
Asia
Requirements differ: Singapore PDPA, Japan APPI, South Korea PIPA — and China's PIPL is the strictest (local storage + a cross-border security assessment). Self-host in-country, or BYO S3 in a local region with a local AI provider.
The honest legal nuance
- GDPR ≠ EU-only storage. It requires "adequate safeguards"; EU storage is the easiest to demonstrate. Transfers outside the EEA use Standard Contractual Clauses, adequacy decisions, or (for the US) the EU-US Data Privacy Framework.
- We're the processor. The customer running the widget is the controller and decides the lawful basis and retention; FodyChat follows instructions and deletes on request.
- We don't over-promise. On the default SaaS plan the chat and AI are not end-to-end encrypted and text passes through our backend; "data never leaves your infrastructure" is true only on self-host / BYOK.
- A DPA is available on request, and an admin endpoint exports a tenant's data for access/portability requests.
- EU placement is a hint, not yet a guarantee. Our default R2 bucket uses a best-effort EU location hint; a hard guarantee is an R2 jurisdiction (eu), a pinned D1 location and a KV regional tier — we switch these on when a regulated customer needs them.