Data Protection Monitor
Global Privacy & Data Protection Intelligence

Not every instrument is backed by its official text yet. At least one law or rulebook covered here has no official source (tier 1) retrieved for it yet. No finding on this page is shown with confidence above “Probable” until stronger sources are retrieved.

Hong Kong Data Protection & Privacy Regulation

HK schema gdpri-v2 trajectory: not yet assessed regulated (omnibus) overlaps: Sentinel (AML/CFT), World Payments, artificial-intelligence

Last updated · 10 categories · 114 claims · 42 sources in the cumulative register

Hong Kong's data-protection perimeter widened this cycle as a dedicated critical-infrastructure cybersecurity regime came into force alongside the long-standing Personal Data (Privacy) Ordinance.

Data collected Data published

AI-assembled from cited sources

Not fully checked this cycle: Controller/Processor Duties, Algorithmic, Biometric & Surveillance Governance (2 open gaps).

Framework & posture10 of 10 modules active
10 active · 10 binding instruments
Next milestoneNo upcoming dated milestone on record
Record & confidence mix114 claims · 76 sources · machine-compiled
110 Probable4 Contested / unverified
Evidence re-verified: ·Position last changed: ·
Record history & provenance ▾

Methodology & record provenance: Module confidence is derived from the underlying claims (source tier and primary excerpt retention), while statutory legal force is tracked independently.

Review status: AI-synthesised · Tier-1/2 verified · As-of date: 2026-11-17

Jurisdiction brief

Latest update · 20 October 2026

Lead Signal

Hong Kong's data protection regulator deepened its engagement with technology-driven risk, most notably through a finding that the Worldcoin iris-scanning biometric project contravened the Personal Data (Privacy) Ordinance. The investigation, which the Privacy Commissioner for Personal Data commenced in January 2024, concluded with a finding of contravention, as recorded in a Legislative Council paper; the specific Data Protection Principle breached and the full enforcement outcome were not independently confirmed beyond that summary. Separately, the PCPD published a supplement to its Model Personal Data Protection Framework specifically addressing agentic artificial intelligence, dated 25 August 2026, extending its existing non-binding 2024 guidance into this newer category of automated decision-making technology.

Key regulatory facts for Hong Kong
Key regulatory facts for Hong Kong
Regulatory DimensionHong Kong Standing Position
JurisdictionHong Kong (HK)
Regulatory ScopeData Protection & Privacy Regulation (10 modules, 114 sourced findings)
Regulator & FrameworkCore regulator/statute framework is well-established (green-equivalent), but material and territorial scope diverge substantially from GDPR baseline, and a registration/filing sub-module could not be evidenced, warranting amber overall.
Lawful Processing & Special DataFunctional equivalents exist via DPPs and guidance, but the absence of enumerated lawful bases and a codified special-category regime is a material structural gap versus GDPR.
Data Subject RightsAccess/rectification rights are well-defined and binding (green-equivalent), but erasure and portability rights are absent, and restriction/objection is narrow — pulling the module to amber overall.
Controller/Processor DutiesMultiple GDPR-equivalent accountability pillars (DPIA, DPO, ROPA, mandatory breach notification) are absent from binding law; only security and retention principles and processor-supervision duties are binding.
Primary Instruments CitedDLA Piper, SmartSuite, Hong Kong Official Instrument (dataprotection.gi hong-kong), Hong Kong Official Instrument (legco.gov.hk ca20250217cb2-247-4-e-pdf), Hong Kong Statutory Instrument 2019A07
Last Confirmed / Updated (42 sources in cumulative register)

#

Core regulator/statute framework is well-established (green-equivalent), but material and territorial scope diverge substantially from GDPR baseline, and a registration/filing sub-module could not be evidenced, warranting amber overall.

Primary frameworkPersonal Data (Privacy) Ordinance (Cap. 486)
Traffic-light rationale — AmberCore regulator/statute framework is well-established (green-equivalent), but material and territorial scope diverge substantially from GDPR baseline, and a registration/filing sub-module could not be evidenced, warranting amber overall.

Sub-modules (5)

Regulator and authorityGreen

PCPD is the statutory regulator headed by the Privacy Commissioner, with investigative and enforcement powers under the PDPO.

Claims (3):

  • The Office of the Privacy Commissioner for Personal Data (PCPD) is the main body responsible for overseeing enforcement of the PDPO and is headed by the Privacy Commissioner for Personal Data.
  • The PCPD, not mainland China's CAC, is the supervisory authority for Hong Kong's PDPO; the two regimes operate separately under 'one country, two systems'.
  • Privacy Commissioner for Personal Data (PCPD) — Enforces the PDPO under section 5 of the Ordinance.

Act and instrumentsGreen

PDPO Cap. 486 (in force since 1996) is the principal instrument, materially amended in 2012 (direct marketing) and 2021 (anti-doxxing).

Claims (4):

  • The Personal Data (Privacy) Ordinance (Cap. 486) came into force on 20 December 1996 and was significantly amended by the 2012 Amendment Ordinance (direct marketing) and the 2021 Amendment Ordinance (anti-doxxing).
  • Protection of Critical Infrastructures (Computer Systems) Ordinance — The CIO came into full force on 1 January 2026, adding a cybersecurity-for-critical-infrastructure regime adjacent to, and separate from, the PDPO.
  • Personal Data (Privacy) Ordinance reform package — Proposed January 2020 reform (mandatory breach notification, processor regulation, retention/disposal rules, administrative fining power) remains substantially un-enacted; only the 2021 anti-doxxing amendment delivered.
  • Personal Data (Privacy) Ordinance Cap. 486 — Government long-proposed PDPO amendments covering mandatory data-breach notification, mandatory data retention policies, PCPD power to impose administrative fines, direct regulation of processors; no bill introduced as of 2026-11-02

Material scopeAmber

PDPO scope centers on Data Protection Principles (DPPs) governing collection, holding, processing and use of personal data by 'data users'.

Claims (3):

  • Data Protection Principle 1(1) requires that only necessary, adequate and not excessive personal data be collected for a lawful purpose, forming part of PDPO's core material-scope obligations on data users.
  • Personal Data (Privacy) Ordinance (Cap. 486), s.2(1) — A foreign business is caught as a 'data user' where it controls the personal data collected, even if processing occurs outside Hong Kong, so long as the controlling data user is based/operating in Hong Kong.
  • Personal Data (Privacy) Ordinance (Cap. 486) Sch.1 — General exemption from the Data Protection Principles for personal data held for domestic or recreational purposes

Territorial scopeAmber

PCPD has clarified PDPO has no extraterritorial scope; it applies where the data user's principal place of business is in Hong Kong.

Claims (2):

  • The PDPO is unclear on its territorial scope on its face, but the PCPD has clarified that the PDPO does not have extraterritorial scope, in contrast to the GDPR's extraterritorial application.
  • Personal Data (Privacy) Ordinance (Cap. 486) — No extraterritorial effect

Regulator registration and filingRed

No evidence located of a general controller registration/filing obligation to PCPD akin to EU-style DPA registers.

Claims (1):

  • Personal Data (Privacy) Ordinance (Cap. 486) — No statutory requirement under the PDPO for data users to register, notify the PCPD, or pay a fee before collecting or processing personal data
Category narrative 75 words

Hong Kong's data protection regime is anchored in the Personal Data (Privacy) Ordinance (Cap. 486), a comprehensive omnibus statute enforced by the Privacy Commissioner for Personal Data (PCPD). The PDPO has no extraterritorial reach and applies to data users with a principal place of business in Hong Kong. Unlike GDPR-model regimes, PDPO does not impose a general registration/filing obligation on data users; no direct evidence of such a regime was found in this research pass.

Periodic update · new data 2026-09-28

Hong Kong's data-protection framework continues to rest on the Personal Data (Privacy) Ordinance, supervised by the Privacy Commissioner for Personal Data. The Privacy Commissioner, not mainland China's Cyberspace Administration, is confirmed as the supervisory authority for this Ordinance, with the two regimes operating entirely separately under the 'one country, two systems' constitutional arrangement — a standing baseline fact with no change this cycle.

The material development this cycle is the commencement of a separate, adjacent instrument: the Protection of Critical Infrastructures (Computer Systems) Ordinance came into full force on 1 January 2026. This Ordinance establishes a cybersecurity-for-critical-infrastructure regime that is structurally distinct from, and sits alongside, the Personal Data (Privacy) Ordinance rather than amending or extending it. Organisations that qualify as operators of critical infrastructure computer systems now face obligations under this new Ordinance in addition to, not instead of, their existing Personal Data (Privacy) Ordinance obligations where personal data is involved. This is an escalating regulatory-framework trajectory for Hong Kong: the jurisdiction's regulatory perimeter for computer-systems and data-related obligations is widening even though the Personal Data (Privacy) Ordinance itself has not been amended this cycle.

No change to the Personal Data (Privacy) Ordinance's own statutory text, its lawful-processing basis, or the Privacy Commissioner's core supervisory mandate under that Ordinance was evidenced this cycle.

Outlook

The item to watch is how the Protection of Critical Infrastructures (Computer Systems) Ordinance's obligations interact in practice with Personal Data (Privacy) Ordinance compliance for organisations that qualify as critical-infrastructure operators and also process personal data, since this cycle's evidence establishes the new Ordinance's commencement but not yet how overlapping compliance obligations will be reconciled or supervised in practice.

1 further periodic run re-emitted the standing brief unchanged and is not shown.

Sources and claims (13)
  1. Probable DataGuidance — The Office of the Privacy Commissioner for Personal Data (PCPD) is the main body responsible for overseeing enforcement of the PDPO and is headed by the Privacy Commissioner for Personal Data. observed
  2. Probable DataGuidance — The Personal Data (Privacy) Ordinance (Cap. 486) came into force on 20 December 1996 and was significantly amended by the 2012 Amendment Ordinance (direct marketing) and the 2021 Amendment Ordinance (anti-doxxing). observed
  3. Probable IAPP — Data Protection Principle 1(1) requires that only necessary, adequate and not excessive personal data be collected for a lawful purpose, forming part of PDPO's core material-scope obligations on data users. observed
  4. Probable DataGuidance — The PDPO is unclear on its territorial scope on its face, but the PCPD has clarified that the PDPO does not have extraterritorial scope, in contrast to the GDPR's extraterritorial application. observed
  5. Probable DLA Piper — Protection of Critical Infrastructures (Computer Systems) Ordinance — The CIO came into full force on 1 January 2026, adding a cybersecurity-for-critical-infrastructure regime adjacent to, and separate from, the PDPO. observed
  6. Probable HFW — A new era for data protection in Hong Kong — The PCPD, not mainland China's CAC, is the supervisory authority for Hong Kong's PDPO; the two regimes operate separately under 'one country, two systems'. observed
  7. Probable SmartSuite — Privacy Commissioner for Personal Data (PCPD) — Enforces the PDPO under section 5 of the Ordinance. observed
  8. Uncertain https://dataprotection.gi/jurisdictions/hong-kong/ — Personal Data (Privacy) Ordinance reform package — Proposed January 2020 reform (mandatory breach notification, processor regulation, retention/disposal rules, administrative fining power) remains substantially un-enacted; only the 2021 anti-doxxing amendment delivered.
  9. Probable https://www.legco.gov.hk/yr2025/english/panels/ca/papers/ca20250217cb2-247-4-e.pdf — Personal Data (Privacy) Ordinance Cap. 486 — Government long-proposed PDPO amendments covering mandatory data-breach notification, mandatory data retention policies, PCPD power to impose administrative fines, direct regulation of processors; no bill introduced as of 2026-11-02
  10. Probable https://www.pcpd.org.hk/english/enforcement/case_notes/casenotes_2.php?id=2019A07&content_type=&content_nature=&msg_id2=518 — Personal Data (Privacy) Ordinance (Cap. 486) — No extraterritorial effect
  11. Probable https://captaincompliance.com/education/hong-kong-pdpo/ — Personal Data (Privacy) Ordinance (Cap. 486), s.2(1) — A foreign business is caught as a 'data user' where it controls the personal data collected, even if processing occurs outside Hong Kong, so long as the controlling data user is based/operating in Hong Kong.
  12. Probable https://www.multilaw.com/Multilaw/Multilaw/Data_Protection_Laws_Guide/DataProtection_Guide_Hong_Kong.aspx — Personal Data (Privacy) Ordinance (Cap. 486) — No statutory requirement under the PDPO for data users to register, notify the PCPD, or pay a fee before collecting or processing personal data
  13. Probable https://www.linklaters.com/en/insights/data-protected/data-protected---hong-kong — Personal Data (Privacy) Ordinance (Cap. 486) Sch.1 — General exemption from the Data Protection Principles for personal data held for domestic or recreational purposes

#

Functional equivalents exist via DPPs and guidance, but the absence of enumerated lawful bases and a codified special-category regime is a material structural gap versus GDPR.

Primary frameworkPersonal Data (Privacy) Ordinance (Cap. 486) — Data Protection Principles
Supervisory authorityPCPD
Traffic-light rationale — AmberFunctional equivalents exist via DPPs and guidance, but the absence of enumerated lawful bases and a codified special-category regime is a material structural gap versus GDPR.

Sub-modules (4)

Lawful basesAmber

DPPs (esp. DPP1 collection limitation) function as the lawful-processing framework rather than an Art.6-style enumerated list.

Claims (2):

  • Data Protection Principle 1(1) provides that only necessary, adequate and not excessive personal data is to be collected for a lawful purpose, operating as PDPO's functional lawful-basis analogue.
  • Personal Data (Privacy) Ordinance (Cap. 486), Schedule 1 DPP1(1) — Personal data may only be collected for a lawful purpose directly related to a function/activity of the data user, must be necessary and not excessive, and collected by lawful and fair means; there is no GDPR-style legitimate-interests balancing test.

Special categoriesAmber

No enumerated special/sensitive-category regime exists in statute; PCPD guidance flags HKID numbers, biometric data and consumer credit data for heightened caution.

Claims (3):

  • The PCPD has published guidelines flagging Hong Kong identity card numbers, biometric data and consumer credit data as categories requiring special caution in collection and use, in the absence of a codified statutory special-category regime.
  • Code of Practice on the Identity Card Number and Other Personal Identifiers (revised Aug 2024) — Data users should not require an individual to provide a Hong Kong ID Card or its number unless statutorily authorised, and should offer less privacy-intrusive identification methods where practicable.
  • Personal Data (Privacy) Ordinance (Cap. 486) — No statutory concept of 'special categories' or 'sensitive personal data'; PCPD Codes of Practice/guidance flag ID-card numbers, biometric data and consumer credit data as warranting extra caution.

Pseudonymisation and anonymisationAmber

PDPO does not statutorily define pseudonymised or anonymised data; PCPD's 2011 Guidance on Personal Data Erasure and Anonymisation addresses the anonymisation threshold.

Claims (1):

  • The PDPO does not address sensitive personal data, anonymisation, or pseudonymisation in the statute itself, though the PCPD has clarified aspects of anonymisation through non-binding guidance.
Category narrative 53 words

PDPO does not use an enumerated GDPR Art.6-style lawful-basis list; instead, its six Data Protection Principles govern collection and use. There is no statutory special/sensitive-category regime; PCPD instead issues category-specific guidance (HKID numbers, biometric data, consumer credit data). Pseudonymisation and anonymisation are not defined in the statute, though PCPD guidance addresses anonymisation thresholds.

Sources and claims (8)
  1. Probable IAPP — Data Protection Principle 1(1) provides that only necessary, adequate and not excessive personal data is to be collected for a lawful purpose, operating as PDPO's functional lawful-basis analogue. observed
  2. Probable IAPP — Before using or providing personal data for direct marketing, a data user must inform the individual and obtain consent or an indication of no objection, and the individual may opt out at any time irrespective of prior consent. observed
  3. Probable DataGuidance — The PCPD has published guidelines flagging Hong Kong identity card numbers, biometric data and consumer credit data as categories requiring special caution in collection and use, in the absence of a codified statutory special-category regime. observed
  4. Probable DataGuidance — The PDPO does not address sensitive personal data, anonymisation, or pseudonymisation in the statute itself, though the PCPD has clarified aspects of anonymisation through non-binding guidance. observed
  5. Probable https://www.mayerbrown.com/en/insights/publications/2024/10/hong-kong-office-of-the-privacy-commissioner-for-personal-data-issues-updated-code-of-practice-on-the-identity-card-number-and-other-personal-identifiers-compliance-guide-for-data-users — Code of Practice on the Identity Card Number and Other Personal Identifiers (revised Aug 2024) — Data users should not require an individual to provide a Hong Kong ID Card or its number unless statutorily authorised, and should offer less privacy-intrusive identification methods where practicable.
  6. Probable https://www.legal500.com/guides/chapter/hong-kong-data-protection-cybersecurity/ — Personal Data (Privacy) Ordinance (Cap. 486) — No statutory concept of 'special categories' or 'sensitive personal data'; PCPD Codes of Practice/guidance flag ID-card numbers, biometric data and consumer credit data as warranting extra caution.
  7. Probable https://www.pcpd.org.hk/english/enforcement/response/files/AEOI.pdf — Personal Data (Privacy) Ordinance (Cap. 486), s.2(3) — 'Prescribed consent' is express consent given voluntarily and not withdrawn by notice in writing; implied or bundled consent and non-response are not valid.
  8. Probable PCPD — Personal Data (Privacy) Ordinance (Cap. 486), Schedule 1 DPP1(1) — Personal data may only be collected for a lawful purpose directly related to a function/activity of the data user, must be necessary and not excessive, and collected by lawful and fair means; there is no GDPR-style legitimate-interests balancing test. observed

#

Access/rectification rights are well-defined and binding (green-equivalent), but erasure and portability rights are absent, and restriction/objection is narrow — pulling the module to amber overall.

Primary frameworkPersonal Data (Privacy) Ordinance (Cap. 486)
Supervisory authorityPCPD
Traffic-light rationale — AmberAccess/rectification rights are well-defined and binding (green-equivalent), but erasure and portability rights are absent, and restriction/objection is narrow — pulling the module to amber overall.

Sub-modules (5)

Access rightGreen

Data subjects may request access; if refused, the data user must inform the requestor within 40 calendar days and explain the refusal.

Claims (1):

  • If a data user rejects or denies a data access request, it must inform the requestor within 40 calendar days from receipt of the request and explain why it cannot comply.

Rectification and erasureAmber

Correction requests must be honored within 40 days; however, PDPO does not provide a general right to erasure/deletion, only a duty not to retain data beyond necessity.

Claims (3):

  • A data correction request must be complied with, and a copy of the corrected personal data provided, within 40 calendar days from receipt under Section 23(1) of the PDPO.
  • Unlike the GDPR, the PDPO does not provide data subjects with a general right to request erasure or deletion of their personal data; only general requirements exist relating to erasure once data is no longer required for its original purpose.
  • Personal Data (Privacy) Ordinance (Cap. 486), s.26(1) — A data user must take all practicable steps to erase personal data no longer required for its purpose, unless erasure is prohibited by law or against the public interest; there is no standalone right to be forgotten.

Restriction and objectionAmber

No general restriction-of-processing right exists; the closest analogue is the standing direct-marketing opt-out right.

Claims (2):

  • An individual is entitled to opt out of direct marketing at any time irrespective of having previously given consent, functioning as PDPO's principal objection-type right.
  • Personal Data (Privacy) Ordinance (Cap. 486), s.35G(1) — A data subject may at any time require a data user, free of charge, to cease using their personal data for direct marketing, and the data user must comply.

Data portabilityRed

No evidence of a statutory data-portability right was located in this research pass.

Deadlines and response windowsGreen

A uniform 40-calendar-day statutory response window applies to both access and correction requests.

Claims (3):

  • If a data user rejects or denies a data access request, it must inform the requestor within 40 calendar days from receipt of the request and explain why it cannot comply.
  • A data correction request must be complied with, and a copy of the corrected personal data provided, within 40 calendar days from receipt under Section 23(1) of the PDPO.
  • Personal Data (Privacy) Ordinance (Cap. 486), s.19(1) — A data user must comply with a data access request within 40 calendar days of receipt, or notify the requestor and refusal reasons within that period if refusing under s.20.
Category narrative 35 words

PDPO grants access and correction rights with a 40-calendar-day statutory response window, but does not provide a general right to erasure/be forgotten, nor a data-portability right. Objection-type rights are largely confined to the direct-marketing opt-out.

Sources and claims (7)
  1. Probable DataGuidance — If a data user rejects or denies a data access request, it must inform the requestor within 40 calendar days from receipt of the request and explain why it cannot comply. observed
  2. Probable DataGuidance — A data correction request must be complied with, and a copy of the corrected personal data provided, within 40 calendar days from receipt under Section 23(1) of the PDPO. observed
  3. Probable DataGuidance — Unlike the GDPR, the PDPO does not provide data subjects with a general right to request erasure or deletion of their personal data; only general requirements exist relating to erasure once data is no longer required for its original purpose. observed
  4. Probable IAPP — An individual is entitled to opt out of direct marketing at any time irrespective of having previously given consent, functioning as PDPO's principal objection-type right. observed
  5. Probable https://www.pcpd.org.hk/english/news_events/media_enquiry/enquiry_20180208.html — Personal Data (Privacy) Ordinance (Cap. 486), s.26(1) — A data user must take all practicable steps to erase personal data no longer required for its purpose, unless erasure is prohibited by law or against the public interest; there is no standalone right to be forgotten.
  6. Probable https://www.pinsentmasons.com/out-law/guides/how-hong-kong-companies-should-deal-with-data-subject-access-requests — Personal Data (Privacy) Ordinance (Cap. 486), s.19(1) — A data user must comply with a data access request within 40 calendar days of receipt, or notify the requestor and refusal reasons within that period if refusing under s.20.
  7. Probable https://hire.legal/article/985 — Personal Data (Privacy) Ordinance (Cap. 486), s.35G(1) — A data subject may at any time require a data user, free of charge, to cease using their personal data for direct marketing, and the data user must comply.

#

Multiple GDPR-equivalent accountability pillars (DPIA, DPO, ROPA, mandatory breach notification) are absent from binding law; only security and retention principles and processor-supervision duties are binding.

Primary frameworkPersonal Data (Privacy) Ordinance (Cap. 486) — DPP2, DPP4; PCPD Privacy Management Programme (non-binding)
Supervisory authorityPCPD
Traffic-light rationale — RedMultiple GDPR-equivalent accountability pillars (DPIA, DPO, ROPA, mandatory breach notification) are absent from binding law; only security and retention principles and processor-supervision duties are binding.

Sub-modules (7)

Accountability & DPIARed

PDPO does not explicitly set out accountability requirements or require DPIAs; the PCPD advocates a voluntary Privacy Management Programme (PMP) as a best-practice accountability framework.

Claims (2):

  • The PDPO does not explicitly set out accountability requirements for data users and processors; the PCPD instead advocates the Privacy Management Programme, a non-binding strategic framework for building privacy infrastructure, including DPO appointment as best practice.
  • Personal Data (Privacy) Ordinance (Cap. 486) — DPIAs are not mandatory under the PDPO; PCPD's PIA information leaflet (revised 2015) and 2018 Ethical Accountability Framework recommend but do not require a PIA before launching projects with significant privacy impact.

DPO requirementsRed

PDPO does not require DPO appointment; the PMP best-practice guide recommends one.

Claims (2):

  • Unlike the GDPR, the PDPO does not require Data Protection Officer appointments; the PCPD's Privacy Management Programme guide (as updated 2019) recommends appointment as best practice only.
  • Personal Data (Privacy) Ordinance (Cap. 486) — No legal requirement to appoint a Data Protection Officer at any headcount or risk threshold; appointing a privacy/compliance officer is a matter of internal governance and PCPD best-practice guidance only.

Ropa requirementsRed

PDPO does not require maintenance of general processing records; only a log book for access/correction requests is mandated.

Claims (2):

  • Unlike the GDPR, the PDPO does not require that general data-processing records be maintained; it only requires a log book be maintained in relation to data subject access and correction requests.
  • Personal Data (Privacy) Ordinance (Cap. 486), ss.14-17 — No general records-of-processing (ROPA) obligation equivalent to GDPR Art.30 exists; the dormant s.14/15 data-user-return and register scheme has never been activated by Commissioner notice.

Joint controller arrangementsAmber

The 2012 Amendment Ordinance imposed express duties on data users to supervise their data processors contractually and otherwise.

Claims (1):

  • The 2012 Amendment Ordinance imposes express obligations on a data user to supervise, through contractual and other means, its data processors to ensure PDPO compliance.

Security measuresAmber

DPP4 imposes a general, non-prescriptive security-of-processing duty; PCPD's 2023 recommendations urge specific technical/organisational measures as best practice.

Claims (7):

  • The PDPO does not stipulate mandatory specific security measures; Data Protection Principle 4 sets only a general, non-prescriptive security-of-processing duty on data users.
  • In September 2023, the PCPD issued non-binding recommendations urging organizations to conduct regular data-security risk assessments and adopt measures such as firewalls, encryption, and the least-privilege principle in compliance with DPP4.
  • Data users (PDPO data controllers) — Must take 'all practicable steps' under DPP4 to protect personal data; breach of an Enforcement Notice is a criminal offence (fine up to HK$50,000 and imprisonment).
  • Personal Data (Privacy) Ordinance (Cap. 486), Schedule 1 DPP2(3)/DPP4(2) — A data user engaging a processor must adopt contractual or other means to prevent the processor retaining data longer than necessary and to prevent unauthorised/accidental access, processing, erasure, loss or use; the data user remains liable for the processor's acts as its agent under s.65.
  • Personal Data (Privacy) Ordinance (Cap. 486), s.65 — A data user remains liable as principal for the acts and practices of its data processor acting as agent, including processors engaged outside Hong Kong.
  • Personal Data (Privacy) Ordinance (Cap 486), Data Protection Principle 4 — PCPD issued an Enforcement Notice against Yau Yat Chuen Garden City Club for DPP4 breach following a ransomware attack.
  • Personal Data (Privacy) Ordinance (Cap 486), Data Protection Principle 4 — Data users must take all practicable steps to protect personal data against unauthorised or accidental access, processing, erasure, loss or use; PCPD found Yau Yat Chuen Garden City Club breached this standard (no authentication controls on third-party remote server access) following a ransomware attack affecting over 9,000 individuals, and issued an Enforcement Notice (published 23 April 2026).

Breach notificationRed

PDPO imposes no mandatory breach-notification obligation; PCPD guidance recommends prompt voluntary notification, and a 2020 consultation proposed mandatory notification but remains unenacted.

Claims (9):

  • The PDPO does not provide for mandatory data breach notifications; the PCPD has instead published non-binding guidance on data breach handling.
  • In a 2020 consultation paper, the Privacy Commissioner and the Constitutional and Mainland Affairs Bureau proposed introducing mandatory data breach notification requirements and data retention periods, with no confirmed timeframe for formal introduction.
  • Hong Kong does not yet have a mandatory personal data breach notification regime under the PDPO; the PCPD has issued updated non-binding 'Guidance on Data Breach Handling and Data Breach Notifications' to guide voluntary notifications.
  • Office of the Privacy Commissioner for Personal Data (PCPD) — As of February 2026, PCPD revived consultation with lawmakers on a mandatory breach-notification framework requiring notice to PCPD and affected individuals within five business days of a breach posing a real risk of significant harm.
  • Office of the Privacy Commissioner for Personal Data (PCPD) — Voluntary data-breach notifications to the PCPD rose from 157 in 2023 to 203 in 2024 to 246 in 2025, with hacking-related incidents up 33% year-on-year in 2025.
  • PDPO (Cap. 486) — Hong Kong does not currently impose a mandatory data-breach notification duty or fixed deadline under the PDPO; notification is voluntary but PCPD-recommended; reform reportedly under discussion but not confirmed in force.
  • Personal Data (Privacy) Ordinance (Cap. 486) — No statutory obligation on data users to notify the PCPD or affected individuals of a data breach; the PCPD's Guidance on Data Breach Handling and Data Breach Notifications (updated June 2023) is non-binding and recommends voluntary notification.
  • Office of the Privacy Commissioner for Personal Data (PCPD) — PCPD received 246 data breach notifications in 2025 (79 public sector, 167 private sector), a 21% increase on 2024's 203 notifications, which itself was a nearly 30% increase on 2023's 157; hacking accounted for about 30% of 2024 incidents and 33% of 2025 incidents.
  • PCPD cessation-notice mechanism (doxxing) — PCPD issued 2,104 cessation notices to 57 online platforms requesting removal of 33,743 doxxing messages, under the voluntary breach-notification and cessation-notice framework of the Personal Data (Privacy) Ordinance.

Retention and disposalGreen

DPP2(2)/Section 26 requires personal data not be kept longer than necessary for the purpose (including any directly related purpose).

Claims (1):

  • Under DPP2(2) and Section 26 of the PDPO, all practicable steps must be taken to ensure personal data is not kept longer than necessary for the fulfilment of the purpose for which it is or is to be used.
Category narrative 53 words

As of February 2026, PCPD is reported to have revived consultation with lawmakers on a mandatory breach-notification framework (five business days for breaches posing real risk of significant harm) and administrative fines (higher of HK$10m or 10% of annual turnover); this remains unenacted. Voluntary breach notifications rose from 157 (2023) to 246 (2025).

Periodic update · new data 2026-10-11

Hong Kong's controller obligations around breach handling remain, for now, without a statutory mandatory-notification requirement. As of February 2026, the Office of the Privacy Commissioner for Personal Data is understood to have revived consultation with lawmakers on a framework that would require data users to notify the PCPD and affected individuals within five business days of a breach posing a real risk of significant harm. This reporting rests on secondary legal-commentary sources rather than a primary PCPD or Legislative Council document, so the specific five-business-day figure and whether the proposal has moved beyond lawmaker briefings to a formally introduced bill are not yet confirmed.

Against this unresolved reform backdrop, the practical breach-reporting picture is nonetheless shifting on the ground: voluntary data-breach notifications to the PCPD rose from 157 in 2023 to 203 in 2024 and to 246 in 2025, with hacking-related incidents up 33 percent year on year in 2025. This rising voluntary-notification trend means Hong Kong data users are already reporting breaches to the PCPD at increasing volume even without a statutory compulsion to do so, which may narrow the practical gap that formal mandatory notification would otherwise close, while the underlying question of statutory timing and administrative-fine exposure remains open.

Outlook

The reform's progression from lawmaker consultation to a formally introduced bill is the key development to track, alongside whether the five-business-day notification window and any associated administrative-fine structure survive into eventual legislative text.

1 further periodic run re-emitted the standing brief unchanged and is not shown.

Sources and claims (24)
  1. Probable DataGuidance — The PDPO does not explicitly set out accountability requirements for data users and processors; the PCPD instead advocates the Privacy Management Programme, a non-binding strategic framework for building privacy infrastructure, including DPO appointment as best practice. observed
  2. Probable DataGuidance — Unlike the GDPR, the PDPO does not require Data Protection Officer appointments; the PCPD's Privacy Management Programme guide (as updated 2019) recommends appointment as best practice only. observed
  3. Probable DataGuidance — Unlike the GDPR, the PDPO does not require that general data-processing records be maintained; it only requires a log book be maintained in relation to data subject access and correction requests. observed
  4. Probable IAPP — The 2012 Amendment Ordinance imposes express obligations on a data user to supervise, through contractual and other means, its data processors to ensure PDPO compliance. observed
  5. Probable DataGuidance — The PDPO does not stipulate mandatory specific security measures; Data Protection Principle 4 sets only a general, non-prescriptive security-of-processing duty on data users. observed
  6. Probable DataGuidance — In September 2023, the PCPD issued non-binding recommendations urging organizations to conduct regular data-security risk assessments and adopt measures such as firewalls, encryption, and the least-privilege principle in compliance with DPP4. observed
  7. Probable DataGuidance — The PDPO does not provide for mandatory data breach notifications; the PCPD has instead published non-binding guidance on data breach handling. observed
  8. Probable IAPP — In a 2020 consultation paper, the Privacy Commissioner and the Constitutional and Mainland Affairs Bureau proposed introducing mandatory data breach notification requirements and data retention periods, with no confirmed timeframe for formal introduction. observed
  9. Probable DataGuidance — Under DPP2(2) and Section 26 of the PDPO, all practicable steps must be taken to ensure personal data is not kept longer than necessary for the fulfilment of the purpose for which it is or is to be used. observed
  10. Probable Linklaters — Hong Kong does not yet have a mandatory personal data breach notification regime under the PDPO; the PCPD has issued updated non-binding 'Guidance on Data Breach Handling and Data Breach Notifications' to guide voluntary notifications. observed
  11. Uncertain https://www.recordinglaw.com/world-laws/world-data-privacy-laws/hong-kong-data-privacy-laws/ — Office of the Privacy Commissioner for Personal Data (PCPD) — As of February 2026, PCPD revived consultation with lawmakers on a mandatory breach-notification framework requiring notice to PCPD and affected individuals within five business days of a breach posing a real risk of significant harm.
  12. Probable https://www.recordinglaw.com/world-laws/world-data-privacy-laws/hong-kong-data-privacy-laws/ — Office of the Privacy Commissioner for Personal Data (PCPD) — Voluntary data-breach notifications to the PCPD rose from 157 in 2023 to 203 in 2024 to 246 in 2025, with hacking-related incidents up 33% year-on-year in 2025.
  13. Probable ask.legal — PDPO (Cap. 486) — Hong Kong does not currently impose a mandatory data-breach notification duty or fixed deadline under the PDPO; notification is voluntary but PCPD-recommended; reform reportedly under discussion but not confirmed in force. observed
  14. Probable DLA Piper — Data users (PDPO data controllers) — Must take 'all practicable steps' under DPP4 to protect personal data; breach of an Enforcement Notice is a criminal offence (fine up to HK$50,000 and imprisonment). observed
  15. Probable PCPD — Personal Data (Privacy) Ordinance (Cap. 486), Schedule 1 DPP2(3)/DPP4(2) — A data user engaging a processor must adopt contractual or other means to prevent the processor retaining data longer than necessary and to prevent unauthorised/accidental access, processing, erasure, loss or use; the data user remains liable for the processor's acts as its agent under s.65. observed
  16. Probable https://www.rpclegal.com/thinking/data-and-privacy/hong-kong-data-protection-cross-border-transfers-of-personal-data/ — Personal Data (Privacy) Ordinance (Cap. 486), s.65 — A data user remains liable as principal for the acts and practices of its data processor acting as agent, including processors engaged outside Hong Kong.
  17. Probable https://www.wipo.int/wipolex/en/legislation/details/6240 — Personal Data (Privacy) Ordinance (Cap. 486), ss.14-17 — No general records-of-processing (ROPA) obligation equivalent to GDPR Art.30 exists; the dormant s.14/15 data-user-return and register scheme has never been activated by Commissioner notice.
  18. Probable https://www.pcpd.org.hk/english/enforcement/data_breach_notification/dbn.html — Personal Data (Privacy) Ordinance (Cap. 486) — No statutory obligation on data users to notify the PCPD or affected individuals of a data breach; the PCPD's Guidance on Data Breach Handling and Data Breach Notifications (updated June 2023) is non-binding and recommends voluntary notification.
  19. Probable https://www.lexmundi.com/guides/data-privacy-guide/jurisdictions/asia-pacific/hong-kong/ — Personal Data (Privacy) Ordinance (Cap. 486) — DPIAs are not mandatory under the PDPO; PCPD's PIA information leaflet (revised 2015) and 2018 Ethical Accountability Framework recommend but do not require a PIA before launching projects with significant privacy impact.
  20. Probable DLA Piper — Personal Data (Privacy) Ordinance (Cap. 486) — No legal requirement to appoint a Data Protection Officer at any headcount or risk threshold; appointing a privacy/compliance officer is a matter of internal governance and PCPD best-practice guidance only. observed
  21. Probable The Standard (HK) — Personal Data (Privacy) Ordinance (Cap 486), Data Protection Principle 4 — PCPD issued an Enforcement Notice against Yau Yat Chuen Garden City Club for DPP4 breach following a ransomware attack. observed
  22. Probable Office of the Privacy Commissioner for Personal Data, Hong Kong — Office of the Privacy Commissioner for Personal Data (PCPD) — PCPD received 246 data breach notifications in 2025 (79 public sector, 167 private sector), a 21% increase on 2024's 203 notifications, which itself was a nearly 30% increase on 2023's 157; hacking accounted for about 30% of 2024 incidents and 33% of 2025 incidents. observed
  23. Probable The Standard (HK) — Personal Data (Privacy) Ordinance (Cap 486), Data Protection Principle 4 — Data users must take all practicable steps to protect personal data against unauthorised or accidental access, processing, erasure, loss or use; PCPD found Yau Yat Chuen Garden City Club breached this standard (no authentication controls on third-party remote server access) following a ransomware attack affecting over 9,000 individuals, and issued an Enforcement Notice (published 23 April 2026). observed
  24. Probable Office of the Privacy Commissioner for Personal Data, Hong Kong — PCPD cessation-notice mechanism (doxxing) — PCPD issued 2,104 cessation notices to 57 online platforms requesting removal of 33,743 doxxing messages, under the voluntary breach-notification and cessation-notice framework of the Personal Data (Privacy) Ordinance. observed

#

The central transfer-restriction mechanism is dormant; only voluntary guidance exists, and adequacy/TIA sub-modules could not be evidenced.

Primary frameworkPersonal Data (Privacy) Ordinance (Cap. 486), Section 33 (not yet in force)
Supervisory authorityPCPD
Traffic-light rationale — RedThe central transfer-restriction mechanism is dormant; only voluntary guidance exists, and adequacy/TIA sub-modules could not be evidenced.

Sub-modules (6)

Transfer mechanismsRed

Section 33 (transfer restriction) remains dormant; PCPD guidance outlines prospective mechanisms (consent, white list, due diligence) that would apply if commenced.

Claims (11):

  • Currently, there are no restrictions in effect concerning the cross-border transfer of personal data from Hong Kong, as Section 33 of the PDPO has never been brought into force.
  • The PCPD has issued a non-binding Guidance on Personal Data Protection in Cross-Border Data Transfer, recommending voluntary compliance with Section 33 as best practice and signalling a possible future commencement of the transfer restriction.
  • No timetable has been announced for the implementation of Section 33; it remains the only section of the PDPO yet to come into effect.
  • Personal Data (Privacy) Ordinance s.33 — Cross-border transfer restriction provision has never been brought into operation.
  • PDPO (Cap. 486) s.33 — PDPO s.33, which would restrict personal-data transfers outside Hong Kong, has been enacted but never brought into force; no statutory prohibition on overseas transfer currently exists.
  • Personal Data (Privacy) Ordinance (Cap. 486), s.33 — Not in force
  • Personal Data (Privacy) Ordinance (Cap. 486), s.33(2) — Six alternative conditions would permit cross-border transfer once in force: white-list destination; reasonable grounds destination has substantially similar protection; written consent of data subject; contractual necessity; Part 8 exemption; or reasonable precautions/due diligence.
  • Personal Data (Privacy) Ordinance (Cap. 486), Schedule 1 DPP3 — A cross-border transfer constitutes 'use' under the Data Protection Principles and requires prescribed consent under DPP3 for a new purpose, unless a Part 8 exemption applies, notwithstanding s.33 being dormant.
  • PCPD Guidance on Recommended Model Contractual Clauses for Cross-Border Transfer of Personal Data — published_2022-05-12
  • PCPD Guidance on Cross-border Data Transfer (2014) — PCPD treats passing personal data to overseas processors and sharing employee/customer data with worldwide affiliates via centralised database as a 'transfer', but mere internet routing via an overseas server does not count.
  • GBA Standard Contract for Cross-boundary Flow of Personal Information — opened to all sectors from 1 November 2024, following a 13 December 2023 launch between Mainland GBA cities and Hong Kong; adoption remains voluntary

Adequacy receivedRed

No evidence located of any foreign regime granting Hong Kong an adequacy-equivalent determination.

Adequacy grantedRed

Since Section 33's white-list mechanism has never been activated, Hong Kong has not granted adequacy-equivalent status to any other jurisdiction.

Claims (1):

  • Currently, there are no restrictions in effect concerning the cross-border transfer of personal data from Hong Kong, as Section 33 of the PDPO has never been brought into force.

SCCs and BCRsRed

Section 33, even if brought into force, does not provide for mechanisms such as BCRs, SCCs, or codes of conduct.

Claims (1):

  • Section 33 of the PDPO does not provide for mechanisms such as binding corporate rules, standard contractual clauses, or codes of conduct, even if it were to come into force.

Transfer impact assessmentRed

No formal transfer-impact-assessment requirement was identified; PCPD guidance recommends general due diligence only.

Claims (1):

  • Personal Data (Privacy) Ordinance (Cap. 486) s.33(2)(f) — s.33 cross-border transfer provision, including the due-diligence exception under s.33(2)(f), has not been brought into force; functions as HK's closest analogue to a transfer impact assessment but is not currently binding

Data localisationAmber

No general PDPO data-localisation mandate exists; sector regulators (e.g., HKMA) impose data-residency/outsourcing controls on regulated entities.

Claims (3):

  • The Outsourcing module (SA-2) of the Hong Kong Monetary Authority's Supervisory Policy Manual requires all authorised institutions to implement proper controls for protection of customer data when entering into an outsourcing arrangement.
  • Personal Data (Privacy) Ordinance (Cap. 486) — No general data-localisation or residency requirement exists under the PDPO.
  • Personal Data (Privacy) Ordinance (Cap. 486) — Hong Kong imposes no general data-localisation requirement (no governmental consent, approval or registration requirement to store or process personal data overseas); sector regulators (HKMA, SFC) separately require risk controls
Category narrative 61 words

Section 33 of the PDPO — the sole cross-border transfer restriction provision — has never been commenced since the Ordinance's 1995/1996 enactment, so no binding transfer restriction currently applies. PCPD has issued non-binding guidance recommending voluntary compliance with Section 33's conditions (consent, a prospective 'white list', due diligence) as best practice. No adequacy decisions received/granted or formal TIA requirement were identified.

Sources and claims (16)
  1. Probable DataGuidance — Currently, there are no restrictions in effect concerning the cross-border transfer of personal data from Hong Kong, as Section 33 of the PDPO has never been brought into force. observed
  2. Probable IAPP — The PCPD has issued a non-binding Guidance on Personal Data Protection in Cross-Border Data Transfer, recommending voluntary compliance with Section 33 as best practice and signalling a possible future commencement of the transfer restriction. observed
  3. Probable DataGuidance — No timetable has been announced for the implementation of Section 33; it remains the only section of the PDPO yet to come into effect. observed
  4. Probable DataGuidance — Section 33 of the PDPO does not provide for mechanisms such as binding corporate rules, standard contractual clauses, or codes of conduct, even if it were to come into force. observed
  5. Probable DataGuidance — The Outsourcing module (SA-2) of the Hong Kong Monetary Authority's Supervisory Policy Manual requires all authorised institutions to implement proper controls for protection of customer data when entering into an outsourcing arrangement. observed
  6. Probable VLO Law Firm — Personal Data (Privacy) Ordinance s.33 — Cross-border transfer restriction provision has never been brought into operation. observed
  7. Probable RecordingLaw — PDPO (Cap. 486) s.33 — PDPO s.33, which would restrict personal-data transfers outside Hong Kong, has been enacted but never brought into force; no statutory prohibition on overseas transfer currently exists. observed
  8. Probable https://www.deacons.com/2023/04/25/hong-kongs-cross-border-data-transfer-regime/ — Personal Data (Privacy) Ordinance (Cap. 486), s.33 — Not in force
  9. Probable https://www.hk-lawyer.org/content/personal-data-protection-cross-border-data-transfer — Personal Data (Privacy) Ordinance (Cap. 486), s.33(2) — Six alternative conditions would permit cross-border transfer once in force: white-list destination; reasonable grounds destination has substantially similar protection; written consent of data subject; contractual necessity; Part 8 exemption; or reasonable precautions/due diligence.
  10. Probable https://www.mayerbrown.com/en/insights/publications/2022/06/hong-kongs-2022-guidance-on-cross-border-data-transfers-implications-for-data-users-and-processors — Personal Data (Privacy) Ordinance (Cap. 486), Schedule 1 DPP3 — A cross-border transfer constitutes 'use' under the Data Protection Principles and requires prescribed consent under DPP3 for a new purpose, unless a Part 8 exemption applies, notwithstanding s.33 being dormant.
  11. Probable https://www.twobirds.com/en/insights/2022/china/hong-kong-pcpd-puts-forward-recommended-model-contractual-clauses — PCPD Guidance on Recommended Model Contractual Clauses for Cross-Border Transfer of Personal Data — published_2022-05-12
  12. Probable https://www.lexology.com/library/detail.aspx?g=08dab810-53b8-4d34-8348-ce2fb029a85d — PCPD Guidance on Cross-border Data Transfer (2014) — PCPD treats passing personal data to overseas processors and sharing employee/customer data with worldwide affiliates via centralised database as a 'transfer', but mere internet routing via an overseas server does not count.
  13. Probable https://privacyrules.com/exploring-hong-kongs-data-localization-and-residency-requirements/ — Personal Data (Privacy) Ordinance (Cap. 486) — No general data-localisation or residency requirement exists under the PDPO.
  14. Probable https://www.digitalpolicy.gov.hk/en/our_work/digital_infrastructure/mainland/gbacbdf/cross-boundary_data_flow/ — GBA Standard Contract for Cross-boundary Flow of Personal Information — opened to all sectors from 1 November 2024, following a 13 December 2023 launch between Mainland GBA cities and Hong Kong; adoption remains voluntary
  15. Probable https://www.hsfkramer.com/notes/employment/2015-03/hong-kong-cross-border-data-transfers — Personal Data (Privacy) Ordinance (Cap. 486) s.33(2)(f) — s.33 cross-border transfer provision, including the due-diligence exception under s.33(2)(f), has not been brought into force; functions as HK's closest analogue to a transfer impact assessment but is not currently binding
  16. Probable https://legal.pwc.de/content/im-fokus/hong-kong-global-data-protection-law-overview.pdf — Personal Data (Privacy) Ordinance (Cap. 486) — Hong Kong imposes no general data-localisation requirement (no governmental consent, approval or registration requirement to store or process personal data overseas); sector regulators (HKMA, SFC) separately require risk controls

#

Financial-sector overlay is well-evidenced; health, telecoms/ePrivacy, employment, and education sub-modules are thin or unevidenced.

Primary frameworkPDPO overlaid by HKMA/Insurance Authority/SFC sectoral guidelines
Supervisory authorityPCPD
Traffic-light rationale — AmberFinancial-sector overlay is well-evidenced; health, telecoms/ePrivacy, employment, and education sub-modules are thin or unevidenced.

Sub-modules (7)

Financial sector overlayAmber

HKMA, Insurance Authority, and SFC issue customer-data circulars/guidelines applicable to licensed institutions, overlaying general PDPO duties.

Claims (3):

  • There are no sectoral data privacy laws as such in Hong Kong, but certain industry-specific requirements are imposed by relevant regulators in respect of customer data held by regulated entities.
  • The Hong Kong Monetary Authority has issued several circulars and guidelines relating to protection and confidentiality of customer data applicable to all licensed banks under the Banking Ordinance (Cap. 155).
  • SFC Circular on Use of External Electronic Data Storage — For SFC-licensed corporations using overseas cloud/data-storage vendors, the vendor must undertake to provide regulatory records and assistance to the SFC on request

Health sector overlayRed

No dedicated health-sector data-privacy statute (e.g., HIPAA-equivalent) was identified in this research pass.

Telecoms and eprivacyRed

No dedicated telecoms/ePrivacy-style cookie-and-communications-specific statute was identified.

Employment dataAmber

Retention limitation rules require employee personal data not be kept beyond the period necessary after termination of employment absent a subsisting reason.

Claims (1):

  • Under DPP2(2)/Section 26, employee personal data must not be kept longer than necessary after the end of employment, unless a subsisting reason requires the employer to hold the data longer.

Credit and scoringAmber

PCPD guidance flags consumer credit data as a category requiring heightened caution in collection and use.

Claims (1):

  • The PCPD has published guidelines on the collection and use of consumer credit data, requiring caution and setting practical guidance on proper collection and use.

educationRed

No dedicated education-sector data-privacy rules were identified in this research pass.

insuranceAmber

The Insurance Authority requires authorised insurers to implement cybersecurity frameworks protecting policyholder personal data.

Claims (1):

  • The Insurance Authority has issued a Guideline on Cybersecurity requiring authorised insurers to implement robust cybersecurity frameworks to protect the personal data of existing or potential policyholders.
Category narrative 40 words

Hong Kong has no standalone sectoral data-privacy statutes; instead, sector regulators (HKMA, Insurance Authority, SFC) issue circulars and guidelines overlaying the PDPO for regulated entities' customer data, and PCPD issues category-specific guidance for sensitive data types including consumer credit data.

No periodic updates recorded in this cycle

Sources and claims (7)
  1. Probable DataGuidance — There are no sectoral data privacy laws as such in Hong Kong, but certain industry-specific requirements are imposed by relevant regulators in respect of customer data held by regulated entities. observed
  2. Probable DataGuidance — The Hong Kong Monetary Authority has issued several circulars and guidelines relating to protection and confidentiality of customer data applicable to all licensed banks under the Banking Ordinance (Cap. 155). observed
  3. Probable DataGuidance — Under DPP2(2)/Section 26, employee personal data must not be kept longer than necessary after the end of employment, unless a subsisting reason requires the employer to hold the data longer. observed
  4. Probable DataGuidance — The PCPD has published guidelines on the collection and use of consumer credit data, requiring caution and setting practical guidance on proper collection and use. observed
  5. Probable DataGuidance — The Insurance Authority has issued a Guideline on Cybersecurity requiring authorised insurers to implement robust cybersecurity frameworks to protect the personal data of existing or potential policyholders. observed
  6. Uncertain dataprotection.gi — No comprehensive data-access-sharing or smart-data portability statute analogous to the EU Data Act exists in Hong Kong; this is a legitimate regime gap. observed
  7. Probable https://www.digfingroup.com/data-localization/ — SFC Circular on Use of External Electronic Data Storage — For SFC-licensed corporations using overseas cloud/data-storage vendors, the vendor must undertake to provide regulatory records and assistance to the SFC on request

#

Direct marketing is green-level binding law; the remaining five sub-modules are unevidenced gaps in a jurisdiction with no dedicated ePrivacy/cookie statute.

Primary frameworkPersonal Data (Privacy) Ordinance (Cap. 486), Part VIA (Direct Marketing)
Supervisory authorityPCPD
Traffic-light rationale — AmberDirect marketing is green-level binding law; the remaining five sub-modules are unevidenced gaps in a jurisdiction with no dedicated ePrivacy/cookie statute.

Sub-modules (6)

Cookies and trackersRed

No dedicated cookie/tracker consent statute was identified distinct from general PDPO principles.

Claims (1):

  • PCPD Information Leaflet on Online Behavioural Tracking — Where a cookie or tracking technology collects personal data, the six Data Protection Principles apply; PCPD recommends disclosure, an opt-out option for non-essential cookies, and a prohibition on super/zombie cookies.

Dark patternsAmber

PCPD guidance criticizes 'bundled consent' application-form designs that force customers to choose between service and direct-marketing data use.

Claims (1):

  • PCPD guidance states it would be unfair for service application forms to force customers to choose between providing personal data for direct marketing or forgoing the service ('bundled consent'), requiring separate voluntary indications instead.

Opt out signalsRed

No evidence of a Global-Privacy-Control-style universal opt-out signal regime was identified.

Clean rooms and dcrRed

No clean-room/data-collaboration-room rules were identified.

Cross context advertisingRed

No CPRA-style 'sale'/'share' cross-context-advertising regime was identified.

Direct marketingGreen

Part VIA requires informed consent/no-objection before use of data in direct marketing, an unconditional opt-out right, and criminalises non-compliant use with fines up to HK$500,000 and up to 3 years' imprisonment.

Claims (3):

  • Part VIA of the PDPO requires a data user to inform individuals, in an easily understandable and readable manner, of an intention to use or provide their data for direct marketing, specifying the data and marketing types, and to obtain consent or no-objection via a free response channel.
  • Section 35E of the PDPO provides for a fine of up to HK$500,000 and up to three years' imprisonment where personal data is used for direct marketing purposes without the individual's informed consent.
  • Personal Data (Privacy) Ordinance (Cap. 486) Part 6A — A data user must inform data subjects of intention to use personal data for direct marketing and obtain consent before doing so; using data for direct marketing without consent is a criminal offence with a fine of up to HK$500,000 and up to three years imprisonment.
Category narrative 41 words

Direct marketing is the best-developed strand of PDPO's commercial-privacy regime (Part VIA), with binding consent/opt-out duties and criminal penalties, plus PCPD guidance against 'bundled consent' dark patterns. No dedicated cookie/tracker law, opt-out-signal regime, clean-room rules, or cross-context-advertising ('sale'/'share') regime was identified.

Sources and claims (5)
  1. Probable IAPP — PCPD guidance states it would be unfair for service application forms to force customers to choose between providing personal data for direct marketing or forgoing the service ('bundled consent'), requiring separate voluntary indications instead. observed
  2. Probable IAPP — Part VIA of the PDPO requires a data user to inform individuals, in an easily understandable and readable manner, of an intention to use or provide their data for direct marketing, specifying the data and marketing types, and to obtain consent or no-objection via a free response channel. observed
  3. Probable IAPP — Section 35E of the PDPO provides for a fine of up to HK$500,000 and up to three years' imprisonment where personal data is used for direct marketing purposes without the individual's informed consent. observed
  4. Probable https://www.mondaq.com/guides/results/20/197/all/hong-kong-data-privacy — Personal Data (Privacy) Ordinance (Cap. 486) Part 6A — A data user must inform data subjects of intention to use personal data for direct marketing and obtain consent before doing so; using data for direct marketing without consent is a criminal offence with a fine of up to HK$500,000 and up to three years imprisonment.
  5. Probable https://www.pcpd.org.hk/english/publications/files/online_tracking_e.pdf — PCPD Information Leaflet on Online Behavioural Tracking — Where a cookie or tracking technology collects personal data, the six Data Protection Principles apply; PCPD recommends disclosure, an opt-out option for non-essential cookies, and a prohibition on super/zombie cookies.

#

AI governance is active but entirely soft-law; national-security carve-outs materially limit PCPD's supervisory reach; profiling/ADM-transparency/genetic-data sub-modules are unevidenced.

Primary frameworkPCPD Artificial Intelligence: Model Personal Data Protection Framework (2024, non-binding); PDPO general principles
Supervisory authorityPCPD
Traffic-light rationale — AmberAI governance is active but entirely soft-law; national-security carve-outs materially limit PCPD's supervisory reach; profiling/ADM-transparency/genetic-data sub-modules are unevidenced.

Sub-modules (6)

Profiling restrictionsRed

No Art.22-style statutory profiling restriction was identified in the PDPO.

Automated decision making transparencyRed

No statutory ADM-transparency or explanation right was identified beyond general AI governance guidance.

Claims (1):

  • PCPD Model Personal Data Protection Framework - Protecting Personal Data Privacy in the Use of Agentic AI — A human-in-the-loop mechanism retaining final control over decisions and transparency under DPP1(3) and DPP5, for organisations deploying agentic AI.

AI risk assessmentsAmber

PCPD's AI compliance-check programme and Model Framework recommend (non-binding) risk assessments, governance structures, and audits for AI systems.

Claims (7):

  • On 11 June 2024, the PCPD published the Artificial Intelligence: Model Personal Data Protection Framework, providing recommendations and best practices for AI governance covering procurement, implementation, and use of AI systems including generative AI, building on its 2021 Guidance on the Ethical Development and Use of AI.
  • The PCPD's 2024-25 Annual Report describes the AI Model Framework as one of the first explicit regional frameworks for regulating AI, reflecting the Commissioner's stated aim to balance innovation and security in AI.
  • PCPD compliance checks on 60 organizations found 80% used AI in daily operations (a 5% increase from 2024), with the PCPD recommending AI governance structures, comprehensive risk assessments, and regular audits as best practice.
  • In May 2026, PCPD published findings of a third round of AI compliance checks covering 60 organisations across 16 sectors; none of PCPD's AI guidance documents has s.13 binding code-of-practice status.
  • Office of the Privacy Commissioner for Personal Data — PCPD conducted compliance checks in May 2025 on 60 organisations' use of AI, finding 80% (48/60) reported using AI in daily operations, prompting new practical AI-adoption guidance.
  • Office of the Privacy Commissioner for Personal Data — Completed compliance checks on 60 organisations regarding AI's impact on personal data privacy; found no PDPO contravention; flagged agentic AI as elevated risk area
  • Office of the Privacy Commissioner for Personal Data — PCPD Safeguarding Personal Data AI Sandbox open for applications until 30 October 2026, providing access to PCPD AI privacy guidance, DPO Generative AI Guideline and technical advice from Cyberport/HKPC

Biometric regimeAmber

PCPD guidance flags biometric data, alongside HKID numbers and credit data, as requiring heightened caution, without a codified statutory biometric regime.

Claims (2):

  • The PCPD has published guidelines regarding the collection and use of biometric data, alongside Hong Kong identity cards and consumer credit data, highlighting the need for caution absent a codified statutory biometric regime.
  • Worldcoin (iris/biometric-scanning project, Hong Kong) — PCPD investigation (commenced January 2024) found the project contravened the PDPO.

Genetic dataRed

No dedicated genetic-data regime was identified in this research pass.

State surveillance carveoutsRed

The PCPD's ability to supervise and regulate authorities' actions under the National Security Law appears fairly limited, as the NSL expressly takes precedence over inconsistent local laws.

Claims (1):

  • In relation to the exercise of authorities' powers under the National Security Law, the PCPD's ability to supervise and regulate compliance with the PDPO appears fairly limited, as the NSL expressly takes precedence over inconsistent provisions of other Hong Kong laws.
Category narrative 56 words

Hong Kong has no binding AI-specific statute; the PCPD's June 2024 AI Model Personal Data Protection Framework and 2021 Ethical AI Guidance are non-binding best-practice instruments. PCPD conducts periodic AI compliance checks. Biometric data attracts special-caution guidance but no codified regime. State-surveillance carve-outs exist under the National Security Law, which the PCPD's supervisory reach cannot override.

Periodic update · new data 2026-10-20

Two developments mark this module as active for Hong Kong. The Privacy Commissioner for Personal Data's investigation into the Worldcoin iris-scanning biometric project, commenced in January 2024, has concluded with a finding that the project contravened the Personal Data (Privacy) Ordinance, as recorded in a paper submitted to the Legislative Council. The specific Data Protection Principle found to have been breached, and the full detail of any enforcement outcome beyond the finding of contravention itself, were not independently confirmed from a source beyond that Legislative Council summary, so this finding is reported at the level of detail the available record supports.

Separately, the PCPD published, on 25 August 2026, a supplement to its Model Personal Data Protection Framework titled to address protection of personal data privacy in the use of agentic artificial intelligence. This supplements the Commissioner's existing 2024 Model Framework and extends non-binding guidance into a category of automated, autonomously-acting AI systems that the original framework did not specifically address. As with the original framework, this guidance carries no binding legal force and does not itself create new statutory obligations under the Personal Data (Privacy) Ordinance.

Taken together, these two developments indicate that Hong Kong's approach to biometric and algorithmic governance continues to operate primarily through the PCPD's existing enforcement powers under the Ordinance and through non-binding guidance, rather than through a dedicated biometric- or AI-specific statute. The Worldcoin finding demonstrates that biometric data processing is being actively reviewed and found wanting under the existing Data Protection Principles framework, even without AI- or biometric-specific legislation in place.

Outlook

Whether the Worldcoin investigation results in a published Enforcement Notice, and what specific remedial steps or restrictions it imposes, is the most consequential open question in this module going forward. Equally, whether the PCPD's Agentic-AI guidance supplement is followed by further sector-specific or binding rule-making, or remains non-binding guidance indefinitely, will determine whether Hong Kong's algorithmic-governance approach continues to rely solely on existing DPP-based enforcement extended by interpretation, or moves toward more specific statutory footing.

1 earlier distinct update
Periodic update · new data 2026-10-18

Two developments mark this module as active this cycle for Hong Kong. The Privacy Commissioner for Personal Data's investigation into the Worldcoin iris-scanning biometric project, commenced in January 2024, has concluded with a finding that the project contravened the Personal Data (Privacy) Ordinance, as recorded in a paper submitted to the Legislative Council. The specific Data Protection Principle found to have been breached, and the full detail of any enforcement outcome beyond the finding of contravention itself, were not independently confirmed from a source beyond that Legislative Council summary, so this finding is reported at the level of detail the available record supports.

Separately, the PCPD published, on 25 August 2026, a supplement to its Model Personal Data Protection Framework titled to address protection of personal data privacy in the use of agentic artificial intelligence. This supplements the Commissioner's existing 2024 Model Framework and extends non-binding guidance into a category of automated, autonomously-acting AI systems that the original framework did not specifically address. As with the original framework, this guidance carries no binding legal force and does not itself create new statutory obligations under the Personal Data (Privacy) Ordinance.

Taken together, these two developments indicate that Hong Kong's approach to biometric and algorithmic governance continues to operate primarily through the PCPD's existing enforcement powers under the Ordinance and through non-binding guidance, rather than through a dedicated biometric- or AI-specific statute. The Worldcoin finding demonstrates that biometric data processing is being actively reviewed and found wanting under the existing Data Protection Principles framework, even without AI- or biometric-specific legislation in place.

Outlook

Whether the Worldcoin investigation results in a published Enforcement Notice, and what specific remedial steps or restrictions it imposes, is the most consequential open question in this module going forward. Equally, whether the PCPD's Agentic-AI guidance supplement is followed by further sector-specific or binding rule-making, or remains non-binding guidance indefinitely, will determine whether Hong Kong's algorithmic-governance approach continues to rely solely on existing DPP-based enforcement extended by interpretation, or moves toward more specific statutory footing.

1 further periodic run re-emitted the standing brief unchanged and is not shown.

Sources and claims (12)
  1. Probable DataGuidance — On 11 June 2024, the PCPD published the Artificial Intelligence: Model Personal Data Protection Framework, providing recommendations and best practices for AI governance covering procurement, implementation, and use of AI systems including generative AI, building on its 2021 Guidance on the Ethical Development and Use of AI. observed
  2. Probable IAPP — The PCPD's 2024-25 Annual Report describes the AI Model Framework as one of the first explicit regional frameworks for regulating AI, reflecting the Commissioner's stated aim to balance innovation and security in AI. observed
  3. Probable IAPP — PCPD compliance checks on 60 organizations found 80% used AI in daily operations (a 5% increase from 2024), with the PCPD recommending AI governance structures, comprehensive risk assessments, and regular audits as best practice. observed
  4. Probable DataGuidance — The PCPD has published guidelines regarding the collection and use of biometric data, alongside Hong Kong identity cards and consumer credit data, highlighting the need for caution absent a codified statutory biometric regime. observed
  5. Probable DataGuidance — In relation to the exercise of authorities' powers under the National Security Law, the PCPD's ability to supervise and regulate compliance with the PDPO appears fairly limited, as the NSL expressly takes precedence over inconsistent provisions of other Hong Kong laws. observed
  6. Probable Linklaters — In May 2026, PCPD published findings of a third round of AI compliance checks covering 60 organisations across 16 sectors; none of PCPD's AI guidance documents has s.13 binding code-of-practice status. observed
  7. Probable Legislative Council of Hong Kong — Worldcoin (iris/biometric-scanning project, Hong Kong) — PCPD investigation (commenced January 2024) found the project contravened the PDPO. observed
  8. Probable Dentons — PCPD Model Personal Data Protection Framework - Protecting Personal Data Privacy in the Use of Agentic AI — A human-in-the-loop mechanism retaining final control over decisions and transparency under DPP1(3) and DPP5, for organisations deploying agentic AI. observed
  9. Probable https://www.mayerbrown.com/en/insights/publications/2025/10/ai-governance-practical-guidance-from-hong-kong-privacy-commissioner-for-personal-data — Office of the Privacy Commissioner for Personal Data — PCPD conducted compliance checks in May 2025 on 60 organisations' use of AI, finding 80% (48/60) reported using AI in daily operations, prompting new practical AI-adoption guidance.
  10. Probable RecordingLaw — Personal Data (Privacy) Ordinance (Cap. 486) — Government and PCPD have repeatedly proposed amending the PDPO to add mandatory breach notification, administrative fines (reported as proposed at the higher of HK$10 million or 10% of annual turnover), a sensitive personal data category, data retention-policy duties, and direct regulation of data processors; no bill had commenced any of these as of the cycle cutoff. observed
  11. Probable https://www.pcpd.org.hk/english/resources_centre/publications/guidance/guidance.html — Office of the Privacy Commissioner for Personal Data — Completed compliance checks on 60 organisations regarding AI's impact on personal data privacy; found no PDPO contravention; flagged agentic AI as elevated risk area
  12. Probable https://www.pcpd.org.hk/english/artificial_intelligence/index.html — Office of the Privacy Commissioner for Personal Data — PCPD Safeguarding Personal Data AI Sandbox open for applications until 30 October 2026, providing access to PCPD AI privacy guidance, DPO Generative AI Guideline and technical advice from Cyberport/HKPC

#

This is a legitimate regulatory gap: no comprehensive children/vulnerable-groups regime exists in the PDPO beyond passing references to minors.

Primary frameworkPersonal Data (Privacy) Ordinance (Cap. 486) — no dedicated minors regime
Supervisory authorityPCPD
Traffic-light rationale — RedThis is a legitimate regulatory gap: no comprehensive children/vulnerable-groups regime exists in the PDPO beyond passing references to minors.

Sub-modules (5)

Age verificationRed

No statutory age-verification requirement was identified.

Minor profiling bansRed

No minor-specific profiling ban was identified.

Education settingsRed

No education-setting-specific data rules were identified.

Dependent adultsRed

No dependent-adult-specific protections were identified.

Category narrative 32 words

PDPO makes passing reference to 'minors' but does not codify a specific age of consent, parental-consent mechanism, or minor-specific profiling ban comparable to GDPR Art.8. No education-setting-specific or dependent-adult-specific rules were identified.

Sources and claims (2)
  1. Probable DataGuidance — The PDPO makes references to 'minors' but is less clear than the GDPR regarding consent from guardians and privacy notices aimed at minors, and does not define a specific age of consent threshold. observed
  2. Probable Office of the Privacy Commissioner for Personal Data (PCPD) — PCPD Guidance: Safeguarding Children's Online Privacy — PCPD published non-statutory guidance (23 April 2026) advising parents and teachers on protecting children's personal data online, including parental controls, privacy-setting review, consent before sharing photos, and prudent use of AI tools, accompanying the Yau Yat Chuen investigation report. observed

#

Enforcement powers and penalties are robust and binding (green-level for that sub-module), but collective redress and regulator-capacity sub-modules are unevidenced gaps, pulling the module to amber.

Primary frameworkPersonal Data (Privacy) Ordinance (Cap. 486)
Supervisory authorityPCPD
Traffic-light rationale — AmberEnforcement powers and penalties are robust and binding (green-level for that sub-module), but collective redress and regulator-capacity sub-modules are unevidenced gaps, pulling the module to amber.

Sub-modules (6)

Regulator powers and penaltiesGreen

PCPD can investigate, issue enforcement notices, and (since 2021) conduct criminal investigations/prosecutions for doxxing, with tiered penalties up to HK$1,000,000 and 5 years' imprisonment.

Claims (11):

  • The PCPD has various investigative powers, including the right to undertake investigations and inquiries and issue enforcement notices in the event of PDPO contraventions.
  • The 2021 Amendment Ordinance removed the prior requirement that an enforcement notice could only be issued where the offending act was likely to continue or repeat, and increased penalties for data users breaching multiple or repeated enforcement notices.
  • The 2021 anti-doxxing regime creates a two-tier offence: a Tier 1 summary offence carrying up to two years' imprisonment and a HK$100,000 fine, and a Tier 2 indictable offence, where actual harm is caused, carrying up to five years' imprisonment and a HK$1,000,000 fine.
  • The PCPD has the power to conduct criminal investigations and institute prosecutions for doxxing cases, and to issue cessation notices to Hong Kong or non-Hong Kong persons or service providers to demand removal of doxxing content.
  • The PDPO has historically lacked GDPR-style direct administrative fining power for the PCPD; reform proposals to change this remain under study, not enacted.
  • Personal Data (Privacy) Ordinance, Cap.486 — Failure to comply with a PCPD enforcement notice is a criminal offence punishable by a fine of up to HK$50,000 and imprisonment for up to two years, plus a daily penalty of HK$1,000 for continuing non-compliance.
  • Privacy Commissioner for Personal Data — No power to impose administrative fines; every monetary penalty requires court conviction. Enforcement Notice breach max HK$50,000 fine and imprisonment.
  • Personal Data (Privacy) Ordinance (Cap. 486), s.50A — Non-compliance with an enforcement notice: first conviction fine at level 5 (HK$50,000) plus 2 years' imprisonment and daily fine of HK$1,000; subsequent conviction fine at level 6 (HK$100,000) plus 2 years and daily fine of HK$2,000.
  • Personal Data (Privacy) Ordinance (Cap. 486), s.64 — Unauthorised disclosure of personal data causing psychological harm, or with intent to gain or cause loss, is punishable on indictment by a fine of HK$1,000,000 and imprisonment for 5 years.
  • Personal Data (Privacy) (Amendment) Ordinance 2021 (doxxing), s.64(3A)-(3D) — First-tier doxxing offence: summary conviction fine at level 6 (HK$100,000) and 2 years' imprisonment. Second-tier (causing specified harm): on indictment, fine of HK$1,000,000 and 5 years' imprisonment.
  • Personal Data (Privacy) Ordinance (Cap. 486), ss.35E/35K — Using personal data for direct marketing without the s.35C notice/consent steps: fine up to HK$500,000 and imprisonment up to 3 years. Providing data to another for direct marketing for gain without written consent: fine up to HK$1,000,000 and imprisonment up to 5 years.

Enforcement activity indexAmber

Documented enforcement activity includes multiple doxxing arrests since the 2021 anti-doxxing law and the first PDPO imprisonment for misleading the PCPD during an investigation.

Claims (7):

  • The PCPD announced the first prison sentence under Section 50B(1)(c)(i) of the PDPO for knowingly making a false or misleading statement to the Commissioner during an investigation.
  • The PCPD arrested an individual for posting personal information of three people on social media in a commercial dispute, marking the second arrest under the anti-doxxing legislation approved in September 2021.
  • From 8 Oct 2021 commencement to 31 Dec 2025, PCPD handled 3,634 doxxing cases, issued 2,104 cessation notices to 57 platforms, initiated 519 criminal investigations, referred 150 cases to police, and secured 43 convictions of 55 prosecuted persons.
  • Hong Kong personal data breach notifications — Personal data breach notifications/detections rose to 217 cases in 2024, up from a stable baseline of roughly 100 cases per year in prior years.
  • Yau Yat Chuen Garden City Club — PCPD published an Investigation Report on 23 April 2026 on a ransomware-caused data breach, finding DPP4 security-measure failures including absent authentication for third-party remote server access, and served an Enforcement Notice.
  • Yau Yat Chuen Garden City Club — PCPD served an Enforcement Notice on the Club after a ransomware attack exposed personal data of 9,045 members; found failure to take all practicable steps to protect personal data (DPP4)
  • PCPD issued an enforcement notice against Cathay Pacific Airways.

Regulator funding and capacityRed

No regulator funding or headcount data was identified in this research pass.

Collective redress and class actionsRed

No dedicated class-action mechanism for data subjects was identified beyond the individual legal-assistance scheme.

Private right of actionAmber

The 2012 Amendment Ordinance introduced a legal-assistance scheme enabling aggrieved individuals to pursue compensation claims arising from PDPO contraventions.

Claims (1):

  • The 2012 Amendment Ordinance introduced, among other measures, a legal assistance scheme for aggrieved individuals seeking to bring proceedings arising from PDPO contraventions.

Recent developments 180dAmber

The PCPD's 2024-25 Annual Report continues to emphasize AI governance, data security, and digital trust as regulatory priorities.

Claims (1):

  • The PCPD's 2024-25 Annual Report, 'Leveraging Artificial Intelligence for a New Digital Privacy Era,' concentrates on AI's impacts on data security and digital trust as a continuing regulatory priority.
Category narrative 44 words

PCPD's 2025 work report shows 4,228 complaints (+23% YoY), 435 compliance checks (+9%), and 308 doxxing cases with 147 criminal investigations and 32 cessation notices issued to 13 platforms (compliance rate above 98%). Maximum enforcement-notice non-compliance penalty remains HK$50,000 fine and two years' imprisonment.

Periodic update · new data 2026-10-18

The Privacy Commissioner for Personal Data published an Investigation Report on 23 April 2026 concerning a ransomware-caused data breach at Yau Yat Chuen Garden City Club. The investigation found failures under Data Protection Principle 4's security-measures standard, specifically identifying an absence of authentication controls governing third-party remote server access as a contributing cause of the breach. Following this finding, the Commissioner served an Enforcement Notice on the organisation. This action illustrates the PCPD's standing approach to security-measure failures: under the Ordinance, breach of an Enforcement Notice itself constitutes a criminal offence, carrying a fine of up to HK$50,000 and imprisonment, though the underlying security-measure failure identified in an Investigation Report is not itself separately finable absent a subsequent Enforcement Notice breach.

This action sits within Hong Kong's distinctive enforcement-power ceiling: the Commissioner has no power to impose administrative fines directly, and every monetary penalty under the Ordinance requires a court conviction, most commonly for a subsequent breach of an Enforcement Notice rather than for the underlying data-protection failure itself. This structure means the Commissioner's primary enforcement tool for a security-measures failure such as this one is the Enforcement Notice itself, which compels specific remedial steps rather than imposing an immediate financial penalty.

This enforcement action also arrives alongside separately-reported statistics on voluntary data-breach notification: the PCPD received 246 voluntary notifications in 2025, a 21 percent increase on 203 in 2024, with roughly a third involving hacking. Hong Kong continues to have no statutory mandatory breach-notification requirement, so the Yau Yat Chuen matter and the broader 2025 notification statistics both arise from a voluntary-notification and Commissioner-initiated-investigation regime rather than a mandatory reporting duty.

Outlook

The Yau Yat Chuen Enforcement Notice, read alongside rising voluntary breach-notification volumes and roughly a third of 2025 notifications involving hacking, points to continuing growth in ransomware and hacking-related data-security incidents within Hong Kong notwithstanding the absence of a mandatory reporting duty. Whether this pattern eventually revives the stalled 2020 PDPO reform package, including its proposed mandatory breach-notification and administrative fining-power provisions, remains an open structural question beyond the Commissioner's current enforcement toolkit.

2 earlier distinct updates
Periodic update · new data 2026-10-11

The Office of the Privacy Commissioner for Personal Data's own 2025 annual reporting, released via a February 2026 press statement, shows a marked rise in enforcement activity. The PCPD received 4,228 complaints in 2025, up 23 percent on the prior year, and initiated 435 compliance checks, up 9 percent. It handled 308 doxxing cases, pursuing 147 criminal investigations and issuing 32 cessation notices to 13 platforms, while reporting a compliance rate above 98 percent. These figures come directly from the regulator's own publication and represent a confirmed escalation in enforcement volume across complaints handling, proactive compliance checking, and doxxing-specific action.

This enforcement intensification occurs within a penalty structure under the Personal Data (Privacy) Ordinance, Cap.486 that has not itself changed: failure to comply with a PCPD enforcement notice remains a criminal offence, punishable by a fine of up to HK$50,000 and imprisonment for up to two years, together with a daily penalty of HK$1,000 for continuing non-compliance. The combination of rising enforcement activity and a long-standing, comparatively modest statutory penalty ceiling creates a widening gap between the volume of regulatory action and the maximum financial consequence available under current law, a gap the revived breach-notification and administrative-fining reform discussed under Controller/Processor Duties would be intended to address.

Outlook

Whether 2026 enforcement volumes continue the 2025 trajectory, particularly in doxxing-related cessation notices, is the principal indicator to watch, alongside whether the unchanged statutory penalty ceiling becomes a more visible point of public or legislative pressure given the widening gap between enforcement activity and available sanctions.

Periodic update · new data 2026-09-28

Hong Kong's data-protection enforcement and redress picture intensified this cycle in observed volume even as the underlying statutory architecture remained unchanged. Personal data breach notifications and detections rose to 217 cases in 2024, a marked increase from a stable baseline of roughly 100 cases per year in prior years, according to a January 2025 government reply to the Legislative Council. This is a confirmed, primary-sourced government figure and represents more than a doubling of the prior stable baseline.

This rise in observed breach activity has occurred despite the Personal Data (Privacy) Ordinance still lacking a mandatory personal data breach notification regime. The Privacy Commissioner for Personal Data responded to this gap through non-binding guidance rather than legislation: updated 'Guidance on Data Breach Handling and Data Breach Notifications' was issued in 2026, clarifying the Commissioner's expectations for breach handling without creating a statutory notification duty. The Personal Data (Privacy) Ordinance also continues to lack a direct administrative fining power for the Privacy Commissioner of the kind available under the European Union's General Data Protection Regulation; reform proposals addressing mandatory notification, processor regulation and administrative fines remain under study rather than enacted.

A supporting judgment drawn from this cycle's evidence assesses that Hong Kong's enforcement posture is intensifying in observed practice even as the binding statutory gaps — no mandatory notification duty, no direct administrative fining power — remain unresolved, widening the gap between observed breach volume and the regulator's binding legal powers to compel disclosure or penalise non-compliance.

It remains unconfirmed whether any amendment bill addressing mandatory breach notification, processor regulation, or administrative fining powers has been introduced to the Legislative Council since reports from autumn 2024 indicated the reform effort had been placed on hold; this is recorded as an open gap rather than an assertion that no such bill exists.

Outlook

The central question to watch is whether the stalled reform package — covering mandatory breach notification, processor regulation and administrative fining powers — is revived and introduced to the Legislative Council, particularly given that observed breach volume more than doubled in 2024 relative to the prior stable baseline. Until such a bill is introduced, organisations will continue to operate under the Privacy Commissioner's non-binding guidance rather than a statutory notification duty, and confirmation of the current legislative status of any reform bill would materially sharpen this cycle's assessment.

1 further periodic run re-emitted the standing brief unchanged and is not shown.

Sources and claims (20)
  1. Probable DataGuidance — The PCPD has various investigative powers, including the right to undertake investigations and inquiries and issue enforcement notices in the event of PDPO contraventions. observed
  2. Probable IAPP — The 2021 Amendment Ordinance removed the prior requirement that an enforcement notice could only be issued where the offending act was likely to continue or repeat, and increased penalties for data users breaching multiple or repeated enforcement notices. observed
  3. Probable DataGuidance — The 2021 anti-doxxing regime creates a two-tier offence: a Tier 1 summary offence carrying up to two years' imprisonment and a HK$100,000 fine, and a Tier 2 indictable offence, where actual harm is caused, carrying up to five years' imprisonment and a HK$1,000,000 fine. observed
  4. Probable DataGuidance — The PCPD has the power to conduct criminal investigations and institute prosecutions for doxxing cases, and to issue cessation notices to Hong Kong or non-Hong Kong persons or service providers to demand removal of doxxing content. observed
  5. Probable IAPP — The PCPD announced the first prison sentence under Section 50B(1)(c)(i) of the PDPO for knowingly making a false or misleading statement to the Commissioner during an investigation. observed
  6. Probable IAPP — The PCPD arrested an individual for posting personal information of three people on social media in a commercial dispute, marking the second arrest under the anti-doxxing legislation approved in September 2021. observed
  7. Probable IAPP — The 2012 Amendment Ordinance introduced, among other measures, a legal assistance scheme for aggrieved individuals seeking to bring proceedings arising from PDPO contraventions. observed
  8. Probable IAPP — The PCPD's 2024-25 Annual Report, 'Leveraging Artificial Intelligence for a New Digital Privacy Era,' concentrates on AI's impacts on data security and digital trust as a continuing regulatory priority. observed
  9. Probable https://www.pcpd.org.hk/misc/dpoc/newsletter189.html — From 8 Oct 2021 commencement to 31 Dec 2025, PCPD handled 3,634 doxxing cases, issued 2,104 cessation notices to 57 platforms, initiated 519 criminal investigations, referred 150 cases to police, and secured 43 convictions of 55 prosecuted persons.
  10. Probable Government of Hong Kong SAR — Hong Kong personal data breach notifications — Personal data breach notifications/detections rose to 217 cases in 2024, up from a stable baseline of roughly 100 cases per year in prior years. observed
  11. Probable HFW — A new era for data protection in Hong Kong — The PDPO has historically lacked GDPR-style direct administrative fining power for the PCPD; reform proposals to change this remain under study, not enacted. observed
  12. Probable DLA Piper Data Protection Laws of the World — Personal Data (Privacy) Ordinance, Cap.486 — Failure to comply with a PCPD enforcement notice is a criminal offence punishable by a fine of up to HK$50,000 and imprisonment for up to two years, plus a daily penalty of HK$1,000 for continuing non-compliance. observed
  13. Probable DLA Piper — Privacy Commissioner for Personal Data — No power to impose administrative fines; every monetary penalty requires court conviction. Enforcement Notice breach max HK$50,000 fine and imprisonment. observed
  14. Probable PCPD — Yau Yat Chuen Garden City Club — PCPD published an Investigation Report on 23 April 2026 on a ransomware-caused data breach, finding DPP4 security-measure failures including absent authentication for third-party remote server access, and served an Enforcement Notice. observed
  15. Probable Office of the Privacy Commissioner for Personal Data (PCPD) — Yau Yat Chuen Garden City Club — PCPD served an Enforcement Notice on the Club after a ransomware attack exposed personal data of 9,045 members; found failure to take all practicable steps to protect personal data (DPP4) observed
  16. Probable https://www.pcpd.org.hk/misc/files/grg_private_sector.pdf — Personal Data (Privacy) Ordinance (Cap. 486), s.50A — Non-compliance with an enforcement notice: first conviction fine at level 5 (HK$50,000) plus 2 years' imprisonment and daily fine of HK$1,000; subsequent conviction fine at level 6 (HK$100,000) plus 2 years and daily fine of HK$2,000.
  17. Probable https://www.pcpd.org.hk/english/news_events/media_statements/press_20190711.html — Personal Data (Privacy) Ordinance (Cap. 486), s.64 — Unauthorised disclosure of personal data causing psychological harm, or with intent to gain or cause loss, is punishable on indictment by a fine of HK$1,000,000 and imprisonment for 5 years.
  18. Probable https://www.legco.gov.hk/yr20-21/english/brief/cmabcr72245_20210714-e.pdf — Personal Data (Privacy) (Amendment) Ordinance 2021 (doxxing), s.64(3A)-(3D) — First-tier doxxing offence: summary conviction fine at level 6 (HK$100,000) and 2 years' imprisonment. Second-tier (causing specified harm): on indictment, fine of HK$1,000,000 and 5 years' imprisonment.
  19. Probable https://www.nortonrosefulbright.com/en/knowledge/publications/69fc1091/hong-kong-regulators-step-up-enforcement-on-personal-data-protection — Personal Data (Privacy) Ordinance (Cap. 486), ss.35E/35K — Using personal data for direct marketing without the s.35C notice/consent steps: fine up to HK$500,000 and imprisonment up to 3 years. Providing data to another for direct marketing for gain without written consent: fine up to HK$1,000,000 and imprisonment up to 5 years.
  20. Probable https://www.jdsupra.com/authors/mark-parsons/page2/page3/page4 — PCPD issued an enforcement notice against Cathay Pacific Airways.
No categories match.

No categories match your current search or filter selection.

Provenance and declared absence

Disclosure model: category cards load OPEN; narratives render in full; standing narratives load as a clamped teaser with an explicit “read full” control carrying the true word count. No text is hidden without disclosing how much of it there is.

Sub-modules are DP-specific nested subsections with their own real per-sub-module traffic light, rendered under each category across all regulatory modules.

Traffic-light dots are REAL data (baseline.<category>.traffic_light), not renderer-invented taxonomy, and are never suppressed -- unlike WPM, where a RAG dot would be forbidden as invented severity.

Family/accent taxonomy is renderer-level presentation config, not a JID field; it decorates the RAG dot, it does not replace it. Colour is always duplicated in text and is never the sole carrier of meaning.

Suppressed by doctrine: derived risk score. Not shown on this page.

Band honesty: uncertainty bands are computed against a frozen build clock of 2026-11-17. A year-precision row is never promoted into a tighter band.

Envelope: baseline resolved at jurisdiction_json.baseline; 10 categories, 57 sub-module(s), 114 claim(s) (114 category placement(s)), 42 source(s) in the cumulative register.

Audit trail

Machine checkChallenged on 25 Oct 2026: upheld (17 confirmed against the cited source; 4 could not be checked). An automated, adversarial test run by a second model; no person has assessed the result.

Think something on this page is wrong? Report an error.

GDPR article map

Cross-reference: which category/sub-module covers each UK GDPR article (14 mapped).

Show article map
GDPR article to category mapping
ArticleCategorySub-module
Art. 5Controller/Processor Dutiesaccountability and dpia
Art. 6Lawful Processing & Special Datalawful bases
Art. 7Lawful Processing & Special Dataconsent thresholds
Art. 9Lawful Processing & Special Dataspecial categories
Art. 22Algorithmic, Biometric & Surveillance Governanceautomated decision making transparency
Art. 25Controller/Processor Dutiesaccountability and dpia
Art. 28Controller/Processor Dutiesjoint controller arrangements
Art. 30Controller/Processor Dutiesropa requirements
Art. 35Controller/Processor Dutiesaccountability and dpia
Art. 13-22Data Subject Rightsaccess right
Art. 32-34Controller/Processor Dutiessecurity measures
Art. 37-39Controller/Processor Dutiesdpo requirements
Art. 44-49Cross-Border & Adequacytransfer mechanisms
Art. 77-84Enforcement & Redressregulator powers and penalties