facebook-pixel

How to Report a Data Breach to PDPC Singapore: Complete 2026 Guide

L
Lunyb Security Team
··9 min read

If your organisation has experienced a data breach in Singapore, you have a legal obligation under the Personal Data Protection Act (PDPA) to assess it and, in many cases, notify both the Personal Data Protection Commission (PDPC) and affected individuals. This guide walks you through the entire reporting process, from initial assessment to post-notification remediation, using the latest requirements in effect for 2026.

What Counts as a Data Breach Under Singapore's PDPA?

A data breach under Singapore's PDPA is any unauthorised access, collection, use, disclosure, copying, modification, or disposal of personal data, or the loss of any storage medium or device on which personal data is stored where the data is likely to be subject to such unauthorised access.

The Data Breach Notification (DBN) obligation came into force on 1 February 2021 through amendments to the PDPA. Since then, every organisation that collects, uses, or discloses personal data in Singapore has been required to maintain procedures to detect, assess, and notify breaches within strict timelines.

Examples of Reportable Incidents

  • A ransomware attack that encrypts a customer database
  • An employee emailing a spreadsheet of customer NRICs to the wrong recipient
  • A lost laptop containing unencrypted HR records
  • A misconfigured cloud storage bucket exposing user profiles
  • A phishing attack that compromises staff email accounts with customer correspondence

When Must You Notify the PDPC?

Under Section 26D of the PDPA, you must notify the PDPC of a notifiable data breach as soon as practicable, and in any case no later than 3 calendar days after you have assessed the breach to be notifiable.

A breach is notifiable if it meets either of these thresholds:

  1. Significant scale: The breach affects 500 or more individuals.
  2. Significant harm: The breach results in, or is likely to result in, significant harm to affected individuals.

What Counts as "Significant Harm"?

The PDPC's Personal Data Protection (Notification of Data Breaches) Regulations 2021 specify categories of personal data that are automatically deemed to cause significant harm if breached. These include:

  • Full name or alias in combination with NRIC, FIN, passport, or birth certificate numbers
  • Financial account details (bank account numbers, credit card numbers)
  • Health information (medical history, diagnoses, treatments)
  • Life insurance policy details
  • Account login credentials
  • Information about minors and vulnerable individuals
  • Adoption-related data and private key information

The 30-Day Assessment Clock

From the moment you have reason to believe a data breach has occurred, you must conduct a reasonable and expeditious assessment within 30 calendar days to determine whether it is notifiable. You cannot sit on a suspected breach indefinitely; the PDPC expects a documented, time-bound assessment process.

Step-by-Step: How to Report a Data Breach to PDPC

Step 1: Contain the Breach

Before notification comes containment. Take immediate action to stop the breach from continuing or expanding:

  1. Isolate affected systems from the network
  2. Revoke compromised credentials and reset passwords
  3. Recall misdirected emails where possible
  4. Preserve logs and forensic evidence
  5. Engage your incident response team or external forensics vendor

Step 2: Conduct the Breach Assessment

Document your assessment carefully. Address these questions:

  • What personal data was involved?
  • How many individuals are affected?
  • What is the cause of the breach?
  • Does the data fall within the prescribed categories of significant harm?
  • Have any mitigating factors (e.g. strong encryption) reduced the risk?

If encrypted data was exposed but the decryption key remains secure, the breach may not require notification. This exception is spelled out in the regulations and is one of the strongest arguments for encrypting personal data at rest.

Step 3: Notify the PDPC Within 3 Days

Once you determine the breach is notifiable, submit the notification through the PDPC's online Data Breach Notification Form, accessible at the PDPC website. The 3-day clock starts from your assessment conclusion, not from breach discovery.

Your notification must include:

  1. Facts of the breach (what happened, when, how discovered)
  2. Nature and volume of personal data involved
  3. Estimated number of affected individuals
  4. Potential harm to individuals
  5. Containment and remediation actions taken or planned
  6. Steps to prevent recurrence
  7. Contact details of your Data Protection Officer (DPO)

Step 4: Notify Affected Individuals

Where the breach is likely to cause significant harm, you must also notify affected individuals in a clear and easily understandable manner, at the same time or after notifying the PDPC. Notification channels can include email, SMS, letter, or public notice if direct contact is not feasible.

Individual notification is not required if:

  • You have taken remedial actions that make significant harm unlikely (e.g. revoking access, confirming data destruction)
  • Technological protections (e.g. encryption) render the data unintelligible
  • The PDPC or a law enforcement agency instructs you to withhold notification

Step 5: Document Everything

Maintain a written record of the breach, the assessment, decisions made, and actions taken. The PDPC can request this documentation during follow-up or in a future audit.

Notification Timeline at a Glance

MilestoneDeadlineAction Required
Breach discovered or suspectedDay 0Begin containment and assessment
Assessment completedWithin 30 daysDetermine if breach is notifiable
PDPC notificationWithin 3 days of assessmentSubmit online DBN form
Individual notificationAt the same time or after PDPC notificationNotify affected persons where significant harm likely
Follow-up reportAs requested by PDPCProvide additional information or updates

Data Intermediaries: Different Obligations

If you process personal data on behalf of another organisation (e.g. a cloud vendor, a payroll service), you are a data intermediary. Your obligation is to notify the organisation you process data for without undue delay once you have reason to believe a breach has occurred. The primary organisation then conducts the assessment and notifies the PDPC.

Your contracts with data intermediaries should explicitly require prompt breach notification, cooperation during assessment, and preservation of evidence. Weak intermediary clauses are one of the most common gaps uncovered during PDPC investigations.

Penalties for Non-Compliance

Failure to notify a notifiable data breach can attract a financial penalty of up to S$1 million, or in the case of organisations with annual turnover exceeding S$10 million, up to 10% of annual Singapore turnover (whichever is higher) under the enhanced penalty regime that took effect on 1 October 2022.

The PDPC has shown willingness to issue substantial fines, with several organisations fined six-figure sums in recent years for breach-related failures, including inadequate security arrangements, delayed notification, and poor vendor oversight.

Preparing Before a Breach Happens

The best time to prepare for a breach notification is well before one occurs. Organisations that handle breach notifications smoothly tend to share these practices:

1. Appoint and Train a DPO

Every organisation must designate at least one Data Protection Officer. Your DPO's contact information must be publicly available and registered with ACRA.

2. Maintain a Data Inventory

You cannot assess what was breached if you do not know what data you hold, where it sits, and who has access. A current data inventory dramatically speeds up breach assessment.

3. Implement a Written Incident Response Plan

Document who does what, in what order, with what authority. Run tabletop exercises at least annually.

4. Encrypt Personal Data at Rest and in Transit

Encryption is both a compliance obligation under the Protection Obligation and a get-out clause under the DBN regulations.

5. Review Third-Party Risk Regularly

Many notifiable breaches originate at vendors. Review your intermediaries' security certifications, access controls, and breach notification clauses annually.

6. Use Privacy-First Tools for Public-Facing Links

When you share marketing links, support documents, or customer-facing resources, use tools that respect user privacy and minimise data exposure. Privacy-first services like Lunyb offer short links without aggressive tracking cookies or extensive behavioural fingerprinting, reducing the personal data you process in the first place. You can read more in our honest review of Lunyb.

Common Mistakes Organisations Make

  • Starting the 3-day clock too late: The clock begins when your assessment concludes, but delaying the assessment itself can still breach the 30-day window.
  • Under-reporting scope: Submitting an initial low estimate and later discovering the real number was much larger undermines your credibility with the PDPC.
  • Vague remediation statements: "We are reviewing our processes" is not a remediation plan. Specific, time-bound actions are expected.
  • Forgetting individual notification: Many organisations notify the PDPC but delay or skip telling affected individuals.
  • Treating the notification as the end: The PDPC often follows up with requests for further information, root cause analysis, and remediation evidence.

After You Notify: What Happens Next

The PDPC will acknowledge your submission and may:

  1. Request additional information or clarification
  2. Open a formal investigation under Section 50 of the PDPA
  3. Issue directions requiring specific remedial actions
  4. Impose a financial penalty
  5. Close the matter with no further action if your response was adequate

Cooperation, transparency, and demonstrating genuine remediation significantly affect the outcome. The PDPC has publicly stated that organisations which self-report promptly, cooperate fully, and implement meaningful fixes often receive lower penalties than those that obstruct or delay.

Frequently Asked Questions

Do I need to notify PDPC if encrypted data was stolen?

Not necessarily. If the personal data was protected by encryption (or similar technological measures) such that it remains unintelligible to unauthorised persons, and the decryption key was not compromised, the breach may fall outside the notification threshold. You still need to document the assessment and reasoning.

What if I discover the breach happened months ago?

The 30-day assessment and 3-day notification clocks start from the point you have reason to believe a breach occurred. However, a prolonged failure to detect breaches can itself indicate inadequate security arrangements, which is a separate PDPA obligation. Report promptly and be prepared to explain detection delays.

Can I notify PDPC before completing my investigation?

Yes, and in many cases you should. You can submit an initial notification with the facts known at the time and update it as your investigation progresses. The PDPC prefers early notification with follow-up updates over delayed notification waiting for full facts.

What is the difference between PDPC and the Cyber Security Agency (CSA)?

The PDPC enforces the PDPA and handles personal data breach notifications. The CSA, through SingCERT, handles cybersecurity incidents under the Cybersecurity Act, which applies to critical information infrastructure. A single incident can require notification to both agencies.

Can affected individuals sue my organisation for a data breach?

Yes. Section 48O of the PDPA grants individuals a private right of action for loss or damage suffered directly as a result of a PDPA contravention. Civil claims are separate from PDPC enforcement, and both can occur from the same breach.

Final Thoughts

Reporting a data breach to the PDPC is not just a compliance checkbox; it is a structured process that tests how well your organisation understands its data, its vendors, and its security posture. Organisations that treat the DBN obligation as an opportunity to mature their privacy programme, rather than a punishment, tend to emerge from breaches with stronger reputations and lower penalties.

Build the processes now, before the incident happens. The 3-day notification window is not the time to write your incident response plan from scratch.

Protect your links with Lunyb

Create secure, trackable short links and QR codes in seconds.

Get Started Free

Related Articles