tokencoup
Edition: International · 国内版 Language: ZH · EN
Get API keys

Cross-border AI: the three data flows, explained without the fear

2026-11-13

Cross-border AI: the three data flows, explained without the fear

If your team is routing prompts from the US or Europe to a Chinese-hosted model

family, "data residency" stops being a compliance checkbox and becomes your

actual architecture. Here is the model we implement, and why.

The three flows

Every request your product makes belongs to exactly one of these:

Baidu Qianfan international nodes. Data does not touch the mainland.

This is the primary flow and the only one that supports resale.

keys. A compliant path that serves China only.

mainland because someone wired a domestic key into an international route.

This is the flow we block at the gateway, permanently, with a 403. It cannot

be fixed by policy; it is fixed by making the code path impossible.

Why S3 deserves a code-level block

Policy says "never". Engineers ship what policy assumes impossible. A gateway

that only documents the rule will eventually route a domestic key across the

border, because the person writing the integration forgot which pool the key

came from. Fail-closed validation (unregistered edition = unknown = reject) is

the only enforcement that survives a Friday deploy.

What GDPR and PIPL actually add

SCCs plus a transfer impact assessment and supplementary measures. That is

paper, and paper is cheap to get wrong.

matter if you collect mainland personal data and ship it out. Under the

de-minimis thresholds, keeping volume low is itself a compliance strategy.

Our current position: the international data-residency claim is written down as

a design goal pending written confirmation from Baidu, not as an accomplished

fact. You can read exactly what we claim, and where it is still unconfirmed, on

the cross-border page.

The part that is your job, not ours

Pick your entity's registration location before launch. Singapore or Hong Kong

for the international business puts S1 outside PIPL export jurisdiction entirely;

a mainland entity puts it inside. That single decision changes which compliance

regime you live in, and no amount of engineering makes it up later.

For the legalistic version, see GDPR, PIPL and your gateway traffic.

Back to blog