Skip to content
Back to Scenario Playbooks
China (Mainland)GenAI & foundation modelsAI agentsComputer visionEnterprise SaaSEmbodied AI & robotics

China-side readiness before going global: algorithm and LLM filings, content labelling and the outbound data route

Before opening overseas markets in earnest, a China-based AI company must first settle its domestic filings, content labelling and outbound data route — a precondition for lawful operation onshore and material that overseas customers, investors and listing reviewers check item by item.

Verified against official sources · 2026-09-12Verified against official text

Prerequisites

  • The domestic entity’s business model is settled: providing generative AI services to the public versus supplying technical capability to enterprise customers only — which directly drives whether the service has public-opinion or social-mobilisation capability, and therefore the security assessment and filing duties.
  • You can list every data leg that touches outside China: overseas customer data coming in, domestic data going out, overseas subsidiaries accessing onshore systems, and offshore cloud and CDN nodes.
  • You know there are three outbound routes (security assessment filing, standard contract filing, personal information protection certification) plus the exemptions, and that threshold triage precedes route selection.
  • Stage 4 (the outbound route) is the critical path here: the review cycle for a security assessment filing runs in months and must start first.

Stages (26–46 weeks, estimate)

  1. 1. Stage 1 — Data asset inventory, classification and grading

    3–5 weeks

    Establish exactly what data you hold and what each category is — the input to every later determination. Build the classification and grading register and identify important data. One practically crucial rule applies here: where the relevant authorities or region have not notified you, or publicly published a determination, that data is important data, the handler need not declare it as important data for outbound transfer. Many companies, unaware of this, push themselves into the security assessment channel unnecessarily. In parallel, carry out personal information protection impact assessments for processing involving personal information and check the lawful conditions for providing personal information abroad item by item.

    Obligations in this stage

    Evidence to retain

    • · Data classification and grading register (category × grade × storage location × purpose × whether transferred abroad)
    • · Important-data determinations and their basis, recording whether a notification was received or a public catalogue entry exists
    • · Personal information protection impact assessment reports and the three-year retention arrangement
    • · Item-by-item checklist of the lawful conditions for providing personal information abroad
    • · Data-flow diagram (onshore systems, offshore systems, who accesses them and by what route)

    Common blockers

    • · Self-designating all sensitive data as important data: this pushes legs that could have used the standard contract or an exemption into the security assessment channel, costing months for nothing.
    • · Inventorying business databases but not logs and backups: logs, backups, monitoring and data warehouses are the hidden conduits most often questioned in outbound review.
    • · Completing impact assessments without retaining them: the law requires three-year retention, and missing records read as never having done the assessment in both inspections and diligence.
  2. 2. Stage 2 — Algorithm filing, generative AI filing and security assessment

    6–12 weeks

    Services with public-opinion or social-mobilisation capability must undergo a security assessment and complete algorithm filing; algorithm recommendation service providers should file within ten working days of starting to provide the service and publish the filing number; deep synthesis services carry their own filing plus a security assessment for new products, applications and functions. The substance of a filing package is explaining the lawfulness of training-data sources, data annotation governance and content safety mechanisms, so this stage also organises the lawful-source and IP chain for training data, the annotation rules and the annotator training records into submittable form. Filing is not one-off: material changes in model capability or functional scope require the process to be run again.

    Obligations in this stage

    Evidence to retain

    • · Filing package (service and algorithm particulars, security assessment report, content safety mechanism description)
    • · Lawful-source statement for training data and the chain of authorisations
    • · Data annotation rules, quality assessment records and annotator training records
    • · Filing receipt and screenshots showing where the filing number is published
    • · Algorithm security management system documentation addressing the eight required internal systems
    • · Security assessment records for new products, applications and functions

    Common blockers

    • · Treating filing as submitting paperwork: the package must be backed by a content safety mechanism that actually runs, and spot checks and follow-up enquiries verify that it does.
    • · A broken authorisation chain for training data: missing authorisation documents for purchased datasets, crawled data and partner data is the most common reason for supplementary-filing requests.
    • · Not re-assessing after model iteration: material changes in capability or function without re-running the process are treated during listing or diligence as a filing status inconsistent with reality.
  3. 3. Stage 3 — Implementing AI-generated content labelling

    3–5 weeks

    The labelling measures require two layers: an explicit label placed per modality in the specified position (and preserved in exported files), and an implicit label in the file metadata. The service agreement must explain the labelling rules, and outputs without an explicit label require logs retained for at least six months. Labelling material is submitted with filings and security assessments and must conform to the mandatory national standard. For a company preparing to go global the value here is double: it is a statutory duty onshore and it maps neatly onto the EU’s Article 50(2) machine-readable marking and California’s latent/manifest disclosure requirements, so one implementation serves three markets — while noting that the technical bases and placement requirements are not identical.

    Obligations in this stage

    Deliverables

    Evidence to retain

    • · Implementation note for explicit labels per modality, with interface and exported-file examples
    • · Field specification for implicit (metadata) labels and sampling results
    • · Text of the labelling clauses in the service agreement
    • · Log retention configuration for outputs without an explicit label (at least six months)
    • · Conformity mapping against the mandatory national standard
    • · Comparison table of labelling bases across China, the EU and California

    Common blockers

    • · Applying the label only in the preview interface so it is lost on export: the measures expressly require exported files to retain the label.
    • · Defining implicit label fields ad hoc instead of against the mandatory national standard: this draws a remediation request at filing.
    • · Assuming the domestic labelling implementation satisfies EU and California requirements: the technical bases and presentation requirements differ across the three, and each must be mapped rather than assumed equivalent.
  4. 4. Stage 4 — Outbound data route triage, filing and registration

    8–16 weeks

    Triage first, then choose the route, then file. Triage each leg against the thresholds in Articles 7 and 8 of the Provisions on Promoting and Regulating Cross-Border Data Flows, checking the exemptions first — and any reliance on an exemption must leave a checkable written basis rather than an oral judgement. On the security assessment route, complete the outbound risk self-assessment, file through the provincial cyberspace administration to the national authority, and track the review period and validity. On the standard contract route, complete the contract-specific personal information protection impact assessment, execute the contract strictly on the template annexed to the measures, and register within ten working days. On the certification route, define the certification scope and complete notification, separate consent and the impact assessment. Whichever route is used, notification, separate consent and the impact assessment cannot be skipped. Free trade zone negative lists may offer simplification and are worth assessing separately.

    Obligations in this stage

    Evidence to retain

    • · Outbound leg inventory and threshold triage conclusions (leg × data category × order of magnitude of data subjects × route)
    • · Written basis for any exemption relied upon
    • · Outbound data risk self-assessment report (security assessment route)
    • · Filing materials plus acceptance, review and decision records, including validity and re-filing triggers
    • · Standard contract executed on the official template and the registration receipt
    • · Notification text, separate consent records and the impact assessment report
    • · Mapping table of the mandatory clauses in the legal instrument with the overseas recipient

    Common blockers

    • · Letting the business pick the route by “which is fastest”: threshold triage is a legal determination, not an option, and the wrong route means the transfer is not compliant at all.
    • · Relying on an exemption with no written basis: exemptions are conditional, and an oral judgement is treated on inspection as no reliance at all.
    • · Scheduling the security assessment filing at the end of the project: the review runs in months, and validity plus re-filing triggers need long-term management, so a late start directly blocks the overseas launch date.
    • · Editing the standard contract clauses: the measures require execution on the annexed template, and substantive changes cause registration to fail.
  5. 5. Stage 5 — Technology export screening and science & technology ethics review

    3–6 weeks

    Two things that are easy to overlook entirely and costly when missed. First, any outbound technology transfer — establishing an overseas R&D centre, moving models and algorithms to an offshore subsidiary, technology licensing, and share reorganisations in going-global transactions — should first be checked against the Catalogue of Technologies Prohibited or Restricted from Export; restricted-category transfers require a technology export licence first. Identify at the same time whether any data is itself a controlled item. Second, science and technology activities involving human subjects, and listed activities, require ethics review: the company should establish a science and technology ethics (review) committee, listed activities additionally require expert re-review organised by the competent authority, and an annual report must be submitted to the national science and technology ethics management information registration platform.

    Obligations in this stage

    Evidence to retain

    • · Outbound technology transfer inventory and catalogue comparison records, covering overseas R&D centres and intra-group transfers
    • · Technology export licence application and decision, where restricted-category technology is involved
    • · Determination of whether any data constitutes a controlled item
    • · Establishment document and membership of the science and technology ethics (review) committee
    • · Ethics risk assessment and review application records; expert re-review records for listed activities
    • · Receipt for the annual report submission (due by 31 March each year)

    Common blockers

    • · Treating an overseas R&D centre as purely an HR and tax question: technology and people leave together, and technology-export compliance belongs up front.
    • · Believing only “selling technology” counts as technology export: licensing, equity investment and joint development can equally constitute outbound technology transfer.
    • · Running ethics review only when applying for research grants: activities involving human subjects conducted by the company itself are equally in scope and carry an annual reporting duty.
  6. 6. Stage 6 — Steady-state operation, incident reporting and annual upkeep

    3–5 weeks

    Freeze the domestic steady-state duties: appoint a personal information protection officer and conduct compliance audits as required; carry out and report periodic risk assessments as an important-data handler; report within 24 hours where a product or service security defect endangers national security or the public interest; remediate personal information breaches and notify both the authority and individuals; and retain network logs for at least six months. These duties share one characteristic — invisible day to day, decisive when something happens — and they are checked item by item in overseas customer diligence and listing review, so put them on the annual compliance calendar with named owners.

    Obligations in this stage

    Evidence to retain

    • · Appointment document and published particulars for the personal information protection officer
    • · Compliance audit plan and audit reports
    • · Important-data risk assessment report and submission receipt, where applicable
    • · Cybersecurity incident response plan and rehearsal records
    • · Log retention configuration evidence (at least six months)
    • · Contracts and processing records for outbound provision and entrusted processing, retained for three years
    • · Annual compliance calendar (duty × due date × owner × last completion)

    Common blockers

    • · Stopping once the outbound route is approved: security assessment results have a validity period, and defined events require re-assessment and re-filing.
    • · Purging contracts and processing records before three years: the regulations require three-year retention, and early deletion cannot be remedied at inspection.
    • · Writing the 24-hour reporting duty into a policy without rehearsing it: when it happens there is no time to work out the decision chain and reporting basis from scratch.

Common failure modes

  • · Treating domestic compliance as something to handle “after we go global”: filing status, outbound routes and labelling implementation are checked in overseas customer diligence, investor diligence and listing review, and retrofitting costs far more time than front-loading.
  • · Frightening yourself into the security assessment channel: data you have not been notified about and that does not appear in a published catalogue need not be declared as important data, so triage the thresholds before debating routes.
  • · Filings inconsistent with the live product: shipping functionality ahead of filing is the most common hard finding in diligence.
  • · Treating outbound compliance as a legal-only matter: it is fundamentally an architecture question (where data sits, who can access it, where logs and backups go) and cannot be done without engineering.
  • · Overlooking technology export and ethics review: establishing an overseas R&D centre, moving models to an offshore subsidiary and conducting activities involving human subjects each carry their own prior-review duties.
  • · Doing it once and never maintaining it: outbound assessments expire, filings need updating as models iterate, and compliance audits and annual reports run on their own cycles.

Sources (19)

Content as of 2026-09-12 · corpus 2026.09|Compiled from public official sources with links and review dates for compliance decision support. Rules change; have licensed professionals review before external disclosure, regulatory filing or contractual commitments.

GDPR · PIPL · CCPA control mapping
Traceable AI · cited when sourced
ISO 27001 alignment in progress
WCAG 2.1 AA accessibility target
China-side readiness before going global: algorithm and LLM filings, content labelling and the outbound data route · Scenario playbook | HaiWen HQ