--- title: "What should an app collect as necessary personal information in China?" canonical_url: "https://www.sorena.io/artifacts/apac/china-privacy-law/faq/what-should-an-app-collect-as-necessary-personal-information" source_url: "https://www.sorena.io/artifacts/apac/china-privacy-law/faq/what-should-an-app-collect-as-necessary-personal-information" author: "Sorena AI" description: "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." 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) --- # What should an app collect as necessary personal information in China? 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. *Question* *China* ## 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. China's necessary-personal-information rules took effect on May 1, 2021. Collect no more than the necessary personal information 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. ## Definitions ### Necessary personal information for an app's basic function **Term:** necessary personal information Necessary personal information is consumer-side personal information without which an app cannot provide its basic functional service. The 2021 rules identify the basic function and permitted necessary-information scope for 39 common app categories. They do not cover service-provider-side information. **Why it matters here:** An app may not deny its basic function because a user refuses information outside that necessary scope. The category list is not permission to collect every listed field regardless of need, and PIPL's purpose, basis, notice, minimization, sensitive-information, child, security, and rights rules still apply. Sources: - [Provisions on the Necessary Personal Information Scope for Common Types of Mobile Internet Applications, Articles 2-5](https://www.cac.gov.cn/2021-03/22/c_1617990997054277.htm?ref=sorena.io) - [PRC Personal Information Protection Law, Articles 5-19 and 28-31](https://www.cac.gov.cn/2021-08/20/c_1631050028355286.htm?ref=sorena.io) ## 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. 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 personal information, the no-refusal rule, and the category-specific scopes and examples. - [PRC Personal Information Protection Law](https://www.cac.gov.cn/2021-08/20/c_1631050028355286.htm?ref=sorena.io) - Articles 5-19 and 28-31 supply the separate purpose, minimization, basis, notice, consent, retention, sensitive-information, and child rules. ## 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. 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) - The 2021 rules support the category decision, field map, and no-refusal test for information outside the necessary scope. - [PRC Personal Information Protection Law](https://www.cac.gov.cn/2021-08/20/c_1631050028355286.htm?ref=sorena.io) - PIPL supports the additional processing-basis, notice, minimization, retention, sensitive-information, child, security, rights, and PIPIA checks. ## 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 source for the covered app forms, basic-function test, consumer-side scope, no-refusal rule, and 39 category-specific necessary-information scopes; effective 1 May 2021. - [PRC Personal Information Protection Law](https://www.cac.gov.cn/2021-08/20/c_1631050028355286.htm?ref=sorena.io) - Binding source for the PIPL duties that still apply to collection permitted by the app-category rules. ## 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 app personal information minimization](/artifacts/apac/china-privacy-law/app-personal-information-minimization.md): How to map app category, basic functions, and necessary personal information under China mobile app personal-information rules. - [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. - [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. *Operationalize the requirement* *Placement: Before primary sources* ## 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. - [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. --- [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/faq/what-should-an-app-collect-as-necessary-personal-information.md