Skip to main content
Skip to guide content

PIPL · 01 Editorial guide

PIPL Scope, Algorithm Duties and AI Training Data (Personal Information)

PIPL attaches to processing facts, not a system label. Classify the information, handler, purpose, lawful basis, sensitive-data trigger and recipient before asking whether consent or an export mechanism is required.

First job Identify what is processed, who is the handler and which PIPL duties actually attach.

Start here

Decision railwhat data → handler role → PI or not → AI/algorithm overlay → transfer gate → evidence
See routing facts

Start here

Key considerations

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

  1. What personal information is processed in or from China?
  2. Who decides purposes and means, and who acts only on instructions?
  3. Which lawful basis, sensitive-information rule or overseas-recipient duty is relied upon?

Direct answer

What this page decides

Owner
02

This page owns PIPL: what is personal information, who is the handler, notice/consent and core duties. AI01 algorithm filing and AI04 training-data PI are spokes here, not a new L3. If the model trains on personal or sensitive PI, PIPL (and often Data Security Law) attach before any ‘AI regulation’ slogan. Copyright in training corpora is IP. Overseas model APIs facing China users are Cross-border transfers + FDI sector overlay (AI05). Supporting: /china-consumer-digital-compliance-algorithm-pipl. Do not invent filing catalogues or PI volume thresholds.

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
Need CAC algorithm filing?Public recommendation/generation duties.Programme L4 for the filing file; this page for PI overlay.
Training on user content?PI + copyright.This page + IP training-data spoke.
Foreign model, China users?AI05.Cross-border transfers L4.
Labelling generated content?AI03.Programme L4 labelling row.

Scope

What this page owns — and what it does not

PIPL core + AI PI overlay. No new AI hub.
Exclusionscopyright (IP); VATS/ICP (FDI sector); financial-sector AI (Fintech L4 overlay).

Practical workflow

Action, evidence, legal gate, output

Practical workflow
ActionDocuments / evidenceLegal gateOutput
Inventory processingSystems, vendors, modelsPI vs non-PI vs sensitive PIMap
If a model or recommender is in scopeUser-facing vs internalAlgorithm/genAI rules may add dutiesAI overlay list
Training-data PISources, consent, sensitive PIDo not scrape firstPI training file
Export or APIWhere the model sitsTransfers L4Route

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
Processing inventory including modelsPIPL mapPrivacyShadow AI
Training-source logPI provenanceProductUnlawful PI set

Common failure points

Where files usually break

  1. Calling internal ChatGPT use ‘not PIPL’ because it is ‘just a tool’.

  2. Standing up a second /china-ai-law hub.

FAQ

Narrow follow-ups owned by this page

Is there a China AI legal-guides L3?

No. Data is the parent for PI/algorithm/filing; IP for copyright; FDI for access; Fintech for licensed financial models.

Decision map

Keep the question bounded.

  1. Map the processingMap collection, use, storage, disclosure and deletion by purpose, system, person category and location.
  2. Name the handlerSeparate independent, joint and entrusted processing and allocate notices, contracts, rights and incidents.
  3. Test the lawful basisConsent is one basis, not the only basis. Record necessity, separate-consent and impact-assessment triggers.

Regulatory gates

Approvals that can hold signing or closing.

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

HREmployee data

Document necessity under lawfully adopted employment rules or collective contracts; do not convert the HR basis into unlimited reuse.

SensitiveSensitive personal information

Specific purpose, sufficient necessity, strict protection, additional notice and separate consent where consent is the basis.

FaceFacial recognition

Test necessity and a non-face alternative, local storage, PIPIA, separate consent and the 100,000-person filing threshold.

ExportOverseas recipient

Move the flow to the transfer route; a PIPL lawful basis does not itself clear export formalities.

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.

Processing inventory in non-confidential termsChina entity and overseas affiliates involvedLawful basis, notice and separate-consent matrixSensitive information, minors, biometrics and facial-recognition inventoryRights-request, retention, deletion and PIPIA evidence

Counsel hand-off

What to bring when you instruct

Instruct privacy counsel (IP if corpus is copyrighted). Bring: systems list, model use, and whether users in China see the output.

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.