The CAC and Ministry of Public Security rules for small-scale personal information processors took effect on September 1, 2026. They offer simplified ways to publish processing rules, handle certain notices, complete audits and impact assessments, and respond to some cross-border transfers. The rules do not remove the Personal Information Protection Law’s core duties, and eligibility depends on the processor’s actual data and activities.
The starting threshold is processing information about fewer than 100,000 natural persons, counted by the people whose information the processor currently handles; deleted information is excluded. Once a business qualifies, it must still check the type of data, whether it shares information outside a platform, why the data is processed, and whether information leaves China. This guide turns those checks into a practical sequence for international businesses.
1. Confirm eligibility before using a simplified measure
The rules define a small-scale processor as a personal information processor that processes information about fewer than 100,000 people. The count is the number of natural persons whose information the processor currently handles; deleted information does not count. Exactly 100,000 people is not “fewer than 100,000.” Keep a dated count and a description of the systems, business units, processors, and purposes included in it.
Do not count rows or devices as people, and do not treat a corporate group chart as a substitute for a processing map. Identify which entity decides why and how the information is used, which entities process it for another party, and whether entities jointly determine those purposes and methods. Where shared systems or group-wide processing make the responsible processor unclear, document the structure and obtain advice before relying on the threshold.
The rules took effect on September 1, 2026. They support proportionate compliance, but Article 3 makes clear that simplified measures operate within the existing personal-information laws and regulations. A smaller processor still needs to comply with the Personal Information Protection Law, including its lawful-basis, security, and data-subject-rights requirements, and any added safeguards triggered by sensitive information, children’s data, or a cross-border transfer.
2. Simplify the public processing rules and notice only when conditions fit
A small processor’s published personal information processing rules must state at least its name, the department or person handling rights requests and contact details, and the purposes, methods, categories, and retention period for the information. A physical business may post the rules conspicuously at its premises; an online business may publish them through its service agreement, app notice, or website.
Article 6 permits a small processor to use the published rules as its notice only if the information is non-sensitive and necessary to provide the product or service, the processor neither provides it to another processor nor makes it public, and the rules make that restriction clear. Article 7 separately addresses information that a person knowingly and voluntarily supplies because it is necessary for the requested service. Do not treat a hidden or bundled notice as voluntary participation.
For sensitive personal information, the rules still require the processor to explain why it is necessary and how processing may affect the person’s rights, and to obtain separate consent where the rule requires it. The ordinary PIPL safeguards for sensitive information, including necessity and heightened protection, still matter.
3. Platform tenants may rely on platform work only within defined limits
A small business operating solely through an online platform may be able to rely on the platform’s processing rules and covered compliance work, but only if all required conditions are met. The business must process information only through that platform and not provide it outside the platform; the platform must publish rules for the tenant’s activity and allocate the parties’ rights and duties; and the tenant must commit to those rules and stay within their stated purposes, methods, and data categories.
If the platform’s compliance audit and impact assessment cover the tenant’s processing, the tenant does not have to repeat those same exercises for that covered activity. If the tenant collects data elsewhere, shares it outside the platform, or uses it beyond the platform rules, it must assess and document its own notice, audit, and impact-assessment obligations. Save the platform agreement and the exact policy version relied on.
4. Apply the cross-border exemptions condition by condition
Article 10 expressly exempts a small processor from the data-export security assessment, standard-contract, and personal-information-protection-certification mechanisms when a listed condition applies. The listed cases include transfers needed to perform a contract with the individual, qualifying cross-border human-resources management, an emergency protecting life, health, or property, a legal duty, and a non-critical-information-infrastructure processor’s transfer of fewer than 100,000 people’s non-sensitive information in the calendar year. The rule also recognizes other conditions prescribed by law or national cyberspace authorities.
This transfer count is not the same as the under-100,000 eligibility threshold: the export exemption looks at cumulative non-sensitive information transferred since January 1 of the current year, while small-processor status looks at the people whose information the processor currently handles. Important data is excluded from the provision. A transfer that qualifies for an exemption from those three mechanisms still requires the processor to follow any applicable notice and separate-consent duties, and to protect the information in the recipient’s hands.
Do not rely on a general claim that small businesses are exempt from cross-border controls. Record the exporter, recipient, data categories, volume, transfer purpose, applicable Article 10 condition, and remaining notice and security steps. Reassess when the transfer purpose or annual volume changes.
5. Use the simplified audit and impact-assessment forms correctly
Small processors may use the rule’s audit self-check form at least once every five years and must retain that audit form for at least five years. They may also use the simplified personal-information-protection impact-assessment form and must retain it for at least three years. A processor that has obtained a qualifying personal-information-protection certification may be exempt from the audit while that certification remains valid.
These periods do not override special requirements. For example, the Regulations on the Protection of Minors in Cyberspace require an annual compliance audit for processing minors’ personal information. If the processor handles children’s data, follow that rule and its reporting requirements rather than relying only on the small-processor five-year schedule.
6. Keep incident response and enforcement in the plan
The rules allow simpler ways to state internal safeguards and incident procedures and, in limited circumstances, to notify individuals about a security incident through a conspicuous notice, app prompt, or website announcement. They still require immediate remedial measures and notices to individuals and authorities as required by law. The regulator may inspect and investigate, and recurring incidents or unlawful processing can still trigger enforcement.
The rules provide for non-punishment or reduced penalties in specified circumstances, such as a minor violation promptly corrected without harm, or timely mitigation and cooperation. That is not blanket immunity. Keep evidence of the incident timeline, containment steps, notices, remediation, and cooperation.
7. A practical implementation checklist
- Count people, not records: document the current population whose information is processed and exclude information that has been deleted.
- Map roles and systems: identify each processor, service provider, platform, group entity, and recipient, and who determines purposes and methods.
- Classify the data: flag sensitive information, minors’ information, important data, and any data disclosed outside a platform.
- Refresh the public rules: include the required identity, rights-contact, purpose, method, data-category, and retention information; make any simplified notice conditions explicit.
- Review each export: record the Article 10 basis, annual non-sensitive export count, recipient, and notice or consent steps that still apply.
- Schedule and retain evidence: calendar audits, child-data annual reviews, impact assessments, and the required five-year and three-year retention periods.
- Recheck on change: repeat the assessment if the user count reaches the threshold, a platform relationship changes, the business adds a new purpose, or data begins leaving China.
Conclusion
The small-processor rules provide real procedural simplifications, including specified cross-border transfer exemptions, but each relief depends on defined conditions. Start with the processor’s current person count and actual role, then test each processing activity and transfer against the relevant article. Keep a short evidence file showing why the business qualifies and which safeguards remain in force. This is general information, not advice on a particular data system or transfer.


