Meet Singapore PDPA obligations with evidence you can show
The PDPA (Personal Data Protection Act 2012) is Singapore's main data protection law, governing how private sector organisations collect, use, disclose and care for personal data. It is administered and enforced by the Personal Data Protection Commission (PDPC).
- Issued by
- Parliament of Singapore; administered by the Personal Data Protection Commission (PDPC)
- In force since
- Data protection provisions from 2 July 2014; Do Not Call provisions from 2 January 2014
- Latest major amendment
- Personal Data Protection (Amendment) Act 2020, in force in phases from 1 February 2021
- Applies to
- Private sector organisations handling personal data in Singapore, including overseas organisations
Is PDPA right for your organisation?
The Act also creates the Do Not Call Registry, which restricts marketing messages to Singapore telephone numbers.
Any organisation that collects, uses or discloses personal data in Singapore must comply, whether or not it is based or registered there. Data intermediaries processing personal data for another organisation must meet the protection, retention and breach notification duties. Public agencies are excluded, as are individuals acting in a personal or domestic capacity.
How OneClickComply helps with PDPA
OneClickComply supports the Singapore PDPA today, so your existing security and privacy controls can be reused against PDPA obligations rather than rebuilt. OneClickComply collects evidence for the Protection Obligation from your connected tools, generates data protection policies from your real environment and keeps a vendor register for data intermediaries and overseas transfers. Our in-house auditors can advise on how your controls line up with each obligation.
Requirements covered
The Act's core data protection obligations sit in Parts 3 to 6A (sections 11 to 26E), with Do Not Call rules in Part 9 and offences, enforcement and financial penalties in Parts 9B and 9C.
Manual PDPA compliance vs OneClickComply
Doing it manually
- Interpreting ten separate obligations and the deemed consent rules without clear owners
- Writing data protection policies from scratch and keeping them in step with practice
- Proving reasonable security arrangements with screenshots gathered by hand
- Tracking which vendors process personal data and where it is transferred
- Working out under pressure whether a breach is notifiable within the deadline
With OneClickComply
- Each PDPA obligation mapped to controls with clear owners and status
- Policies generated from your real environment and kept current
- Security evidence collected automatically from your connected tools
- One vendor register showing data intermediaries and transfer risk
- An incident response policy and evidence trail ready before a breach happens
Everything you need for PDPA
PDPA obligations mapped to controls you already run for other frameworks
Automated evidence for reasonable security arrangements under the Protection Obligation
AutoComplete policies covering data protection, retention and breach response
Vendor risk management for data intermediaries and overseas transfers
Continuous monitoring with alerts when security controls drift
Ask an Auditor guidance on applying PDPA obligations to your organisation
Three steps to PDPA compliance
Connect and scan
Connect your cloud, identity and SaaS tools. OneClickComply checks them against PDPA and shows which controls pass and which fail.
Fix and generate
OneClickFix fixes supported misconfigurations automatically, and AutoComplete drafts PDPA policies from your real environment.
Monitor and evidence
Continuous monitoring flags drift as it happens, and our in-house audit team is on hand when you need expert guidance.
See how far your current setup is from PDPA.
Singapore Personal Data Protection Act (PDPA) requirements
The PDPA's substantive obligations by section: data protection duties in Parts 3 to 6A, Do Not Call rules in Part 9, and the key offence and enforcement provisions; administrative and interpretation sections are omitted.
| Reference | Requirement |
|---|---|
| Section 11 | Compliance with Act (designating a data protection officer) |
| Section 12 | Policies and practices |
| Section 13 | Consent required |
| Section 14 | Provision of consent |
| Section 15 | Deemed consent |
| Section 15A | Deemed consent by notification |
| Section 16 | Withdrawal of consent |
| Section 17 | Collection, use and disclosure without consent |
| Section 18 | Limitation of purpose and extent |
| Section 19 | Personal data collected before 2 July 2014 |
| Section 20 | Notification of purpose |
| Section 21 | Access to personal data |
| Section 22 | Correction of personal data |
| Section 22A | Preservation of copies of personal data |
| Section 23 | Accuracy of personal data |
| Section 24 | Protection of personal data |
| Section 25 | Retention of personal data |
| Section 26 | Transfer of personal data outside Singapore |
| Section 26B | Notifiable data breaches |
| Section 26C | Duty to conduct assessment of data breach |
Always check the official text of PDPA for the exact wording.
PDPA questions, answered
Can't find what you need? Our in-house auditors can talk you through PDPA on a 30-minute call.
What is the Singapore PDPA?
The PDPA is the Personal Data Protection Act 2012, Singapore's general data protection law for the private sector. It sets rules on how organisations collect, use, disclose, protect, retain and transfer personal data, gives individuals rights to access and correct their data, and requires notification of serious data breaches. It also establishes the Do Not Call Registry for marketing messages sent to Singapore telephone numbers. The Personal Data Protection Commission (PDPC) administers and enforces the Act.
Who must comply with the PDPA?
Any organisation that collects, uses or discloses personal data in Singapore must comply with the PDPA, including organisations with no office or place of business in Singapore. Data intermediaries processing personal data on behalf of another organisation under a written contract must still meet the protection, retention and breach notification duties. Public agencies, and individuals acting in a personal or domestic capacity, are excluded from the data protection obligations.
What are the main PDPA obligations?
The PDPC groups the PDPA into ten data protection obligations: accountability, notification, consent, purpose limitation, accuracy, protection, retention limitation, transfer limitation, access and correction, and data breach notification. A data portability obligation has also been passed into law but is not yet in force. Accountability includes designating at least one person, often called a data protection officer, and making their business contact information publicly available.
What are the penalties for breaching the PDPA?
The PDPC can impose a financial penalty of up to S$1 million, or up to 10% of annual turnover in Singapore for organisations whose Singapore turnover exceeds S$10 million, whichever applies. The higher cap took effect on 1 October 2022. The PDPC can also issue directions to stop collecting data or destroy it, and individuals who suffer loss can bring a private action. Some conduct, such as reckless unauthorised disclosure by individuals, is a criminal offence.
When must a data breach be reported under the PDPA?
A data breach must be reported to the PDPC no later than 3 calendar days after an organisation assesses it as notifiable. A breach is notifiable if it causes, or is likely to cause, significant harm to affected individuals, or affects 500 or more individuals. Organisations must assess a suspected breach expeditiously, and where significant harm is likely they must also notify the affected individuals, subject to limited exceptions.
How does the PDPA compare with GDPR?
The PDPA and GDPR share core ideas such as purpose limitation, security, access rights and breach notification, but they are not interchangeable. The PDPA relies mainly on consent and deemed consent with defined exceptions, and has no direct equivalent of GDPR's lawful bases. Its breach notification window and penalty caps also differ. GDPR compliance work gives a strong head start, but Singapore-specific obligations such as the Do Not Call rules still need separate attention.
Does ISO 27001 help with PDPA compliance?
Yes, ISO 27001 helps mainly with the PDPA Protection Obligation, which requires reasonable security arrangements to prevent unauthorised access, use, disclosure and similar risks. An ISO 27001 information security management system gives documented, tested security controls and evidence. It does not cover consent, notification, access and correction, retention or Do Not Call obligations, so those still need their own privacy policies and processes.
Does OneClickComply support the Singapore PDPA?
Yes. OneClickComply supports the Singapore PDPA today. Controls you already operate for frameworks such as ISO 27001 or GDPR can be reused against PDPA obligations, with automated evidence collection, policy generation and vendor risk management. OneClickComply does not certify PDPA compliance, as the PDPA has no certification scheme, but our auditors can advise on gaps.
Related frameworks
- Japan Act on the Protection of Personal Information (APPI)Law · Japan
- New Zealand Privacy Act 2020Law · New Zealand
- China Personal Information Protection Law (PIPL)Law · China
- India Digital Personal Data Protection Act 2023Law · India
- China Cybersecurity LawLaw · China
- South Korea Personal Information Protection Act (PIPA)Law · South Korea
- Philippines Data Privacy Act of 2012Law · Philippines
- Hong Kong Personal Data (Privacy) OrdinanceLaw · Hong Kong
Start working towards PDPA
Automate controls, gather evidence continuously and stay audit-ready, all on one platform.