Skip to main content
Skip to guide content

Transfers · 03 Editorial guide

Cross-Border Data Transfers and Foreign AI Providers into China

A transfer path is a gate. Architecture slides are not a filing.

First job Name the transfer route before promising a system architecture or a date.

Start here

Decision railChina-facing? → operator → telecom/cloud → AI filing → data export gate → launch
See routing facts
Do not promise a cutover before the export gate is named

A missed CAC or SCC step can move the date. This is a compliance clock, not a safety strip.

Open the transfer roadmap

Start here

Key considerations

The first questions are about urgency, governance and preservation — before collection expands or interviews begin.

  1. What leaves China, and to whom?
  2. Which mechanism is even plausible?
  3. What clock sits in front of go-live?

Direct answer

What this page decides

Owner
02

This page owns PIPL export gates and AI05 routing: if a foreign model or API is China-facing, ask (1) is there a China operator, (2) telecom/cloud, (3) algorithm/genAI filing, (4) data export, (5) launch. Do not invent SCC thresholds. FDI sector L4 owns VATS/ICP access.

At a glance

Which fact changes the next route

Use the fact that changes ownership or urgency to decide the next move.

Facts that change the next investigation route
QuestionWhy it mattersNext route
Only HR data to HQ?Classic transfer file.This L4’s existing transfer routes.
Offshore LLM, China users?AI05.Rail above + FDI sector.

Scope

What this page owns — and what it does not

Transfers + AI05.
ExclusionsNSR (FDI); export-controls of models as dual-use (export-control centre).

Practical workflow

Action, evidence, legal gate, output

Practical workflow
ActionDocuments / evidenceLegal gateOutput
Is it a China-facing service?Users, language, payment, serversIf no, still may export PI of employeesFacing memo
Name the China operatorWFOE vs noneFDI/telecom if providingOperator
Pick the export mechanismCurrent CAC pathsNo memorised volume numbersGate
AI filing overlayProgramme L4If public genAI/recommenderFiling owner

Documents

What to gather before the next call

These items help clarify the file; they are not a legal requirement list.

Documents to gather before instructing counsel
ItemWhy neededWho holds itRisk if missing
Data map and vendor locationsExportITSilent US tenant
Product geographyAI05ProductUnlicensed China offering

Common failure points

Where files usually break

  1. Pointing China users at a US API and calling it ‘SaaS’ with no transfer or telecom analysis.

FAQ

Narrow follow-ups owned by this page

Does an SCC replace algorithm filing?

No. Different regimes. Sequence them.

Decision map

Keep the question bounded.

  1. Describe the flowCategories, volume band and overseas recipient type.
  2. Pick a candidate pathAssessment, SCC, certification or exemption test.
  3. Place it on a clockDo not promise a cutover before the gate is named.

Timeline

Sequence and clocks that change the next action.

  1. Before architecture lockRecipient and volume facts that change the path.
  2. Before go-liveFiling or contract steps that must exist.
  3. After go-liveOngoing records and change control.

Regulatory gates

Approvals that can hold signing or closing.

This map does not decide whether a filing is required on your facts.

CACSecurity assessment

When an assessment is the plausible mandatory path.

SCCStandard contract

When the working mechanism is a China standard-contract filing for this transfer, not a generic export slogan.

CertCertification

When certification is in view.

TestExemption / threshold

When a published test may change the path — still a test.

Quick answers

Need the short version? Start with one narrow question.

These explainers answer one question. They do not replace this topic route or a deep guide.

Curated resources

Open the asset that matches this job.

Helpful to prepare

Facts that make the next conversation clearer.

These items are orientation aids, not a legal requirement list.

Overseas recipients and system names at a high levelCandidate mechanismTarget go-live or HR/payroll date

Counsel hand-off

What to bring when you instruct

Instruct data counsel plus FDI if you are providing a service into China. Bring: architecture diagram and user geography.

Local context

Add the city when regulator practice changes.

CAC and industry-regulator practice can differ after the national transfer or cybersecurity question is identified.

Open city and province guides

Counsel hand-off

Need data-privacy counsel?

This hub organises PIPL, cybersecurity and export questions. It does not decide whether a transfer is lawful or whether notice is required on your facts.

Find data-privacy counsel

Submit an initial enquiry

Need qualified counsel?

Move carefully. Move with a record.

Use the portal to identify counsel for this practice and related China-side issues.