QuestionChina

What should an app collect as necessary personal information in China? Direct answer

Collect no more than the personal information necessary for the app's actual basic function, using the 2021 rules for the matching app category. A listed field may be permitted for that function; the list does not require the app to collect it.

Keep the basic function available when a user declines non-necessary information, and apply PIPL separately to every collection and use.

Author
Sorena AI
Published
Jul 5, 2026
Updated
Jul 24, 2026
Questions
2

Structured answer sets in this page tree.

Primary sources
2

Cited legal and guidance references.

Publication metadata
Sorena AI
Published Jul 5, 2026
Updated Jul 24, 2026
Overview

China's necessary-personal-information rules took effect on May 1, 2021. Collect no more than the for the app's actual basic function. The rules define that term as consumer-side personal information without which the basic function cannot operate and give category-specific scopes for 39 common app types, including installed apps, preinstalled apps, and mini programs.

Search this module

Find a question or answer quickly

2 of 2 questions
Question 1

Match the app to its basic function

Start with what the user is obtaining, not the app's marketing label. Match that basic function to the 2021 category and map each proposed field to the listed scope. If the app provides several distinct basic functions, document the category and necessary scope for each function rather than treating the broadest category as permission for the whole product.

The list sets the outer scope of information treated as necessary for each stated basic function. It does not require collection of every listed item when the app can deliver the function without it. It also does not make optional analytics, advertising, personalization, contacts, background permissions, or SDK events necessary merely because they support the business.

  • Map navigation: location, departure point, and destination are listed for the basic location-and-navigation function.
  • Online shopping and food delivery: the listed scope includes a registered mobile number, recipient name, address and contact number, and payment time, amount, and channel.
  • Instant messaging: the listed scope includes a registered mobile number plus the account and instant-messaging contact-account list.
  • Functions requiring no personal information: the rules list news browsing, online audio or video playback, short-video search and playback, browsers, input methods, photography or beautification, and several other categories as needing none for the stated basic function. Requiring account registration or a device permission before those basic functions would conflict with that category result unless another controlling rule applies.
  • Health, finance, transport, and other categories can include information that is sensitive under PIPL. The category table does not remove the separate sensitive-information duties.
Citations
Question 2

Build and test the collection map

For every field, device permission, SDK, and event, record the product function, collection timing, recipient, purpose, and whether the item is necessary for the basic function. If it is outside the category scope or the function works without it, keep it out of the mandatory flow and do not block the basic function when the user refuses.

Then apply PIPL. Identify the processing basis, give the required notice, keep collection within the minimum necessary range, use the shortest necessary retention, and address sensitive personal information, children under 14, security, individual rights, and PIPIA triggers.

  • Category decision: basic-function description, selected 2021 category, any multi-function split, and product owner.
  • Field map: field or event, collection source, user action, basic function, necessity rationale, recipient or SDK, retention, and deletion.
  • Refusal test: evidence that declining each non-necessary field or permission leaves the relevant basic function available.
  • PIPL overlay: basis, notice, consent, sensitive-information classification, child treatment, security controls, rights path, and PIPIA where triggered.
  • Change trigger: reassess when a function, SDK, permission, field, use, recipient, or collection timing changes.
Citations
Operationalize the requirement

Prepare the PIPL and data export evidence file

Sorena AI helps turn the answer to "What should an app collect as necessary personal information in China?" into assigned controls and retained evidence.

Primary sources

References and citations

cac.gov.cn
Referenced sections
  • PIPL supports the additional processing-basis, notice, minimization, retention, sensitive-information, child, security, rights, and PIPIA checks.
Related guides

Explore more topics

App minimum necessary personal information by category
App category mapping page for common mobile app necessary personal information scope, using only categories supported by the official source.
China app personal information minimization
How to map app category, basic functions, and necessary personal information under China mobile app personal-information rules.
China data export security assessment workflow
Workflow for screening data export security assessment triggers, materials, owners, and evidence records.
China personal information cross-border transfer routes
Compare China's current data-export exemptions, CAC security assessment, standard contract, and personal information protection certification routes.
China personal information standard contract filing workflow
Workflow for the PIPL standard contract route, assessment, filing package, and cited evidence.
China PIPL compliance checklist
China PIPL compliance checklist covering scope, processing bases, notices, sensitive information, rights, vendors, impact assessments, incidents, and exports.
China PIPL deadlines and compliance calendar
Calendar China PIPL effective dates, recurring audits, privacy-officer reporting, impact-assessment retention, and data export filing and renewal deadlines.
China PIPL penalties and enforcement exposure
Understand PIPL corrective orders, serious-violation fines, responsible-person exposure, civil claims, public-interest actions, and data export enforcement.
China PIPL privacy notice and consent checklist
China PIPL checklist for privacy notices, valid consent, separate consent, sensitive information, children under 14, withdrawal, and rights requests.
China PIPL requirements
China PIPL requirements from scope and processing basis through notices, rights, security, impact assessments, incidents, vendors, and data exports.
China PIPL vs CCPA/CPRA: Requirements Compared
Compare PIPL and CCPA/CPRA scope, consent and opt-out rules, rights, assessments, data exports, breach duties, and penalties.
China PIPL vs EU GDPR: Requirements Compared
Compare PIPL and GDPR scope, roles, legal bases, rights, impact assessments, breach deadlines, international transfers, and penalties.
China PIPL vs Singapore PDPA: Requirements Compared
Compare PIPL and Singapore PDPA scope, roles, consent alternatives, rights, breach duties, overseas transfers, and penalties.
China Privacy Law FAQ
Practical answers on China's PIPL: scope, legal bases, sensitive information, separate consent, vendors, PIPIA records, app minimization, and export routes.
How should vendor contracts handle entrusted processing under PIPL?
A PIPL entrusted-processing contract must define the purpose, duration, method, personal-information categories, safeguards, and both parties' duties. See the required terms and supporting records.
Is PIPL the same as GDPR?
No. China's PIPL and the EU GDPR overlap on core privacy controls, but differ in territorial scope, legal bases, roles, sensitive data, impact assessments, and transfer routes.
PIPL automated decision-making and personalized recommendations
PIPL checks for automated decisions, personalized recommendations, marketing, differential treatment, explanations, refusal rights, and impact assessments.
PIPL breach response and notification
PIPL incident workflow for immediate remediation, authority and individual notices, the narrow individual-notice exception, vendor coordination, and evidence.
PIPL cross-border transfer route selector
Step-by-step selector for China's data-export exemptions, CAC security assessment, standard contract, and personal information protection certification.
PIPL entrusted processing and vendor contracts
How to document entrusted processing, vendor responsibilities, contract controls, and evidence under PIPL.
PIPL impact assessment template
Template fields for a China personal information protection impact assessment and export/entrusted-processing evidence.
Sensitive personal information and separate consent under PIPL
How to identify sensitive PI triggers, separate consent, minors, additional safeguards, and evidence records.
What counts as sensitive personal information in China?
PIPL uses a harm-based test for sensitive personal information and lists examples such as biometrics, health, financial accounts, location traces, and all personal information of children under 14.
What is separate consent under PIPL?
Separate consent under China's PIPL is a distinct consent for a specified processing activity. See when it applies, what notice must come first, and what evidence to keep.
What records should we keep for a PIPL impact assessment?
A PIPL impact-assessment file should preserve the Article 55 trigger, processing facts, Article 56 analysis, safeguards, decision, and processing record for at least three years.
When can a company use the China standard contract route?
Use China's standard contract route only after applying the 2024 exemptions and confirming that no CAC security assessment is required. See current thresholds, filing steps, and change triggers.
When does a China PIPL security assessment apply?
A CAC data export security assessment applies to CIIO exports, important data, and specified high-volume personal-information exports after the 2024 exemptions are applied.