Three decisions, not one approval
A transfer mechanism does not answer every notice-and-consent question. An assessment extension does not automatically cover a new purpose or recipient. Recruitment necessity depends on the actual hiring decision, not simply whether an employer belongs to an international group.
The tables and examples below are original research aids, not official application forms. For each decision retain the facts, source clause, evidence, owner and unresolved question. That makes the review useful to a colleague who was not present when it was prepared.
Separate notice from the basis for consent
Question 1 says transfers under PIPL Article 13(1)(2)–(7) do not require consent, but export notice remains. Sensitive-information notice also addresses necessity and effects. Where separate consent is required, blanket authorisation is insufficient.
Prepare a recipient-specific notice record. If the product team uses a cloud service's brand but the contract names another legal entity, resolve the mismatch before relying on the notice. The privacy policy, consent log, signed document and actual system should describe the same activity.
| Working check | Useful evidence |
|---|---|
| Recipient and contact | Legal name mapped to service/vendor names; a contact channel that works. |
| Purpose, method and fields | A field list consistent with the contract and live system, rather than 'business operations' alone. |
| Rights and consent | A usable rights route, notice version and the recorded basis for requiring or not requiring consent. |
Review every extension condition
Question 2 requires cumulative checks: unchanged activity and parties; applicable 20% limits for people and important-data scale; compliant legal documents; and three years within the approval without major data-security incidents. Compare the future three-year projection with the approved preceding three-year quantity.
The third-edition release notice provides an application window within the 60 working days before expiry. Extension requires approval; filing an application does not automatically grant another three years.
| Review area | Evidence comparison |
|---|---|
| Activity and parties | Approved purpose, scope, processor and recipient against actual and planned arrangements. |
| Growth basis | Approved baseline, projection period, counting method and relevant important-data unit. |
| Documents and conduct | Signed document versions, change logs, incident record and evidence of compliance with the approval. |
Worked example: 20% is not a general allowance
Hypothetical facts: an approval covers 500,000 natural persons over the preceding three-year period. A comparable future three-year projection of 590,000 is an 18% increase: (590,000 − 500,000) ÷ 500,000 × 100. A projection of 600,000 is 20%; 610,000 is 22%. These numbers illustrate the arithmetic, not an approval decision.
Do not substitute a lower actual-use figure for the approved baseline. Explain how the same individual appearing in more than one annual file is handled; do not silently change the unit from people to accounts. For important data, do not mix bytes and records. Where the approval supplies no usable baseline, seek clarification rather than choosing a favourable denominator. A zero baseline cannot be used in this percentage formula.
An 18% projection does not cure a changed recipient, new purpose or deficient legal document. Keep the calculation beside the complete eligibility review, not in place of it. The extension baseline is also not the separate annual threshold used to select a transfer mechanism.
Ask who participates in the hiring decision
Question 3 ties necessity to the overseas recipient's hiring role. No participation means no necessity on that basis; direct participation requires the minimum people and fields needed. Route, notice and PIPIA remain separate checks.
Illustrative case A: the domestic team makes all hiring decisions, while headquarters requests every CV for a global talent dashboard. Group membership does not explain why the CVs are needed. Consider whether aggregate staffing information could meet the reporting purpose.
Illustrative case B: an overseas engineering lead interviews the final candidates. Map that decision to the shortlisted people and relevant qualifications. It does not follow that every unsuccessful applicant's identity scans or unrelated medical information must also be exported. Reducing a dataset is a preparation measure, not automatic proof that every legal condition is met.
A reviewable output, not a generic compliance label
Use one decision record with activity, source location, baseline, evidence owner, conclusion and open question. Attach the recipient map, notice/consent record, growth calculation if relevant and the next review trigger. Assign someone to resolve each open item rather than labelling the whole transfer 'compliant'.
For a change request, compare the old and new facts before editing a template. A document that looks complete but contradicts the production system is weaker evidence than a clear record of a gap and its resolution. The official Chinese sources control; these examples are not case-specific legal advice.
Official sources & revisions
- CAC July 2026 data-export Q&A, questions 1–3
- CAC third-edition assessment filing guide release notice, extension and online filing paragraphs
: Expanded the existing guide with bilingual evidence matrices, growth calculations and recruitment scenarios while retaining its URL.
Examples and working tables are original research aids, not official forms or legal advice.
Suggest a correction