Data Breach Notification Policy (Hong Kong)
DATA BREACH NOTIFICATION POLICY
Personal Data (Privacy) Ordinance (Cap. 486), Hong Kong SAR
[Organisation Name]
Effective Date: [Effective Date]
Data Protection Contact: [DPO Name], [DPO Contact]
1. PURPOSE
1.1 This Data Breach Notification Policy (“Policy”) establishes the procedures for identifying, assessing, containing, and notifying data breaches involving personal data held by [Organisation Name] (“the Organisation”).
1.2 This Policy ensures the Organisation responds to data breaches in compliance with the Personal Data (Privacy) Ordinance (Cap. 486) and the PCPD’s Guidance on Data Breach Handling and the Giving of Breach Notifications.
2. DEFINITION AND INTERNAL REPORTING
2.1 A data breach is defined as: [Breach Definition]
2.2 All employees must report suspected data breaches to: [Internal Reporting Channel], [Internal Reporting Timeframe].
2.3 The Data Protection Contact shall perform an initial assessment within 24 hours of receiving a breach report.
3. BREACH ASSESSMENT
3.1 The following factors shall be considered when assessing breach severity: [Assessment Criteria]
3.2 External notification shall be triggered when: [Notification Threshold]
4. CONTAINMENT
4.1 Upon confirmation of a breach, the Organisation shall take immediate steps to contain the breach: [Containment Steps]
5. NOTIFICATION
5.1 Notification to the PCPD: Where the breach meets the notification threshold, the Organisation shall notify the PCPD [PCPD Notification Timeframe] using the PCPD’s Data Breach Notification Form. The notification shall include: the nature of the breach; categories and number of affected individuals; likely consequences; and measures taken.
5.2 Notification to affected individuals: The Organisation shall notify affected individuals as soon as practicable via: [Individual Notification Method]. The notification shall include: what happened; what data was affected; what the individual can do to protect themselves; and the Organisation’s contact details.
5.3 Regulatory notification: [Regulatory Notification]
6. RECORD KEEPING
6.1 The Organisation shall maintain a breach register recording all data breaches, including breaches that did not meet the notification threshold. The register shall record: the date of discovery, the nature of the breach, the data and individuals affected, the actions taken, and the outcome.
7. REVIEW AND TESTING
7.1 This Policy shall be reviewed: [Review Frequency], and following any significant data breach.
7.2 Breach notification procedures shall be tested through simulation exercises at least annually.
8. GOVERNING LAW
8.1 This Policy is governed by the laws of the Hong Kong Special Administrative Region of the People’s Republic of China, in particular the Personal Data (Privacy) Ordinance (Cap. 486).
APPROVAL
This Data Breach Notification Policy has been reviewed and approved by the undersigned.
Data Protection Contact
________________
Signature
Chief Executive Officer
________________
Signature
What Is a Data Breach Notification Policy (Hong Kong)?
A Data Breach Notification Policy in Hong Kong sets out the standards and procedures the organisation expects its people to follow.
Hong Kong does not currently impose mandatory data breach notification on all organisations under the Personal Data (Privacy) Ordinance (Cap. 486). Unlike the European Union’s General Data Protection Regulation (GDPR), which requires notification to supervisory authorities within 72 hours, or Singapore’s Personal Data Protection Act, which introduced mandatory notification in 2022, Cap. 486 relies on voluntary notification encouraged by the Office of the Privacy Commissioner for Personal Data (PCPD). The PCPD published its Guidance on Data Breach Handling and the Giving of Breach Notifications, recommending that data users notify the Commissioner and affected individuals when a breach has occurred and there is a real risk of harm to the affected data subjects. Section 50A of Cap. 486 empowers the Privacy Commissioner to serve an enforcement notice requiring a data user to take steps to remedy a contravention of the Ordinance, including failures in data security.
Proposed amendments to Cap. 486 to introduce mandatory data breach notification have been under consideration by the Hong Kong government for several years. When enacted, these amendments are expected to require data users to notify the PCPD and affected individuals within a prescribed period following discovery of a notifiable breach. Organisations with a documented notification policy will be better positioned to comply with the mandatory regime when it takes effect.
For regulated organisations, sector-specific mandatory reporting requirements already apply. Authorised institutions regulated by the Hong Kong Monetary Authority (HKMA) must report material cybersecurity incidents — including data breaches — under the HKMA Supervisory Policy Manual module TM-E-1. The HKMA expects notification within a specified timeframe and may require follow-up reports as the investigation progresses. Licensed corporations regulated by the Securities and Futures Commission (SFC) must report operational incidents affecting client data under applicable SFC circulars and the requirements of the Securities and Futures Ordinance (Cap. 571).
The Crimes Ordinance (Cap. 200) is relevant when a data breach is caused by a criminal act — Section 161 of Cap. 200 criminalises access to computers with criminal or dishonest intent. Section 19 of Cap. 486 gives data subjects the right to request access to their personal data held by a data user, and Section 22 of Cap. 486 gives the right to correct inaccurate data. Where a breach involves criminal conduct, the Hong Kong Police Force’s Cyber Security and Technology Crime Bureau (CSTCB) should be notified alongside the PCPD. The Privacy Commissioner for Personal Data holds powers under Section 48 of Cap. 486 to investigate complaints and under Section 50 to conduct investigations on the Commissioner’s own initiative. Forms-legal.com provides this Data Breach Notification Policy template incorporating the PCPD’s breach notification guidance and HKMA reporting requirements.
When Do You Need a Data Breach Notification Policy (Hong Kong)?
A Data Breach Notification Policy in Hong Kong should be adopted before any data breach occurs. Organisations that attempt to manage a breach without pre-established procedures respond more slowly, make avoidable mistakes in notification content and timing, and present a weaker compliance posture to the PCPD in any subsequent investigation.
Every Hong Kong organisation that collects or processes personal data needs this policy to meet its DPP4 obligations under Cap. 486. The PCPD’s enforcement decisions following data breach complaints consistently reference the absence of documented breach response procedures as evidence of inadequate data security measures. A written policy demonstrates due diligence.
Organisations handling large volumes of sensitive personal data — HKID numbers, financial account details, health records, salary information — face heightened harm potential from breaches and require particularly detailed notification procedures that address the nature of the compromised data, the risk assessment methodology, and the specific content of notifications to affected individuals.
HKMA-regulated authorised institutions need the policy to satisfy SPM module TM-E-1 cybersecurity incident management requirements and to meet the HKMA’s expectations for timely incident reporting. Banks and other authorised institutions that suffer material data breaches must report to the HKMA within specified timeframes, and a policy that establishes internal escalation procedures confirms those timelines can be met.
SFC-licensed corporations need the policy to satisfy SFC circular requirements on cybersecurity incident response. The SFC has taken disciplinary action against licensed persons for failing to maintain adequate cybersecurity incident management procedures, making a written policy a regulatory necessity rather than a best-practice recommendation.
Healthcare providers — hospitals, clinics, and diagnostic laboratories — processing patient data must have a notification policy that addresses the PCPD’s guidance on medical data sensitivity and the reporting expectations of the Hospital Authority and the Department of Health for incidents affecting patient records.
Organisations preparing for the eventual introduction of mandatory data breach notification under proposed Cap. 486 amendments should adopt a notification policy now that mirrors the likely mandatory requirements — including notification timelines, content standards, and the distinction between notifiable and non-notifiable breaches — so that no remediation is required when the amendments take effect.
What to Include in Your Data Breach Notification Policy (Hong Kong)
A Data Breach Notification Policy for Hong Kong organisations must address the following core elements to satisfy DPP4 of Cap. 486, PCPD guidance, and, for regulated entities, HKMA and SFC incident reporting requirements.
Definition of Data Breach specifies what the policy treats as a data breach — any incident resulting in unauthorised or accidental access to, processing, erasure, loss, or use of personal data held by the organisation, whether caused by external attack, employee error, system failure, physical loss of devices, or third-party processor incident. The definition should align with the PCPD’s guidance to avoid ambiguity about when the policy is triggered.
Detection and Internal Reporting establishes the channels through which potential breaches are detected — security monitoring systems, employee reports, vendor notifications, regulatory alerts — and the internal escalation procedure specifying who must be notified and within what timeframe. Every employee should know the designated breach reporting contact and the obligation to report suspected incidents promptly.
Initial Assessment and Severity Classification requires the Data Protection Officer (or designated breach response lead) to conduct an initial assessment within a defined period (typically 24–48 hours) covering: the nature of the compromised personal data; the number and categories of affected data subjects; whether the data was encrypted or otherwise protected; whether the data has been recovered; the likely cause of the breach; and the potential risk of harm to affected individuals — identity theft, financial loss, reputational damage, physical harm, or loss of employment.
Containment and Interim Measures specifies the immediate steps to stop the breach from continuing — revoking compromised credentials, isolating affected systems, blocking unauthorised access, recovering lost devices, or instructing a data processor to cease processing. Evidence preservation for potential law enforcement referral must be balanced against the need for rapid containment.
Notification Decision Criteria sets out the framework for deciding whether to notify the PCPD, affected individuals, the HKMA, the SFC, the Hong Kong Police CSTCB, or overseas regulators. The PCPD recommends notification when there is a real risk of harm to affected data subjects — the policy should apply a consistent risk assessment methodology. For HKMA-regulated institutions, notification within the required timeframe is mandatory for material incidents regardless of harm assessment.
PCPD Notification Procedure describes the process for voluntarily notifying the PCPD — using the PCPD’s Data Breach Notification Form, specifying the breach nature, personal data categories, number of affected individuals, likely consequences, and measures taken. Initial notification may be preliminary with a follow-up report as the investigation is completed.
Individual Notification Procedure establishes the content, format, and delivery method for notifications to affected data subjects — plain language description of what occurred, what personal data was affected, what individuals can do to protect themselves, what the organisation is doing in response, and who to contact for further information. Notifications should be sent by the most effective available method (email, letter, or public notice where direct contact is impractical).
Record Keeping requires documentation of all breach handling activities — detection records, assessment records, containment actions, notification decisions, notification content, and post-incident review findings — retained for at least seven years under Inland Revenue Ordinance (Cap. 112) record-keeping practice and consistent with Section 26 of the Personal Data (Privacy) Ordinance (Cap. 486), which prohibits retaining personal data longer than is necessary for the purpose for which it was collected. Post-incident review findings should be used to update the policy and close identified control gaps. The PCPD and the Hong Kong Monetary Authority (HKMA) may request inspection of breach records in the course of regulatory investigations. Forms-legal.com provides a related Cybersecurity Incident Response Plan template that addresses the technical response to incidents underlying data breaches.
Sources & Citations
Statutory citations link to official government sources.
Cite this page
Reference this free template in an article, syllabus, or research note:
Forms Legal. (2026). Data Breach Notification Policy (Hong Kong) (Hong Kong) [Legal document template]. Forms Legal. https://forms-legal.com/hong-kong/business/policies/data-breach-notification-policy-hong-kong
"Data Breach Notification Policy (Hong Kong) (Hong Kong)." Forms Legal, 2026, https://forms-legal.com/hong-kong/business/policies/data-breach-notification-policy-hong-kong.
@misc{formslegal-data-breach-notification-policy-hong-kong,
author = {{Forms Legal}},
title = {Data Breach Notification Policy (Hong Kong) (Hong Kong)},
year = {2026},
howpublished = {\url{https://forms-legal.com/hong-kong/business/policies/data-breach-notification-policy-hong-kong}},
note = {Free legal document template. Based on Personal Data (Privacy) Ordinance (Cap. 486)}
}Also available for these jurisdictions:
Frequently Asked Questions
As of 2026, data breach notification is not mandatory under Hong Kong’s Personal Data (Privacy) Ordinance (Cap. 486). Unlike the EU GDPR (which requires notification within 72 hours) or Australia’s Notifiable Data Breaches scheme, the PDPO does not currently include a statutory breach notification requirement. However, the Office of the Privacy Commissioner for Personal Data (PCPD) has strongly encouraged voluntary data breach notification since publishing its Guidance on Data Breach Handling and the Giving of Breach Notifications. The PCPD recommends that data users notify the Commissioner and affected individuals when a breach involving personal data has occurred and there is a real risk of harm to the affected individuals. Proposed amendments to the PDPO to introduce mandatory data breach notification have been under discussion for several years. The proposed amendments would require data users to notify the PCPD and affected individuals within a specified timeframe following a data breach. While these amendments have not yet been enacted, they remain on the legislative agenda and organisations should prepare for their eventual introduction. Even without mandatory notification, there are strong practical reasons for voluntary notification. The PCPD considers voluntary notification as evidence of responsible data handling, which may be viewed favourably if the breach leads to a complaint or investigation. Organisations that fail to notify and are subsequently found to have breached DPP 4 (security) may face more severe regulatory consequences.
The PCPD’s guidance recommends notification when a data breach meets specific criteria. Understanding these triggers is essential for any data breach notification policy. A data breach involving personal data is defined by the PCPD as any incident that results in unauthorised or accidental access to, processing of, erasure of, loss of, or use of personal data held by a data user. This includes both external attacks (hacking, ransomware, phishing) and internal incidents (employee error, unauthorised access by staff, lost devices). The PCPD recommends notification when the breach involves personal data AND there is a real risk of harm to the affected data subjects. Harm may include identity theft, financial loss, physical harm, humiliation, damage to reputation, or loss of employment opportunities. Factors to assess when determining whether notification is warranted include the nature and sensitivity of the personal data involved (HKID numbers, financial data, and health data are more sensitive); the number of individuals affected; whether the data was encrypted or otherwise protected; whether the data has been recovered; the likelihood that the data will be misused; and the potential consequences for affected individuals. The PCPD’s guidance distinguishes between notification to the Commissioner (recommended for all significant breaches) and notification to affected individuals (recommended where there is a real risk of harm). The two types of notification may have different triggers and timelines.
When voluntarily notifying the PCPD of a data breach, the organisation should provide comprehensive information to enable the Commissioner to assess the breach and provide guidance. The PCPD has a Data Breach Notification Form available on its website. The notification should include the following information. Description of the breach: What happened, when it was discovered, and when it occurred (if different from the discovery date). The type of breach — unauthorised access, accidental loss, theft, ransomware, employee error, or system vulnerability. Personal data affected: The categories of personal data involved (names, HKID numbers, contact details, financial information, health data). Whether the data was encrypted or otherwise protected. Affected individuals: The approximate number of individuals affected and the categories of data subjects (customers, employees, patients, students). Likely consequences: An assessment of the potential impact on affected individuals, including the risk of identity theft, financial loss, or other harm. Measures taken: The steps the organisation has taken to contain the breach, mitigate its effects, and prevent recurrence. Whether law enforcement has been notified. Notification to individuals: Whether affected individuals have been notified or will be notified, and if so, the timing and content of the notification. Contact details: The name, role, and contact details of the person responsible for managing the breach response.
When a data breach involves a real risk of harm to individuals, the PCPD recommends that the organisation notify affected individuals as soon as practicable. The notification should be direct, clear, and provide actionable information. Method of notification: Use the most effective method available to reach affected individuals promptly. This may include email, letter, telephone call, or SMS. If direct notification is not practicable (for example, because contact details have been compromised), the organisation may use public announcements, website notices, or media statements as a supplementary measure. Content of notification: The notification to individuals should include a description of what happened in plain language; what categories of personal data were affected; what the individual can do to protect themselves (for example, changing passwords, monitoring bank accounts, being alert to phishing); what the organisation is doing to address the breach and prevent recurrence; and contact details for the organisation’s data protection contact or help line. Timing: Notification should be made as soon as practicable after the breach is confirmed. Delay may be justified if law enforcement requests a delay to avoid prejudicing an investigation, but the delay should be as short as possible. Tone and transparency: The notification should be honest and transparent. Attempting to minimise or conceal the breach may cause greater reputational damage if the full extent is later revealed.
Proposed amendments to the Personal Data (Privacy) Ordinance (Cap. 486) to introduce mandatory data breach notification have been under active consideration by the Hong Kong government for several years. When enacted, the amendments are expected to require data users to notify the PCPD and affected individuals within a prescribed period — expected to be 72 hours for notification to the PCPD and as soon as practicable thereafter for individual notification — following discovery of a notifiable breach. Organisations can prepare for mandatory notification by taking the following steps now. First, adopt a written Data Breach Notification Policy that mirrors the expected mandatory requirements — including a 72-hour PCPD notification timeline, notification content standards, and a risk assessment framework for determining whether a breach is notifiable. Organisations with a policy already aligned to the expected requirements will face no compliance gap when the amendments take effect. Second, appoint a Data Protection Officer (DPO) or privacy lead with clear authority and responsibility for breach response. Many HKMA-regulated institutions and SFC-licensed corporations already have compliance officers with data protection responsibilities — formalising the DPO function ensures accountability. Third, conduct a data mapping exercise to identify what personal data the organisation holds, where it is stored, who has access, and which systems are most vulnerable to breach.
This template is provided for informational purposes only and does not constitute legal advice. Laws vary by jurisdiction and change over time. Consult a qualified attorney for advice specific to your situation.Full disclaimer
Found an error? Let us knowRelated Documents
You may also find these documents useful:
Cybersecurity Incident Response Plan (Hong Kong)
A Cybersecurity Incident Response Plan for Hong Kong organisations establishing procedures for detecting, responding to, and recovering from cybersecurity incidents. Addresses data breach handling under the Personal Data (Privacy) Ordinance (Cap. 486) and PCPD guidance on voluntary breach notification.
Data Protection Policy (Hong Kong)
A Data Protection Policy for Hong Kong organisations ensuring compliance with the Personal Data (Privacy) Ordinance (Cap. 486) and its six Data Protection Principles. Establishes rules for collecting, holding, processing, and using personal data, and addresses data subject rights under the PDPO.
Privacy Policy (Hong Kong)
A Privacy Policy Statement for Hong Kong organisations compliant with the Personal Data (Privacy) Ordinance (Cap. 486). Addresses the six Data Protection Principles, data subject rights, direct marketing consent, cookies, and data breach handling as recommended by the PCPD.
Data Processing Agreement (Hong Kong)
A Data Processing Agreement (DPA) governing the processing of personal data by a third-party processor on behalf of an organisation, compliant with the Personal Data (Privacy) Ordinance (Cap. 486) and its six Data Protection Principles. Establishes processor obligations, data handling standards, and security requirements under Hong Kong's PDPO framework.
Acceptable Use Policy (Hong Kong)
An Acceptable Use Policy (AUP) for Hong Kong organisations setting out the rules and guidelines for the proper use of company IT systems, networks, and digital resources. Governs employee conduct when accessing company technology, internet, email, and software under Hong Kong common law and practical compliance standards.