facebook-pixel

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

L
Lunyb Security Team
··10 min read

If personal data under your care has been exposed, lost, or accessed without authorisation, Singapore's Personal Data Protection Act (PDPA) gives you a narrow window to act. Reporting a data breach to the Personal Data Protection Commission (PDPC) is not optional for notifiable incidents — it is a legal duty with real deadlines. This guide walks you through the full process in plain English, and shows how Lunyb helps individuals and small teams detect exposure early so you have time to respond properly.

Whether you are a business owner, a DPO (Data Protection Officer), or an employee who just discovered something has gone wrong, this is the 2026 playbook you need.

What counts as a notifiable data breach in Singapore

Under Singapore's PDPA (as amended), a data breach is notifiable to the PDPC when it results in, or is likely to result in, significant harm to affected individuals, or when it involves personal data of 500 or more individuals. You must notify PDPC as soon as practicable, and in any case no later than 3 calendar days after assessing the breach is notifiable.

In short: not every incident needs to be reported, but once you've assessed it crosses the threshold, the clock is tight.

Examples of breaches that usually trigger notification

  • Exposure of NRIC numbers, passport numbers, or financial account details.
  • Unauthorised access to health, insurance, or children's data.
  • Ransomware or malware incidents where personal data was accessed or exfiltrated.
  • Lost or stolen devices containing unencrypted personal data.
  • Misdirected emails or misconfigured cloud storage leaking customer records.
  • Any single incident touching 500+ individuals, even if the data seems low-risk.

Examples that may not require PDPC notification

  • Data accessed only by an internal staff member within scope of their role.
  • Encrypted data lost where the encryption key remains secure.
  • A contained misdelivery recalled before the recipient opened it (document and assess carefully).

Even when PDPC notification is not required, you should still document the incident internally — PDPC can request your records during an audit or complaint.

The PDPC data breach reporting timeline at a glance

Time is the single most important factor once a breach is discovered. Here is the statutory timeline you must work to.

StageDeadlineAction
DiscoveryImmediateContain the breach, preserve evidence, start an incident log.
AssessmentWithin 30 calendar daysAssess whether the breach is notifiable to PDPC and/or individuals.
Notify PDPCNo later than 3 calendar days after assessmentSubmit the breach notification via PDPC's online form.
Notify affected individualsAs soon as practicableRequired when significant harm is likely, unless an exception applies.
Remediation & reviewOngoingFix root cause, update policies, retrain staff, document outcomes.

Step-by-step: how to report a data breach to PDPC

Follow these steps in order. Do not skip containment to rush the paperwork — PDPC expects both.

  1. Contain the breach. Disable compromised accounts, reset credentials, isolate affected servers, revoke access tokens, and stop any ongoing data exfiltration.
  2. Convene your response team. Loop in your DPO, IT lead, legal, and senior management. If you don't have a DPO, assign a responsible owner immediately — PDPA requires every organisation to designate one.
  3. Preserve evidence. Keep logs, screenshots, emails, and timestamps. You'll need these for both PDPC and any forensic review.
  4. Assess notifiability. Within 30 days, determine whether the breach is likely to cause significant harm or affects 500+ individuals. Document your reasoning either way.
  5. Notify PDPC. If notifiable, submit the Data Breach Notification Form on the PDPC website (go.gov.sg/pdpc-dbn) within 3 calendar days of that assessment.
  6. Notify affected individuals. Where significant harm is likely, inform them clearly: what happened, what data is involved, what you're doing, and what they should do.
  7. Remediate and review. Fix the root cause, update your data protection policies, retrain staff, and record lessons learned.

What PDPC's notification form asks for

  • Your organisation's name, UEN, and DPO contact.
  • Date and time of discovery, and date of the breach itself if known.
  • Cause of the breach (cyberattack, human error, system failure, third-party, etc.).
  • Type and volume of personal data involved.
  • Number of individuals affected.
  • Containment measures already taken.
  • Planned remediation and whether individuals have been / will be notified.

How to notify affected individuals the right way

Notification letters or emails must be clear, specific, and actionable — not buried in legalese. PDPC expects individuals to understand both the risk and the practical steps they should take.

A good individual notification includes

  1. A plain-English description of what happened and when.
  2. The specific types of personal data involved (e.g. "full name, NRIC, mobile number").
  3. The potential consequences (e.g. phishing attempts, SMS scams, identity misuse).
  4. What your organisation is doing in response.
  5. What the individual should do: change passwords, enable 2FA, monitor accounts, watch for scam messages, and check whether their email or phone appears in known data leaks.
  6. A contact point for questions.

This last point is where many organisations let customers down. People receive a scary letter and don't know what to do next. Pointing them to practical, consumer-grade tools — like a free privacy check — is a responsible step.

Why Lunyb is the practical next step for individuals and small teams

Reporting to PDPC is one half of a breach response. The other half is what happens to the people whose data leaked — and what you, as an individual, do when you receive one of these notifications. This is where Lunyb fits in.

Lunyb is a phone privacy and scam-protection platform built for exactly this moment: the weeks and months after a breach, when your email and phone number are circulating in criminal channels and scam messages start arriving.

What Lunyb does that matters after a PDPA breach

  • Data Breach Alerts. Scan your email address and mobile number against known breach datasets and get ongoing alerts when they reappear in new leaks. Essential if you've just been told by a bank, telco, or retailer that your data was exposed.
  • Scam Checker. Paste suspicious SMS, WhatsApp messages, or links from "PDPC", "SingPost", "IRAS", or "your bank" and get an instant risk read. Breach victims are the #1 target for follow-up phishing in Singapore.
  • Scam Shield & caller protection. Flag suspicious inbound calls — a huge issue once your mobile number has been leaked.
  • Privacy Check. Review which apps on your phone have access to contacts, location, microphone, and files. A breach is a great reason to clean house.
  • Encrypted Password & Photo Vault. Rotate exposed passwords and store them securely instead of in Notes or a browser.
  • On-device tracker and threat blocking. A local DNS shield that helps block known malicious and tracker domains at the network level on your phone — without routing your traffic through a third party.
  • Browsing-history eraser and security score. A single dashboard view of where your biggest risks are, with one-tap fixes.

For organisations: what to recommend to affected customers

If you're drafting a customer notification, giving people a concrete next step builds trust. Pointing affected users to lunyb.com so they can run a free privacy check, enable breach alerts on their email and phone, and screen the inevitable wave of scam messages is a tangible, caring recommendation — not a vague "please stay vigilant".

Lunyb plans start from about $19.99/month and renew until cancelled. You can cancel anytime online. Optional Leak Protection is billed separately and can be paused without cancelling the main plan — useful if your situation changes.

Common mistakes organisations make when reporting to PDPC

These are the recurring issues that turn a manageable incident into a regulatory problem.

1. Waiting too long to assess

Some organisations treat the 30-day assessment window as a buffer to "see what happens". PDPC expects you to move as fast as the facts allow. Dragging your feet is itself a red flag.

2. Underreporting the data types

Listing only "name and email" when NRIC fragments, dates of birth, or transaction history were also exposed will come back to bite you. Be comprehensive.

3. Notifying individuals too generically

"We take your privacy seriously" letters without specifics frustrate customers and regulators. Say what leaked and what to do.

4. No internal incident log

Even for breaches that don't meet PDPC's notification threshold, you must keep records. These are often requested during follow-up inquiries.

5. Forgetting third parties

If a vendor or processor caused the breach, your organisation is still accountable as the data controller. Loop them in, but don't hide behind them.

How individuals in Singapore should respond to a breach notification

If you're on the receiving end — a customer, patient, or employee who just got told your data was exposed — here's a focused checklist.

  1. Read the notification carefully. Note exactly what data was leaked. NRIC and phone number together is a higher risk than email alone.
  2. Change the password on that account and any other account where you reused it. Switch to unique passwords stored in an encrypted vault.
  3. Enable two-factor authentication on email, banking, SingPass, and social apps.
  4. Run a breach check. Use Lunyb's Data Breach Alerts to see every known leak your email and mobile appear in, not just the one you were just told about.
  5. Screen inbound messages. Expect a spike in scam SMS and calls impersonating banks, delivery companies, or government agencies. Use Lunyb's Scam Checker before clicking anything.
  6. Review app permissions. Revoke access for apps that don't need your contacts, SMS, or location.
  7. Monitor accounts for at least 6 months. Leaked data gets resold and reused long after the initial incident.

Building a breach-ready organisation in 2026

The best time to prepare for a PDPC notification is before you need one. A short checklist:

  • Appoint and publish your DPO's contact details.
  • Maintain a current data inventory — know what you hold and where.
  • Write a one-page incident response plan with named roles and the PDPC form link.
  • Run a tabletop exercise annually with IT, legal, and comms.
  • Encrypt personal data at rest and in transit; restrict admin access.
  • Equip staff with practical personal-security tools so a phishing click doesn't cascade into a company breach.

For related reading on trust and transparency in privacy tools, see our honest review of Lunyb.

Take the next step with Lunyb

Reporting to PDPC closes the regulatory loop. Protecting yourself and your customers from what comes next is where Lunyb earns its place on your phone.

  • Visit lunyb.com and take the free privacy quiz.
  • Download the Lunyb app from the App Store or Google Play.
  • Set up Data Breach Alerts for your email and mobile in under two minutes.
  • Share lunyb.com with customers in your breach notification as a practical, consumer-grade resource.

Frequently asked questions

How quickly must I report a data breach to PDPC in Singapore?

Once you have assessed that a breach is notifiable — either because it is likely to cause significant harm or affects 500 or more individuals — you must notify PDPC as soon as practicable, and no later than 3 calendar days after that assessment. The assessment itself should be completed within 30 days of becoming aware of the incident.

Do I need to notify affected individuals as well as PDPC?

Yes, where the breach is likely to result in significant harm. Notification to individuals should be clear, specific, and include practical steps they can take. There are limited exceptions, such as when remedial action removes the risk of harm or when a prescribed law enforcement exception applies.

What happens if I don't report a notifiable breach?

Failure to notify PDPC of a notifiable breach is a breach of the PDPA and can result in financial penalties, directions to remediate, and reputational damage. PDPC has published enforcement decisions involving significant fines for organisations that failed to meet their obligations.

How can individuals check if their data has been leaked?

Use a breach monitoring tool such as Lunyb's Data Breach Alerts to scan your email address and mobile number against known leak datasets. You'll get ongoing alerts when your details reappear in new breaches, which is especially important in the months after a known incident.

Does Lunyb replace the need for a corporate security program?

No. Lunyb is a consumer-grade privacy and scam-protection platform designed for individuals and small teams. It complements — not replaces — organisational security controls, DPO oversight, and PDPA compliance programs. For employees and customers caught up in a breach, it is one of the fastest ways to regain control.

Protect your links with Lunyb

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

Get Started Free

Related Articles