FAQSingapore PDPABreach notification

Singapore PDPA Breach thresholds

A Singapore PDPA data breach is notifiable when it is likely to result in to or affects a of individuals.

This FAQ helps apply the PDPC assessment clock, the 500-individual significant-scale threshold, PDPC notice timing, affected-individual notice timing, and evidence records supported by official sources.

Author
Sorena AI
Published
May 9, 2026
Updated
Oct 15, 2026
Overview

This FAQ explains how implementation teams should assess Singapore PDPA breach notification thresholds after a personal data breach. It distinguishes prescribed significant-harm circumstances from the 500-individual significant-scale route, the PDPC-guidance assessment window from the post-determination notification clock, and PDPC notification from affected-individual notification.

Search this module

Find a question or answer quickly

6 of 6 questions
Question 1

When is a Singapore PDPA data breach notifiable?

A Singapore PDPA data breach is notifiable if either threshold is met: the breach is likely to result in to , or it affects a of individuals. PDPC guidance states that organisations do not need to report every breach, but they must assess whether the breach is notifiable.

In implementation terms, start every incident record with four facts: what personal data was affected, how the breach occurred, how many individuals are affected or likely affected, and whether the data type or circumstances create likely .

  • Treat and as separate tests; either one can make the breach notifiable to the PDPC.
  • Do not wait for a final root-cause report before starting the notifiability assessment once credible grounds exist.
  • If the answer is uncertain, PDPC's self-assessment guidance encourages organisations to err on the side of caution.
Question 2

What counts as significant harm under Singapore PDPA breach notification rules?

The Notification of Data Breaches Regulations deem a breach to result in when it involves specified combinations of personal data. The core statutory examples are a full name, alias, or identification number together with prescribed personal data in the Schedule, or account access data such as an account identifier together with a password, security code, access code, security-question response, biometric data, or other account-access credential.

For a working incident triage, classify the affected fields before deciding the notice path. If account access credentials or prescribed identity-linked data are involved, escalate the incident as a likely significant-harm case unless counsel or the DPO documents a supported reason otherwise.

  • Record whether the incident involves full name, alias, identification number, account identifier, password, security code, access code, security-question response, biometric data, or comparable account-access data.
  • Separate the data-type analysis from the number-of-individuals analysis so a small breach involving high-risk data is not missed.
  • Use the affected-individual notice draft to identify concrete harms and protective steps such as password changes, card cancellation, account monitoring, or misuse prevention.
Question 3

What counts as significant scale, and why does the 500-person threshold matter?

A data breach is of when it involves the personal data of 500 or more . PDPC guidance says the organisation must notify the Commission when a breach affects 500 or more individuals even if the breach does not involve prescribed personal data that would otherwise trigger the significant-harm test.

If the exact count is unknown, use a reasonable initial estimate. PDPC guidance says organisations should notify the Commission when they have reason to believe the affected number is at least 500 and may later update the Commission with the actual number.

  • Use 500 as the operational escalation threshold for .
  • Count people, not records, rows, accounts, or files; preserve the method used to estimate the affected population.
  • Do not treat the absence of prescribed high-risk data as the end of the assessment when the affected population may be 500 or more.
Question 4

How quickly must the organisation assess and notify the PDPC?

Once the organisation has credible grounds to believe a data breach occurred, it must take reasonable and expeditious steps to assess whether the breach is notifiable. PDPC guidance expects that assessment within 30 calendar days. If the assessment cannot be completed within 30 days, the organisation should be ready to explain the time taken or required.

After the organisation determines that the breach is notifiable, it must notify the PDPC as soon as practicable and no later than three calendar days. PDPC guidance states that the three-day period starts on the day after the determination that the breach is notifiable.

  • Open the 30-calendar-day assessment tracker from the point credible grounds exist, including discovery by monitoring, public alert, or data intermediary notification.
  • Open the three-calendar-day PDPC notification tracker from the notifiability determination, not from the first incident alert.
  • If PDPC notification is late, keep the reasons and supporting evidence because the Regulations require those details in the notice.
Question 5

When must affected individuals be notified?

Notification to the PDPC and notification to are separate decisions. A breach that is notifiable only because it affects 500 or more individuals must be reported to the PDPC, but that scale threshold alone does not trigger individual notification. Notify affected individuals when the breach is likely to result in , unless a statutory exception, prohibition, waiver, or other written law changes that result.

PDPC guidance says organisations must notify as soon as practicable, at the same time as or after notifying the PDPC. For breaches likely to attract widespread public attention or interest, the guidance strongly encourages organisations to notify and seek advice from the PDPC first; it does not state a separate universal legal rule that every public statement must wait for PDPC approval.

The affected-individual notice should be practical rather than merely formal. The Regulations require information about how the organisation became aware of the breach, the affected personal data, potential harm, actions taken or planned, steps the individual may take to reduce harm, and business contact information for an authorised representative.

  • Record whether individual notification is triggered by likely ; do not infer it from the 500-individual significant-scale route alone.
  • Prepare affected-individual notices in parallel with PDPC notification, but send them at the same time as or after notifying the PDPC.
  • For a breach likely to attract widespread public attention or interest, follow PDPC's strong recommendation to notify and seek its advice before notifying individuals or making a public statement.
  • Make the notice clear enough for the individual to act: what happened, what data was affected, what harm is possible, what the organisation is doing, and what the individual should do.
Question 6

What evidence records should support a Singapore PDPA breach-threshold decision?

Keep evidence that proves the assessment was timely, cited, and based on the data actually affected. PDPC guidance says organisations must document all steps taken in assessing whether a breach is notifiable, and the Regulations require the PDPC notice to include a chronological account of steps taken after awareness of the breach.

The minimum useful record is an incident chronology, data-field inventory, affected-individual count or estimate, significant-harm analysis, significant-scale analysis, notifiability determination time, PDPC notification time, affected-individual notification plan, mitigation actions, and any late-notification explanation with supporting evidence.

  • Preserve the moment credible grounds existed, the assessment start time, and the notifiability determination time.
  • Keep the affected data categories and count methodology with links to logs, exports, vendor notices, or forensic findings used in the assessment.
  • Record the grounds for not notifying when the organisation decides not to do so despite a notifiable breach that would otherwise involve affected-individual notification.
Primary sources

References and citations

pdpc.gov.sg5 citations
Referenced sections
  • Primary PDPC implementation guide for assessment timing, significant-harm and significant-scale criteria, PDPC notification timing, affected-individual notification timing, and evidence records.
  • Explains that prescribed personal data in the DBN Regulations makes affected-individual and PDPC notification required.
  • Explains that 500 or more affected individuals requires Commission notification even without prescribed personal data.
Show 2 more
  • Supports the 30-calendar-day assessment expectation and the three-calendar-day PDPC notification timeframe.
  • Supports documenting assessment steps and keeping evidence for late notification explanations.
"reasonable and expeditious steps to assess whether the data breach is notifiable"
More quoted passages
"Where a data breach involves any of the prescribed personal data"
"even if the data breach does not involve any prescribed personal data"
"within 30 calendar days"
"document all steps taken in assessing the data breach"
sso.agc.gov.sg5 citations
Referenced sections
  • Legal source for significant-harm categories, the 500-individual significant-scale threshold, and required contents of PDPC and affected-individual notifications.
  • Defines when a data breach is deemed to result in significant harm for PDPA breach notification.
  • Sets the prescribed number for a significant-scale data breach at 500 affected individuals.
Show 2 more
  • Lists the information that must be included in notification to affected individuals.
  • Requires the PDPC notice to include a chronological account of post-awareness steps and late-notification evidence where applicable.
"the prescribed number of affected individuals is 500"
More quoted passages
"Data breach resulting in significant harm to individuals"
"Notification to affected individuals"
"a chronological account of the steps taken"
pdpc.gov.sg2 citations
Referenced sections
  • PDPC page confirming affected-individual notices should be sent at the same time as or after PDPC notification, with PDPC-first handling for high-public-interest breaches.
  • Supports affected-individual timing and the PDPC-first approach for high-public-interest breaches.
"at the same time or after notifying the PDPC"
pdpc.gov.sg2 citations
Referenced sections
  • PDPC reporting page describing when organisations are legally required to notify the PDPC and affected persons.
  • Supports the two notifiable breach triggers: likely significant harm or significant scale.
"likely to cause significant harm"
More quoted passages
"likely to cause significant harm to the affected individuals, or affects a significant scale of individuals"
pdpc.gov.sg2 citations
Referenced sections
  • PDPC page confirming notifiable breaches should be reported as soon as practicable and no later than three calendar days.
  • States that notifiable breaches should be notified to the PDPC as soon as practicable and no later than three calendar days.
"no later than three (3) calendar days"
pdpc.gov.sg2 citations
Referenced sections
  • Supports using PDPC's self-assessment tool as a guide while recognising that organisations must still assess notifiability.
  • Supports the point that organisations should assess notifiability and that not every breach must be reported.
"the result is not definitive"
More quoted passages
"Organisations do not need to report every breach to the PDPC."
Show all related guides (37)

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.

Singapore PDPA Anonymisation and DPIA Records

Build Singapore PDPA anonymisation and DPIA records around PDPC guidance: release model, re-identification risk, data flows, action plans, safeguards, and monitoring.

Singapore PDPA Applicability Test

Test whether Singapore PDPA obligations apply by checking personal data, organisation role, data intermediary status, public agency and individual boundaries, and business contact information.

Singapore PDPA Breach Notification Playbook

A source-cited Singapore PDPA breach-notification playbook covering assessment, notifiable-breach thresholds, PDPC and affected-individual notification steps, roles, records, and citations.

Singapore PDPA Breach Notification Workflow

A source-cited Singapore PDPA workflow for containing a personal data breach, assessing notifiability, notifying PDPC or affected individuals, and retaining evidence.

Singapore PDPA Compliance Checklist

A source-cited Singapore PDPA checklist for scope, DPO accountability, consent, data intermediaries, breach notification, DNC checks, transfers, and evidence records.

Singapore PDPA Compliance Guide

Build a Singapore PDPA compliance plan covering DPO accountability, consent and notification, protection, retention, access and correction, transfers, breach notification, and DNC checks.

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 Breach Notification Thresholds

Source-cited Singapore PDPA breach notification thresholds covering significant harm, the 500-individual significant-scale test, assessment records, and notification timing.

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.