Artifact GuideSingaporePDPA breach thresholds

Singapore PDPA Breach Notification Thresholds

Notify the PDPC when a Singapore PDPA data breach results in, or is likely to result in, to affected individuals, or is of . Significant scale is 500 or more affected individuals.

The significant-harm route can require notice to both the PDPC and affected individuals, while alone requires PDPC notice. Document the tests and notification decisions separately.

Author
Sorena AI
Published
May 9, 2026
Updated
Jul 24, 2026
Overview

This page is relevant when an incident response team needs to decide whether a Singapore PDPA personal data breach is notifiable to the Personal Data Protection Commission, affected individuals, or both. The key tests are and , supported by documented assessment steps and timing evidence.

Section 1

What are the Singapore PDPA breach notification thresholds?

The Singapore PDPA breach notification threshold is not a single headcount rule. A breach can be notifiable because it is likely to result in to affected individuals, or because it is of .

is the clearer numeric threshold: the Personal Data Protection (Notification of Data Breaches) Regulations 2021 prescribe 500 affected individuals. PDPC guidance states that an organisation should notify the Commission when it has reason to believe the affected count is at least 500, even if the actual count is still being established.

The 500-individual test does not supersede the test. A smaller breach can still be notifiable if it results in, or is likely to result in, significant harm. Conversely, a breach affecting at least 500 individuals must be notified to the PDPC even when affected-individual notification is not required on the harm facts.

  • Use to decide whether the Commission and, subject to the statutory exceptions, affected individuals must be notified.
  • Use to decide whether the Commission must be notified when 500 or more individuals are affected; scale alone does not trigger affected-individual notice.
  • Do not close a breach as non-notifiable only because the affected count is below 500; check the data classes and harm analysis first.
  • When the count is uncertain, document the estimate, the source of the estimate, and why it is or is not reasonable to believe the count reaches 500.
Section 2

How should teams assess significant harm?

Start with the data involved, not the incident label. The Regulations deem where the breach involves an individual's full name, alias, or identification number together with classes in the Schedule, subject to the Schedule's limits. For this rule, identification number includes an identity card number, passport number, another government-issued identity document number used as evidence of nationality or residence, and a foreign identification number.

The Regulations also deem where the breach involves all required account-access elements: an account identifier, such as an account name or number, and a password, security code, access code, response to a security question, biometric data, or other data required to access or use the account.

PDPC guidance describes broadly, including physical, psychological, emotional, economic, financial, reputational, and other harms that a reasonable person would identify as possible outcomes of the breach.

  • Record each personal data class affected and whether it maps to a prescribed significant-harm category.
  • Check whether account identifiers were exposed together with credentials, security responses, biometric access data, or equivalent account-access data.
  • Apply the combinations precisely: a name, alias, or identification number must be paired with a prescribed Schedule data class under regulation 3(1)(a), while the account route requires both an account identifier and the data needed to access or use that account under regulation 3(1)(b).
  • Assess likely harm in concrete terms: identity misuse, financial loss, account takeover, reputational damage, physical safety risk, or harm to vulnerable individuals.
  • If the prescribed category analysis is incomplete, keep the breach open for escalation rather than treating it as non-notifiable.
Section 3

What assessment record should prove the threshold decision?

PDPC guidance expects organisations with credible grounds to believe a breach occurred to take reasonable and expeditious steps to assess whether it is notifiable, generally within 30 calendar days. The organisation must document all steps taken in the assessment.

The assessment record should be complete enough to support the final notification or non-notification decision. For a notifiable breach, the Regulations require a chronological account of steps taken after awareness of the breach, including the organisation's assessment that the breach is notifiable.

If a data intermediary has credible grounds to believe a breach occurred while processing personal data for another organisation or public agency, it must notify that organisation or public agency without undue delay. The engaging organisation conducts the notifiability assessment and keeps the threshold decision record.

  • Capture the date and circumstances when the organisation first became aware of the breach.
  • Record the affected systems, affected individuals or estimate, personal data classes, and whether the breach meets or .
  • Document containment, remediation, mitigation of harm, and the reasoning for notifying or not notifying affected individuals.
  • Keep evidence explaining any assessment that takes longer than 30 calendar days and any Commission notification made after the three-calendar-day notification period.
Section 4

When does the notification clock start?

The Commission notification clock starts after the organisation determines that the breach is notifiable. PDPC guidance states that the Commission must be notified as soon as practicable and no later than three calendar days after that determination.

The first day of the three-day period starts on the day after the organisation makes the notifiable-breach determination. PDPC's example says a breach determined notifiable on 1 January must be notified to the Commission by 4 January.

Affected individuals, where notification is required, must be notified as soon as practicable, at the same time as or after notifying the Commission. PDPC also says that breaches likely to attract widespread public attention or interest should be notified to the Commission before affected individuals or public/media statements.

  • Record the timestamp for credible grounds to believe a breach occurred, the assessment start, the notifiable-breach determination, and each notification sent.
  • Notify the Commission within three calendar days after the notifiable-breach determination, not three days after initial discovery.
  • Sequence affected-individual notices at the same time as or after Commission notification when affected-individual notification is required.
  • If Commission notification is late, include the reasons for late notification and supporting evidence.
Primary sources

References and citations

pdpc.gov.sg5 citations
Referenced sections
  • PDPC guidance source for the breach assessment process, 30-calendar-day assessment expectation, notification timing, and practical notification records.
  • PDPC guidance explains that significant-scale breaches require Commission notification even without prescribed significant-harm data.
  • PDPC guidance describes the kinds of harm teams should consider when assessing a breach.
Show 2 more
  • PDPC guidance supports the 30-calendar-day assessment expectation and the need to document assessment steps.
  • PDPC guidance supports the three-calendar-day Commission notification clock and explains when the first day begins.
"must document all steps taken in assessing the data breach"
More quoted passages
"even if the data breach does not involve any prescribed personal data"
"physical, psychological, emotional, economic and financial harm"
"starts on the day after the organisation makes the determination"
sso.agc.gov.sg4 citations
Referenced sections
  • Primary Singapore legislation source for the significant-harm data breach trigger, the 500-individual significant-scale threshold, and required notification contents.
  • Regulations 3 and 4 define the prescribed significant-harm trigger and set significant scale at 500 affected individuals.
  • Regulation 3 identifies the prescribed data combinations that are deemed to result in significant harm.
Show 1 more
  • Regulation 5 lists the information required in a Commission notification, including the assessment and chronology.
"the prescribed number of affected individuals is 500"
More quoted passages
"deemed to result in significant harm to an individual"
"a chronological account of the steps taken"
pdpc.gov.sg3 citations
Referenced sections
  • PDPC self-assessment source for determining whether an incident is notifiable before reporting.
  • PDPC's self-assessment page states that organisations do not need to report every breach, but should first assess whether the incident is notifiable.
  • PDPC's self-assessment page supports using a structured assessment before deciding whether to report a breach.
"assess whether the data breach is notifiable under the PDPA"
More quoted passages
"Organisations do not need to report every breach"
"assist with the determination of whether a data breach incident is notifiable"
pdpc.gov.sg2 citations
Referenced sections
  • PDPC web source for sequencing affected-individual notifications with PDPC notification.
  • PDPC's affected-individual guidance supports sequencing notices to individuals at the same time as or after PDPC notification.
"at the same time or after notifying the PDPC"
pdpc.gov.sg2 citations
Referenced sections
  • PDPC web source confirming the three-calendar-day notification deadline after a breach is notifiable.
  • PDPC's reporting page confirms notification to the PDPC should be as soon as practicable and no later than three calendar days.
"no later than three (3) calendar days"
Show all related guides (37)

Singapore PDPA Consent and Deemed Consent Workflow

Choose express consent, deemed consent by conduct, contractual necessity, notification, or the legitimate interests exception under Singapore PDPA with fact-based intake fields and evidence records.

Singapore PDPA Consent, Notification and Purpose Rules

How Singapore PDPA consent, notification, purpose limitation, deemed consent, withdrawal, and consent exceptions should be handled in product and privacy workflows.

Singapore PDPA Cross-Border Transfers

Source-cited Singapore PDPA guidance for overseas personal data transfers, comparable protection, ASEAN MCCs, APEC certifications, vendor roles, and evidence records.

Singapore PDPA Data Intermediary Responsibilities

Practical Singapore PDPA guide to data intermediary role boundaries, organisation accountability, protection, retention, breach escalation, and contract evidence.

Singapore PDPA Deadlines and Compliance Calendar

A Singapore PDPA compliance calendar for breach notification, DNC checks, access and correction requests, enforcement responses, retention reviews, and DPMP maintenance.

Singapore PDPA Deemed Consent and Legitimate Interests

How to apply Singapore PDPA deemed consent by conduct, contractual necessity, notification, and legitimate interests with opt-out, adverse-effect, disclosure, and assessment records.

Singapore PDPA DNC and Marketing Messages Guide

A source-cited Singapore PDPA guide to DNC checks, specified marketing messages, Singapore telephone numbers, consent evidence, opt-outs, sender duties, and excluded messages.

Singapore PDPA DNC Marketing Checks

Operational checklist for Singapore PDPA DNC marketing checks: account evidence, register status, 21-day result validity, consent evidence, and campaign owner records.

Singapore PDPA DNC Marketing Workflow

Workflow for Singapore PDPA DNC marketing campaigns: classify specified messages, check Singapore telephone numbers, document consent, suppress opt-outs, and approve sends.

Singapore PDPA DPMP Accountability Guide

Build a Singapore PDPA Data Protection Management Programme with DPO ownership, policies, data inventories, DPIAs, training, monitoring, breach logs, and review records.

Singapore PDPA FAQ: scope, DPO, consent, breaches and DNC

FAQ answers for Singapore PDPA implementation, covering scope, accountability, consent, access and correction, security, retention, transfers, data intermediaries, breach notification, and DNC checks.

Singapore PDPA NRIC Handling Rules

When Singapore organisations may collect, use, disclose, retain, mask, or replace NRIC numbers, including the 31 December 2026 authentication deadline.

Singapore PDPA Penalties and Enforcement Cases

How PDPC enforcement under Singapore's PDPA works: directions, voluntary undertakings, published decisions, financial penalty caps, and implementation lessons from cases.

Singapore PDPA Penalties and Fines

Singapore PDPA penalty ceilings, PDPC directions, undertakings, breach notification context, and practical controls based on official PDPC and Singapore Statutes sources.

Singapore PDPA Privacy Policy Template

A Singapore PDPA privacy policy template for writing notices, DPO contact details, access and correction routes, retention, transfers, protection, withdrawal, and complaint handling without overclaiming compliance.

Singapore PDPA Requirements: Core Obligations

Map Singapore PDPA obligations across consent, notification, access, security, retention, transfers, accountability, breaches, DNC checks, and data intermediaries.

Singapore PDPA Scope, Exclusions, and Data Intermediaries

Classify Singapore PDPA coverage, business contact information, personal or domestic activity, employee acts, and data intermediary obligations using cited statutory boundaries and processing records.

Singapore PDPA Transfer Assessment Workflow

A Singapore PDPA workflow for assessing overseas personal data transfers, comparable protection, ASEAN MCCs, APEC CBPR/PRP certifications, vendor due diligence, onward transfers, and evidence records.

Singapore PDPA Transfer Clauses

Draft Singapore PDPA transfer clauses for overseas vendors, affiliates, data intermediaries, onward transfers, ASEAN MCCs, and APEC or Global CBPR and PRP evidence.

Singapore PDPA Vendor Outsourcing and Contracts

Contract and operating checklist for Singapore PDPA vendor outsourcing: data intermediary status, written terms, security, retention, breach, transfers, sub-contracting, and exit evidence.

Singapore PDPA vs GDPR Comparison

Compare Singapore PDPA and EU GDPR rules for legal bases, DPOs, intermediaries and processors, transfers, breaches, marketing objections, rights, retention, and penalties.

Singapore PDPA anonymisation FAQ

FAQ on anonymisation under the Singapore PDPA: de-identification, pseudonymisation, re-identification risk, when PDPA may no longer apply, and evidence records.

Singapore PDPA breach notification thresholds FAQ

FAQ on Singapore PDPA notifiable data breach tests: significant harm, significant scale, 500 affected individuals, assessment timing, PDPC notices, and affected-individual notices.

Singapore PDPA Data Intermediaries FAQ

FAQ guidance on Singapore PDPA data intermediary roles, direct obligations, organisation accountability, contracts, retention, protection, and breach escalation.

Singapore PDPA Deemed Consent FAQ

FAQ on Singapore PDPA deemed consent by conduct, contractual necessity, notification, opt-out periods, adverse-effect assessment, withdrawal, and direct-marketing limits.

Singapore PDPA DNC checking FAQ: when to check the DNC Registry

FAQ guidance on Singapore PDPA DNC checking: when to check the DNC Registry, which registers apply, 8-digit numbers, 21-day result validity, consent evidence, on-behalf checks, opt-outs, and supported exclusions.

Singapore PDPA DPIAs: when to run and what to document

FAQ-style implementation guidance on Singapore PDPA DPIAs, including when PDPC guidance recommends them, data-flow mapping, risk treatment, DPO review, and evidence records.

Singapore PDPA DPMP Accountability FAQ | DPO, Policies, Evidence

FAQ for implementing Singapore PDPA accountability through a DPMP: DPO designation, policies, evidence, training, monitoring, incident logs, and review records.

Singapore PDPA legitimate interests FAQ

FAQ guidance on Singapore PDPA legitimate interests: assessment fields, adverse effects, mitigation, balancing, disclosure, records, and marketing limits.

Singapore PDPA NRIC Handling FAQ

FAQ guidance on when Singapore organisations may collect, use, disclose, retain, mask, or replace NRIC and other national identification numbers under PDPC guidance.

Singapore PDPA transfer clauses FAQ

FAQ guidance on Singapore PDPA transfer clauses, comparable protection, ASEAN MCCs, APEC CBPR and PRP certifications, onward transfers, and evidence records.