- Lists past decisions used by PDPC to illustrate aggravating and mitigating factors in financial penalty calibration.
"Past enforcement cases"
PDPC enforcement is not only about fines. A case may end with no breach, a warning, directions, a financial penalty, directions plus a penalty, suspension or discontinuation, or a voluntary undertaking.
Use this page to brief product, privacy, security, and leadership teams on what PDPC can require, what evidence matters, and how published cases should feed back into controls.
Structured answer sets in this page tree.
Cited legal and guidance references.
This guide explains the enforcement outcomes available to Singapore's Personal Data Protection Commission under the PDPA and turns the official enforcement guidance into practical remediation, evidence, and governance lessons for organisations handling personal data.
The PDPC's Active Enforcement Framework starts with the facts of the incident and the likely impact on affected individuals. Low-impact matters may be resolved through facilitation, mediation, suspension or discontinuation of the investigation, sometimes with an advisory notice that identifies improvements without making a breach finding.
Where PDPC takes a matter through investigation and determines a breach, the possible outcomes include a warning, directions, a financial penalty, or both directions and a financial penalty. For high-impact incidents, the guide says PDPC may launch a full investigation early, especially where many individuals are affected or the personal data could cause significant harm.
Implementation lesson: do not treat every incident as a fine scenario. Build an enforcement intake that separates impact, data sensitivity, affected population, remedial action, cooperation, repeat issues, and whether the matter is suitable for facilitation, undertaking, expedited decision, or full investigation.
Directions are remedial orders. The enforcement guidelines describe section 48I directions as measures PDPC may issue to secure compliance, including stopping non-compliant collection, use, or disclosure, destroying personal data collected in contravention of the PDPA, complying with review directions, preventing or reducing harm, and rectifying processes.
Voluntary undertakings are different. PDPC may accept a written undertaking where an organisation is ready to implement an effective remediation plan. The Active Enforcement guide says a voluntary undertaking does not amount to an admission of breach, but PDPC is unlikely to accept one where the organisation refutes responsibility, repeats a similar breach cause, lacks a credible remediation plan, asks for more time to prepare one, or the breach is wilful or egregious.
Published decisions and summaries are operational learning material. PDPC generally publishes decisions where an organisation is found to have contravened the PDPA so other organisations can see how the law was applied and take preventive measures.
For intentional or negligent contraventions of the PDPA Data Protection Provisions, the enforcement guidelines state that PDPC may require an organisation to pay a financial penalty of up to S$1 million or 10% of the organisation's annual turnover in Singapore, whichever is higher where annual turnover in Singapore exceeds S$10 million.
For intentional or negligent contraventions of DNC provisions involving dictionary attacks and address-harvesting software, the guidelines state a cap of up to S$200,000 for an individual and, for an organisation, up to S$1 million or 5% of annual turnover in Singapore, whichever is higher where annual turnover in Singapore exceeds S$20 million. Other DNC contraventions are described separately: up to S$200,000 for an individual and up to S$1 million in other cases.
Penalty calibration is not a flat schedule. PDPC assesses harm and culpability, then considers factors such as mitigation, previous PDPA failures, voluntary admission of liability, cooperation during investigation, first-time offender status, proportionality, deterrence, and likely impact on the organisation.
PDPC's decisions page explains that published decisions provide insights and lessons so organisations can prevent similar occurrences. The enforcement guidelines also list past cases used to illustrate penalty factors, including examples involving duration of non-compliance, sensitive personal data, profiteering from sale of personal data, prompt mitigation, previous similar incidents, and the proportionality of penalties.
A useful case review should not stop at the organisation name or penalty amount. It should identify the breached obligation, failure mode, affected data, harm and culpability factors, directions or remediation required, penalty factors if any, and the internal control that prevents recurrence.
Turn each relevant case into an implementation record that engineering, security, marketing, HR, legal, privacy, and vendor-management teams can act on. For example, a case about exposed tracking pages belongs in access-control and testing evidence; a case about repeated mailing errors belongs in operational training, vendor oversight, and exception monitoring.
Use this Singapore PDPA enforcement guide to convert PDPC directions, undertakings, penalty factors, and published case lessons into assigned remediation records inside Sorena.
Turn enforcement lessons into scoped controls, owners, evidence fields, and remediation tasks.
Use Research Copilot to compare internal controls against PDPC enforcement guidance and published cases.
Review PDPA enforcement exposure, evidence gaps, and practical remediation actions with Sorena.
"Past enforcement cases"
"Enforcement Cases"
"Types of Enforcement Outcomes"
"Undertakings"
"48J Financial penalties"