---
title: "PIPL breach response and notification"
canonical_url: "https://www.sorena.io/artifacts/apac/china-privacy-law/breach-response-and-notification"
source_url: "https://www.sorena.io/artifacts/apac/china-privacy-law/breach-response-and-notification"
author: "Sorena AI"
description: "PIPL incident workflow for immediate remediation, authority and individual notices, the narrow individual-notice exception, vendor coordination, and evidence."
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)

---

# PIPL breach response and notification

PIPL incident workflow for immediate remediation, authority and individual notices, the narrow individual-notice exception, vendor coordination, and evidence.

*Privacy* *China*

## China Privacy Law PIPL breach response and notification

When personal information has been or may have been leaked, altered, or lost, take remedial measures immediately and notify the responsible authority and individuals. PIPL sets no fixed hour-based deadline.

Trigger the Article 57 workflow when personal information has been or may have been leaked, altered, or lost. The personal information processor must take remedial measures immediately and notify the department responsible for personal information protection and affected individuals. PIPL does not specify a 24-, 48-, or 72-hour deadline, so do not import a foreign deadline into the PIPL decision.

## Definitions

### Personal information processor

A personal information processor is the organization or individual that independently decides the purpose and method of personal-information processing. It is the accountable role under PIPL and is determined by the actual decision-making facts, not by a contract label.

**Why it matters here:** When personal information has been or may have been leaked, altered, or lost, the personal information processor must take immediate remedial measures and make the Article 57 notifications. An entrusted processor has separate security and assistance duties but does not displace the appointing processor's accountability.

Sources:

- [PRC Personal Information Protection Law, Articles 9, 57, 59, and 73](https://www.cac.gov.cn/2021-08/20/c_1631050028355286.htm?ref=sorena.io)

## Contain and establish the facts

Start remedial action before every fact is known. Stop continuing disclosure or alteration, preserve relevant logs and systems, secure affected accounts or interfaces, and determine whether the event involves personal information and one of Article 57's states: actual or possible leakage, alteration, or loss. The trigger is broader than a confirmed confidentiality breach because possible leakage, alteration, and loss are expressly included.

The personal information processor remains responsible for the PIPL response. An entrusted processor must protect the information and assist the processor with PIPL duties, so the incident procedure and contract should state who escalates, preserves evidence, investigates, and supplies notice facts.

- Incident lead: record discovery time, source, affected systems, status, containment steps, and decision owners.
- Privacy lead: identify the information categories, affected people, sensitive-information or child-data status, processing purpose, jurisdictions, and possible harm.
- Security lead: establish cause, access or disclosure path, duration, recipients, whether data was copied or changed, and whether containment is effective.
- Vendor lead: obtain prompt facts and remedial evidence from entrusted processors and overseas recipients; preserve contractual and technical escalation records.
- Legal owner: check other applicable Chinese sectoral, cybersecurity, data-security, contractual, and foreign notification rules separately. Article 57 is not necessarily the only incident rule.

Sources for this answer:

- [PRC Personal Information Protection Law](https://www.cac.gov.cn/2021-08/20/c_1631050028355286.htm?ref=sorena.io) - Articles 9, 21, 51, 57, and 59 establish processor accountability, entrusted-processing assistance, security and incident-plan controls, and the response trigger.

## Prepare authority and individual notices

Article 57 says the notice must describe the categories of information involved, the reason for the actual or possible leakage, alteration, or loss, the possible harm, the processor's remedial measures, steps individuals can take to reduce harm, and the processor's contact details. Use confirmed facts, identify uncertainty, and correct material information as the investigation develops.

The statute permits omission of notice to individuals only when the processor's measures can effectively prevent harm from the event. This exception does not remove notice to the responsible authority, and the authority may still require individual notice if it considers harm possible. A low-risk label by itself does not meet the statutory test; retain evidence showing how the measures effectively avoid harm.

- Authority-notice record: recipient authority, submission route, submitted content, time, confirmation, follow-up requests, and updates.
- Individual-notice record: audience, channel, languages, versions, send time, delivery status, support path, and measures individuals can take.
- Exception record: the specific measures already operating, evidence that they effectively avoid harm, decision owner, time of decision, and continued monitoring.
- Do not delay immediate remediation while debating notice wording. Do not state that PIPL itself supplies a fixed reporting clock or a numeric harm threshold.

Sources for this answer:

- [PRC Personal Information Protection Law](https://www.cac.gov.cn/2021-08/20/c_1631050028355286.htm?ref=sorena.io) - Article 57 specifies immediate remediation, authority and individual notice, required notice content, the effective-harm-avoidance exception, and the authority's power to require individual notice.

## Close, preserve, and improve the response

Keep a decision log that links changing facts to containment, notification, individual support, and recovery. Preserve evidence needed to show what happened and why each action was taken without retaining exposed personal information longer than necessary.

After containment, verify that remedial measures work, address individual requests and complaints, update risk and vendor records, and correct the weakness that caused the event. Article 51 requires an incident plan; use the findings to update and test it.

- Preserve the incident chronology, affected-data analysis, system and vendor evidence, decisions, approvals, notice versions, delivery records, regulator communications, and remediation tests.
- Track later discoveries that change the affected population, data categories, cause, possible harm, or effectiveness of the individual-notice exception.
- Record follow-up access, correction, deletion, explanation, and complaint requests through the normal PIPL rights process.
- If the event involves an overseas transfer, also assess the transfer instrument, recipient duties, and any data-export incident reporting requirement that applies to the route.

Sources for this answer:

- [PRC Personal Information Protection Law](https://www.cac.gov.cn/2021-08/20/c_1631050028355286.htm?ref=sorena.io) - Articles 44-51, 57, and 64 support rights handling, security remediation, incident records, and possible regulatory interviews or required compliance audits.
- [Provisions on Promoting and Regulating Cross-border Data Flow](https://www.cac.gov.cn/2024-03/22/c_1712776611775634.htm?ref=sorena.io) - Article 11 requires remedial measures and timely reports to the provincial-level CAC and other relevant authorities for an actual or possible data-security incident involving exported data.

*Put the requirement into practice*

*Placement: Before primary sources*

## Prepare the PIPL and data export evidence file

Assign response owners and keep the incident facts, decisions, notices, regulator communications, and remediation evidence together.

- [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

- [PRC Personal Information Protection Law](https://www.cac.gov.cn/2021-08/20/c_1631050028355286.htm?ref=sorena.io) - Binding source for security measures, incident plans, immediate remediation, authority and individual notice, required content, and the individual-notice exception.
- [Provisions on Promoting and Regulating Cross-border Data Flow](https://www.cac.gov.cn/2024-03/22/c_1712776611775634.htm?ref=sorena.io) - Binding source for remedial action and timely authority reporting when an actual or possible data-security incident affects exported data.

## 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 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 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/breach-response-and-notification.md