---
title: "China app personal information minimization"
canonical_url: "https://www.sorena.io/artifacts/apac/china-privacy-law/app-personal-information-minimization"
source_url: "https://www.sorena.io/artifacts/apac/china-privacy-law/app-personal-information-minimization"
author: "Sorena AI"
description: "How to map app category, basic functions, and necessary personal information under China mobile app personal-information rules."
published_at: "2026-07-05"
updated_at: "2026-07-24"
keywords:
  - "China PIPL"
  - "Personal Information Protection Law"
  - "Data export"
  - "Standard contract"
  - "App privacy"
---
**[SORENA](https://www.sorena.io/)** - AI-Powered GRC Platform

[Home](https://www.sorena.io/) | [Solutions](https://www.sorena.io/solutions) | [Artifacts](https://www.sorena.io/artifacts) | [About Us](https://www.sorena.io/about-us) | [Contact](https://www.sorena.io/contact) | [Portal](https://app.sorena.io)

---

# China app personal information minimization

How to map app category, basic functions, and necessary personal information under China mobile app personal-information rules.

*Privacy* *China*

## China Privacy Law app personal information minimization

Minimize each field, permission, SDK event, use, and retention period against a clear purpose. For 39 common app types, the 2021 rules also define the information indispensable to the basic function.

An app must collect and use personal information only for a clear, reasonable purpose, keep the processing directly related to that purpose, and use the method with the least effect on individual rights. For 39 common app types, the 2021 provisions add a concrete test: necessary personal information is consumer-side information without which the listed basic function cannot operate. A user who refuses non-necessary information must still be able to use that basic function.

## Definitions

### Necessary personal information for an app's basic function

**Term:** necessary personal information

Necessary personal information is personal information about a consumer-side app user without which the app's stated basic function cannot operate normally. The 2021 provisions specify the basic function and necessary-information scope for 39 common app types; information about supply-side users is outside this particular definition.

**Why it matters here:** The category test narrows what may be treated as indispensable to the basic function. It does not require every listed field, authorize a different purpose, or replace PIPL's purpose, processing-condition, notice, retention, sensitive-information, security, and rights duties.

Sources:

- [Necessary Personal Information Scope for Common Types of Mobile Apps, Articles 2-5](https://www.cac.gov.cn/2021-03/22/c_1617990997054277.htm?ref=sorena.io)

## 1. Define the basic function and each additional purpose

Write the basic function in user terms, such as positioning and navigation, purchasing goods, booking transport, or playing online video. Then separate analytics, advertising, personalization, fraud prevention, support, regulatory checks, and convenience features. A broad label such as service improvement is not enough to show that a field is directly related or indispensable.

Match each basic function to the official 39-category table where a category fits. The table covers installed and preinstalled mobile apps and qualifying mini programs, and its necessary-information definition concerns consumer-side users, not service providers. The category provisions took effect on 1 May 2021; the separate app information-service provisions took effect on 1 August 2022.

- For a multi-function app, make a separate category and necessity decision for each basic function.
- For an unlisted function, apply PIPL's purpose, direct-relevance, minimum-impact, and shortest-necessary-retention principles instead of borrowing the nearest category.
- Record the user type. The category table's definition excludes supply-side personal information, which still requires its own PIPL analysis.
- Identify any sensitive personal information early because specific purpose, sufficient necessity, strict protection, additional notice, separate consent, and a pre-processing impact assessment may apply.

Sources for this answer:

- [Necessary Personal Information Scope for Common Types of Mobile Apps](https://www.cac.gov.cn/2021-03/22/c_1617990997054277.htm?ref=sorena.io) - Articles 2-5 define covered apps, consumer-side necessary information, the no-refusal rule, and the basic functions and scopes for 39 categories.
- [PRC Personal Information Protection Law](https://www.cac.gov.cn/2021-08/20/c_1631050028355286.htm?ref=sorena.io) - Articles 5-7, 13, 17, 19, and 28-30 support purpose limitation, minimum impact, transparency, processing bases, shortest necessary retention, and special handling of sensitive information.

## 2. Test every collection and use

Build the inventory from code and observed behavior, not only from the privacy notice. Include form fields, device permissions, software development kits, identifiers, inferred data, background events, logs, server-side enrichment, recipients, storage, and deletion.

- For each item, record the precise purpose, user action, collection point, source, recipient, processing basis, whether it is sensitive, retention period, and deletion event.
- For a listed basic function, ask whether the item appears in the official scope and whether the implemented function would fail without it. Listing supports the category boundary; it does not require collection of every listed item.
- For permissions that expose more data than needed, reduce precision, frequency, duration, accessible files, or background access and collect only when the relevant feature is used.
- Separate required and optional processing in the interface. Do not bundle unrelated purposes into access to the basic function or force agreement to non-necessary processing.
- Check each SDK independently. An SDK vendor's default event set or privacy statement does not establish the app provider's necessity or processing basis.

Sources for this answer:

- [Necessary Personal Information Scope for Common Types of Mobile Apps](https://www.cac.gov.cn/2021-03/22/c_1617990997054277.htm?ref=sorena.io) - Articles 3-5 support field-level mapping to an indispensable basic function and the refusal rule.
- [PRC Personal Information Protection Law](https://www.cac.gov.cn/2021-08/20/c_1631050028355286.htm?ref=sorena.io) - Articles 6, 13-17, and 19 support direct relevance, minimum impact, processing-basis and consent controls, notice, withdrawal, and shortest necessary retention.

## 3. Verify refusal, retention, and release evidence

Test a clean installation and existing account with each optional field, permission, and purpose refused or withdrawn. The binding rule is that the provider may not deny the basic function because the user refuses non-necessary information. Confirm that refusal does not cause a hidden loop, degraded core path, repeated coercive prompt, or collection through another SDK or endpoint. Those test details are Sorena's practical evidence method, not wording prescribed by the regulation.

- Retain the app version, category and basic-function decision, data-flow inventory, code or configuration owner, field-level necessity analysis, processing basis, notice and consent version, refusal test, retention rule, deletion test, and approval.
- For every retention period, connect the duration to the purpose or a specific legal duty. PIPL's default is the shortest period necessary to achieve the processing purpose unless a law or administrative regulation provides otherwise.
- Review release changes to screens, permissions, SDKs, events, purposes, recipients, data categories, user types, regions, and retention. Reopen the assessment before the changed processing begins.
- App providers must also maintain data-security controls, monitor risk, remedy security defects or vulnerabilities, and follow the applicable user-notification and authority-reporting rules.

Sources for this answer:

- [Mobile Internet Application Information Service Management Provisions](https://www.cac.gov.cn/2022-06/14/c_1656821626455324.htm?ref=sorena.io) - Articles 10-12 require security remediation, full-process data-security management, compliance with necessary-information scopes, no forced consent, and continued basic service after refusal of non-necessary information.
- [PRC Personal Information Protection Law](https://www.cac.gov.cn/2021-08/20/c_1631050028355286.htm?ref=sorena.io) - Articles 15-16, 19, 51, and 57 support withdrawal, limits on refusing service, shortest necessary retention, security controls, and incident response.

*Operationalize the requirement*

*Placement: Before primary sources*

## Prepare the PIPL and data export evidence file

Sorena AI helps turn the China Privacy Law app personal information minimization decision into owners, controls, and reviewer-ready records.

- [Map official sources to evidence](/solutions/research-copilot.md): Research Copilot connects the official citation, decision, owner, retained evidence, and change history.
- [Review the China route](/contact.md): Check the China Privacy Law scope decision and unresolved launch questions with Sorena.

## Primary sources

- [Necessary Personal Information Scope for Common Types of Mobile Apps](https://www.cac.gov.cn/2021-03/22/c_1617990997054277.htm?ref=sorena.io) - Official category, basic-function, necessary-information, and no-refusal rules, effective 1 May 2021.
- [PRC Personal Information Protection Law](https://www.cac.gov.cn/2021-08/20/c_1631050028355286.htm?ref=sorena.io) - Binding PIPL principles and duties for purpose limitation, minimum impact, notice, processing bases, retention, sensitive information, security, and incidents.
- [Mobile Internet Application Information Service Management Provisions](https://www.cac.gov.cn/2022-06/14/c_1656821626455324.htm?ref=sorena.io) - App-provider rules for security, data management, necessary-information scope, consent design, and access to basic functions, effective 1 August 2022.

## Related Topic Guides

- [App minimum necessary personal information by category](/artifacts/apac/china-privacy-law/app-minimum-necessary-personal-information-by-category.md): App category mapping page for common mobile app necessary personal information scope, using only categories supported by the official source.
- [China data export security assessment workflow](/artifacts/apac/china-privacy-law/data-export-security-assessment-workflow.md): Workflow for screening data export security assessment triggers, materials, owners, and evidence records.
- [China personal information cross-border transfer routes](/artifacts/apac/china-privacy-law/cross-border-transfer-routes.md): 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](/artifacts/apac/china-privacy-law/standard-contract-filing-workflow.md): Workflow for the PIPL standard contract route, assessment, filing package, and cited evidence.
- [China PIPL compliance checklist](/artifacts/apac/china-privacy-law/checklist.md): China PIPL compliance checklist covering scope, processing bases, notices, sensitive information, rights, vendors, impact assessments, incidents, and exports.
- [China PIPL deadlines and compliance calendar](/artifacts/apac/china-privacy-law/deadlines-and-compliance-calendar.md): 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](/artifacts/apac/china-privacy-law/penalties-and-fines.md): 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](/artifacts/apac/china-privacy-law/privacy-policy-and-consent-checklist.md): China PIPL checklist for privacy notices, valid consent, separate consent, sensitive information, children under 14, withdrawal, and rights requests.
- [China PIPL requirements](/artifacts/apac/china-privacy-law/requirements.md): 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](/artifacts/apac/china-privacy-law/china-pipl-vs-ccpa-cpra.md): 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](/artifacts/apac/china-privacy-law/china-privacy-law-vs-gdpr.md): Compare PIPL and GDPR scope, roles, legal bases, rights, impact assessments, breach deadlines, international transfers, and penalties.
- [China PIPL vs Singapore PDPA: Requirements Compared](/artifacts/apac/china-privacy-law/china-privacy-law-vs-singapore-pdpa.md): Compare PIPL and Singapore PDPA scope, roles, consent alternatives, rights, breach duties, overseas transfers, and penalties.
- [China Privacy Law FAQ](/artifacts/apac/china-privacy-law/faq.md): 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?](/artifacts/apac/china-privacy-law/faq/how-should-vendor-contracts-handle-entrusted-processing.md): 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?](/artifacts/apac/china-privacy-law/faq/is-pipl-the-same-as-gdpr.md): 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](/artifacts/apac/china-privacy-law/automated-decision-making-and-personalized-recommendations.md): PIPL checks for automated decisions, personalized recommendations, marketing, differential treatment, explanations, refusal rights, and impact assessments.
- [PIPL breach response and notification](/artifacts/apac/china-privacy-law/breach-response-and-notification.md): 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](/artifacts/apac/china-privacy-law/pipl-cross-border-transfer-route-selector.md): 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](/artifacts/apac/china-privacy-law/entrusted-processing-and-vendor-contracts.md): How to document entrusted processing, vendor responsibilities, contract controls, and evidence under PIPL.
- [PIPL impact assessment template](/artifacts/apac/china-privacy-law/personal-information-protection-impact-assessment-template.md): Template fields for a China personal information protection impact assessment and export/entrusted-processing evidence.
- [Sensitive personal information and separate consent under PIPL](/artifacts/apac/china-privacy-law/sensitive-personal-information-and-separate-consent.md): How to identify sensitive PI triggers, separate consent, minors, additional safeguards, and evidence records.
- [What counts as sensitive personal information in China?](/artifacts/apac/china-privacy-law/faq/what-counts-as-sensitive-personal-information-in-china.md): 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?](/artifacts/apac/china-privacy-law/faq/what-is-separate-consent-under-pipl.md): 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?](/artifacts/apac/china-privacy-law/faq/what-records-should-we-keep-for-a-pipl-impact-assessment.md): 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.
- [What should an app collect as necessary personal information in China?](/artifacts/apac/china-privacy-law/faq/what-should-an-app-collect-as-necessary-personal-information.md): Match the app's basic function to China's 2021 rules and collect no more than the listed necessary personal information. Users must retain the basic function if they decline non-necessary data.
- [When can a company use the China standard contract route?](/artifacts/apac/china-privacy-law/faq/when-can-a-company-use-the-china-standard-contract-route.md): 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?](/artifacts/apac/china-privacy-law/faq/when-does-a-china-pipl-security-assessment-apply.md): 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.


---

[Privacy Policy](https://www.sorena.io/privacy.md) | [Terms of Use](https://www.sorena.io/terms-of-use.md) | [DMCA](https://www.sorena.io/dmca.md) | [About Us](https://www.sorena.io/about-us.md)

(c) 2026 Sorena AB (559573-7338). All rights reserved.

Source: https://www.sorena.io/artifacts/apac/china-privacy-law/app-personal-information-minimization.md