OneClickComply
    Hong Kong Personal Data (Privacy) OrdinanceSupported in OneClickComply

    Meet Hong Kong PDPO obligations with evidence you can show

    The PDPO, or Personal Data (Privacy) Ordinance (Cap. 486), is Hong Kong's data protection law, enacted in 1995 and in force since 20 December 1996. It sets six Data Protection Principles that govern how personal data is collected, kept accurate, used, secured, explained and made accessible. The Privacy Commissioner for Personal Data (PCPD) oversees and enforces it.

    PDPO Aligned
    Automated Evidence
    OneClickFix Enabled
    Continuous Monitoring
    In-House Audit Team
    Who needs PDPO

    Is PDPO right for your organisation?

    Any organisation or person that controls the collection, holding, processing or use of personal data in or from Hong Kong is a data user under the PDPO, whatever its size or sector. That includes overseas companies handling the data of Hong Kong customers or staff through a Hong Kong presence. It matters most when you launch services in Hong Kong, run direct marketing, use data processors or answer due diligence from Hong Kong clients.

    It is a legal or regulatory requirement for organisations in scope.

    PDPO at a glance
    Issued by
    Hong Kong SAR Legislative Council (Cap. 486)
    Enforced by
    Privacy Commissioner for Personal Data (PCPD)
    In force since
    20 December 1996
    Major amendments
    2012 (direct marketing, enforcement) and 2021 (anti-doxxing, in force 8 October 2021)
    Core obligations
    Six Data Protection Principles (Schedule 1)
    Enforcement route
    PCPD investigations and enforcement notices; breaching a notice is a criminal offence
    Maximum penalty
    HK$1,000,000 and 5 years' imprisonment for the most serious direct marketing and disclosure offences
    Type
    Law (mandatory)
    Region
    Hong Kong, Asia-Pacific
    In OneClickComply
    Supported today
    How we help

    OneClickComply makes it simple

    OneClickComply maps the six Data Protection Principles to practical controls for purpose limitation, retention, security and data subject requests, then collects evidence automatically from your connected systems. AutoComplete generates privacy policies and notices from your real environment, and continuous monitoring flags when security controls under DPP4 drift. Because controls are mapped once across frameworks, work you do for ISO 27001 or GDPR also counts towards PDPO.

    Requirements covered

    Six Data Protection Principles in Schedule 1, given force by section 4, plus operational duties across 10 Parts covering data access and correction (Part 5), direct marketing (Part 6A), enforcement (Part 7) and offences (Part 9).

    Already working towards another framework?

    Evidence you collect once counts towards every framework it applies to.

    Manual PDPO vs. OneClickComply

    Manual PDPO
    • Interpreting six principle-based DPPs into concrete controls with no checklist from the law
    • Chasing screenshots to prove that personal data is held securely
    • Tracking retention periods and erasure across scattered systems by hand
    • Managing data access and correction requests within the 40-day deadline using email and spreadsheets
    • Re-doing the same privacy and security work separately for PDPO, GDPR and ISO 27001
    With OneClickComply
    • Ready-mapped PDPO controls that turn each principle into clear tasks
    • Security evidence collected automatically from connected tools and logged
    • Retention and disposal controls monitored with alerts when they drift
    • Documented procedures and policies for handling data subject requests
    • Evidence collected once and reused across PDPO, GDPR and ISO 27001
    Capabilities

    Everything you need for PDPO

    Control set mapped to all six PDPO Data Protection Principles

    AutoComplete privacy policy and personal information collection statement drafts

    Automated evidence for DPP4 security controls from cloud and identity tools

    Retention and disposal tracking to support DPP2 and section 26

    Vendor risk management for data processors under DPP2(3) and DPP4(2)

    Ask an Auditor guidance on data access requests and direct marketing rules

    How it works

    Three steps to PDPO compliance

    01

    Connect & scan

    Connect your cloud, identity and SaaS tools. OneClickComply checks them against PDPO and shows you exactly where you stand.

    02

    Fix & generate

    OneClickFix remediates technical gaps in one click, and AutoComplete generates PDPO-aligned policies from your real environment.

    03

    Monitor & evidence

    Continuous monitoring keeps you compliant, and our in-house audit team is on hand when you need expert guidance.

    Requirements

    Hong Kong Personal Data (Privacy) Ordinance requirements

    The six Data Protection Principles followed by the key operative sections of the Ordinance that create duties, rights and offences for data users.

    ReferenceRequirement
    DPP1Purpose and manner of collection of personal data
    DPP2Accuracy and duration of retention of personal data
    DPP3Use of personal data
    DPP4Security of personal data
    DPP5Information to be generally available
    DPP6Access to personal data
    Section 4Data users must not contravene the data protection principles
    Section 12Approval of codes of practice by the Commissioner
    Section 14Data user returns
    Section 15Register of data users
    Section 18Data access request
    Section 19Compliance with data access request
    Section 22Data correction request
    Section 23Compliance with data correction request
    Section 26Erasure of personal data no longer required
    Section 27Log book to be kept by data user
    Section 30Matching procedure not to be carried out without consent
    Section 33Transfer of personal data outside Hong Kong (not yet in operation)
    Section 35CSpecified action before using personal data in direct marketing
    Section 35ENo use of personal data in direct marketing without consent

    Always check the official PDPO text for the exact wording.

    PDPO FAQs

    What is the Hong Kong PDPO?

    The PDPO is the Personal Data (Privacy) Ordinance (Cap. 486), Hong Kong's main data protection law. It was enacted in 1995 and came into force on 20 December 1996. It requires data users to comply with six Data Protection Principles covering collection, accuracy and retention, use, security, openness and data access. The Privacy Commissioner for Personal Data (PCPD) oversees it and can investigate complaints and issue enforcement notices.

    Who must comply with the PDPO?

    Every data user must comply with the PDPO. A data user is any person or organisation, public or private, that alone or with others controls the collection, holding, processing or use of personal data. There is no size threshold or sector exemption, so small businesses, charities and government bodies are all covered. Overseas organisations can also be caught when they control personal data in or from Hong Kong.

    What are the six Data Protection Principles?

    The six Data Protection Principles in Schedule 1 of the PDPO are: DPP1 purpose and manner of collection; DPP2 accuracy and duration of retention; DPP3 use of personal data; DPP4 security of personal data; DPP5 information to be generally available; and DPP6 access to personal data. Section 4 requires data users not to contravene them. Together they set the core rules for handling personal data in Hong Kong.

    What are the penalties for breaching the PDPO?

    Breaching a Data Protection Principle is not itself a crime, but the PCPD can issue an enforcement notice. Contravening an enforcement notice is an offence, with a fine at level 5 and two years' imprisonment on first conviction, plus daily penalties. Direct marketing and unauthorised disclosure offences carry fines of up to HK$1,000,000 and up to five years' imprisonment. Individuals can also claim compensation under section 66.

    Does the PDPO require data breach notification?

    No, the PDPO does not currently impose a mandatory data breach notification duty. The PCPD encourages data users to notify it and affected individuals voluntarily, and provides a breach notification form. Organisations should still have an incident response process, because a breach usually indicates a possible contravention of DPP4 on security, which the PCPD can investigate and act on through an enforcement notice.

    How does the PDPO compare with GDPR?

    The PDPO and GDPR share similar ideas, such as purpose limitation, accuracy, security and individuals' rights of access and correction. The PDPO is narrower: it has no general administrative fines, no mandatory breach notification and no statutory data protection officer role, and its cross-border transfer restriction in section 33 is not yet in operation. Controls built for GDPR usually cover most PDPO requirements.

    How do you comply with the PDPO?

    You comply with the PDPO by building a privacy programme around the six Data Protection Principles. In practice that means mapping the personal data you hold, giving collection notices, limiting use to the original purpose, setting retention and erasure rules, securing data and processors, publishing a privacy policy and handling access and correction requests within 40 days. Direct marketing needs specific notice and consent under Part 6A.

    Does OneClickComply support the PDPO?

    Yes. OneClickComply supports the Hong Kong PDPO today. The platform maps the six Data Protection Principles to practical controls, collects evidence automatically from connected tools, generates privacy policies with AutoComplete and monitors security controls continuously. Our in-house audit team can answer PDPO questions through Ask an Auditor. OneClickComply helps you build and evidence your programme, but compliance remains your organisation's responsibility.

    Get PDPO ready, not stressed

    Automate controls, gather evidence continuously and stay audit-ready, all on one platform.