Singapore PDPA and Mandatory Breach Notification
Singapore's Personal Data Protection Act 2012, significantly amended in 2020 with mandatory breach notification, deemed consent, and enhanced penalties.
Singapore's Personal Data Protection Act 2012 (PDPA), administered by the Personal Data Protection Commission (PDPC), underwent comprehensive amendments in 2020 through the Personal Data Protection (Amendment) Act 2020, effective February 1, 2021. The amendments introduced mandatory data breach notification (MDBN), a new deemed and deemed-legitimate-interest consent framework, increased financial penalties up to SGD 1 million or 10% of annual turnover (whichever is higher), and new data portability obligations. The PDPA applies to organizations collecting, using, or disclosing personal data in Singapore, with a domestic exception for individuals acting in a personal or domestic capacity. The PDPC's Advisory Guidelines and Enforcement Decisions provide binding interpretive guidance alongside the statute.
The mandatory breach notification regime (PDPA Part VIA) requires organizations to assess breaches within 3 calendar days of discovery, notify the PDPC within 3 calendar days of assessing that the breach is notifiable, and notify affected individuals where the breach is likely to result in significant harm — defined as including financial loss, identity theft, bodily harm, humiliation, and damage to relationships or reputation (Second Schedule). Critically, a breach is "notifiable" if it affects 500 or more individuals, or if it involves data likely to cause significant harm regardless of scale. This 3-day PDPC notification window is shorter than GDPR's 72 hours only superficially — the 3-day assessment window precedes the 3-day notification window, giving a potential 6-day maximum before PDPC notification, though organizations should aim for 72 hours total.
The PDPA's 2020 amendments introduced "deemed consent by notification" and "deemed consent by contractual necessity" — new consent pathways that allow organizations to process personal data without explicit consent in defined circumstances, provided individuals are notified and given a reasonable opt-out window. Technically, this requires organizations to implement notification mechanisms, opt-out handling within the prescribed period, and documentation that the deemed consent pathway was properly invoked. Data portability obligations (Part VA) — effective February 2021 for select sectors — require organizations in the banking, insurance, and telecom sectors to transmit customer data directly to designated recipient organizations upon request in a commonly used machine-readable format. Port-to-port transfer APIs must meet PDPC's data portability technical standards.
We implement PDPA breach response playbooks with automated breach severity scoring that triggers the 3+3-day PDPC and individual notification workflow, including pre-populated notification templates aligned to the Second Schedule harm categories. Our data portability pipelines are built to PDPC technical standards for banking and telecom sectors, with machine-readable export formats and secure direct-transfer API endpoints.
Compliance-Native Architecture Guide
Design principles and a structured checklist for building software that is compliant by default — not compliant by retrofit. Covers data architecture, access controls, audit trails, and vendor due diligence.