Singapore · PDPA

PDPA breach notification: the 3-day rule explained

Once an organisation assesses a breach as notifiable, Singapore's PDPA requires notifying the PDPC no later than three calendar days later. Here is what the clock means, what to include, and the penalty exposure.

3 days
PDPC window
10%
Max penalty (SG turnover)
S$1M
Max fine (small org)
s26D
PDPA section

LowerPlane serves startups in the United States, Singapore, India and worldwide.

What counts as a notifiable breach

⚠️

Significant harm

Likely to result in significant harm to an affected individual — physical, financial, reputational, emotional.

📊

Significant scale

Affects a significant number of individuals per the PDPC's guidance. Thresholds published by the PDPC apply.

A reasonable, expeditious assessment is required once the organisation becomes aware of a potential breach.

The 3-day timeline

Five steps from detection to PDPC notification and recordkeeping.

Step 1
🚨

Detect

Tasks:
  • ▸An incident is detected or reported — a user, a monitoring alert, or a vendor notification.
Step 2
🧯

Contain and assess

Tasks:
  • ▸Contain the incident and assess whether it meets the PDPA notifiable-breach threshold (significant harm or affecting a significant number of individuals).
Step 3
📨

Notify PDPC

Tasks:
  • ▸If notifiable, notify the PDPC as soon as practicable and no later than three calendar days after the assessment.
Step 4
📬

Notify individuals

Tasks:
  • ▸Notify affected individuals on or after notifying the PDPC, unless an exception applies.
Step 5
🧾

Remediate and record

Tasks:
  • ▸Complete remediation, record the incident in your incident register, and conduct a post-incident review within an agreed window.
from assessment to PDPC
3 days
then affected individuals + remediation

What to include in the PDPC notification

📝

Nature of the breach

What happened, when, and how it was discovered.

🗂️

Data categories & scale

Personal data categories affected and approximate number of individuals.

🩹

Consequences

Likely consequences for affected individuals.

🔧

Containment & remediation

Steps taken to contain, remediate, and prevent recurrence.

📞

DPO contact

DPO contact information for the PDPC's follow-up.

💰

Penalty exposure

For contraventions from 1 October 2022, PDPC financial penalties cap at:

  • • 10% of annual Singapore turnover for organisations with SG turnover above S$10M.
  • • S$1 million otherwise.
🔧

Incident runbook (4 phases)

  • • Detect — who’s on call, how incidents are logged.
  • • Assess — harm/scale checklist against PDPC guidance; DPO decides.
  • • Notify — PDPC form pre-filled; 3-day clock from assessment.
  • • Review — post-incident report; register entry; lessons learned.

See the incident response plan template.

SOC 2 & ISO 27001 do most of the work

SOC 2 common criteria CC7.3, CC7.4, CC7.5 and ISO 27001 Annex A.5.24–A.5.26 map directly to a PDPA-ready incident process. If those are already running, the gap to meet PDPA s26D is usually just the notification letter templates and the 3-day clock discipline.

Frequently asked questions

When does the 3-day clock start?

After the organisation assesses the breach as notifiable. The PDPA requires notification to the PDPC no later than three calendar days after that assessment. The assessment itself must be conducted in a reasonable and expeditious manner once the organisation becomes aware of a potential breach.

Do I always notify individuals?

Not always. The PDPA sets exceptions where notifying affected individuals is not required — for example, when remedial action has been taken that makes it unlikely significant harm will result, or where law-enforcement or other prescribed exceptions apply. Review the specific exceptions in PDPA s26D before relying on them.

What's the maximum penalty?

For contraventions from 1 October 2022, the PDPC can impose financial penalties up to 10% of annual Singapore turnover for organisations with Singapore turnover above S$10 million, otherwise up to S$1 million.

What counts as "significant harm"?

The PDPC publishes guidance on the harm threshold. Common examples: financial loss, identity theft, loss of employment, loss of insurance, physical or emotional harm, or reputational damage. If a reasonable person would conclude a type of harm is likely to result, the breach is notifiable.

Can we delay notification to investigate further?

The 3-day clock starts after you assess the breach as notifiable, not when the incident begins. You can investigate before concluding the assessment — but the investigation itself must be reasonable and expeditious. Dragging the assessment deliberately to delay notification exposes the organisation to penalties.

Does a breach at one of our vendors count as our breach?

Often yes. If a processor or subprocessor you engaged mishandles personal data for which you remain the controller, the PDPA holds you accountable. Your contracts should require vendors to notify you promptly so the 3-day PDPC clock stays in your control, not theirs.

Do we have to publicly announce a breach?

The PDPA requires notifying the PDPC and affected individuals. Public announcement is not required by law for most breaches, though some scenarios (e.g. loss of contactability of affected individuals) effectively require public notice. Larger breaches often attract press coverage regardless.

Stand up a PDPA breach runbook in a week

The LowerPlane PDPA policy pack ships with the 3-day runbook, the PDPC notification form, and the affected-individual letter template.

3 days
PDPC window
s26D
PDPA citation
10/10
PDPA Obligations covered
70%
SOC 2 overlap