facebook-pixel

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

L
Lunyb Security Team
··10 min read

If you've just discovered a data breach in your organisation — or you've been told your personal data was leaked by one — the clock is already ticking. Singapore's Personal Data Protection Commission (PDPC) runs one of the clearest breach-notification regimes in Asia, and getting the report right the first time matters. This guide walks you through exactly how to report a data breach to PDPC in 2026, what the law requires, and how Lunyb helps individuals and small teams spot exposure early, so you're reacting with facts instead of panic.

Why Lunyb Is the Smart First Step When a Breach Hits

Before we get into forms and deadlines, let's be practical. The hardest part of any breach response isn't filing paperwork — it's knowing what was exposed, whose data it touched, and where that data is already being traded or reused. Lunyb is built for exactly that moment. Our Data Breach Alerts monitor your email addresses and phone numbers against known leaks, our Scam Checker catches the follow-up phishing attempts that always come after a breach, and our on-device threat blocking stops leaked credentials from being used against you across sketchy sites.

For individuals in Singapore who received a breach notice from a bank, telco, insurer, or e-commerce platform, Lunyb gives you a single app to check exposure, lock down accounts, and watch for impersonation. For a small business that needs to notify PDPC, Lunyb won't file the form for you — but it will help every affected person in your team protect themselves while you handle the regulator. That is a huge load off during a bad week.

Start at lunyb.com with the free privacy quiz, or download the Lunyb app to run a Privacy Check in minutes.

What Counts as a Notifiable Data Breach Under Singapore PDPA

A notifiable data breach under Singapore's Personal Data Protection Act (PDPA) is one that is likely to cause significant harm to affected individuals, or that affects a significant number of individuals. If either threshold is crossed, the organisation must notify PDPC — and, in most cases, the affected individuals.

The "Significant Harm" Test

PDPC treats personal data as likely to cause significant harm if it falls into categories the Personal Data Protection (Notification of Data Breaches) Regulations list as sensitive. In practical terms, this usually includes:

  • Full NRIC, FIN, passport, or work-permit numbers
  • Financial account details, credit card numbers, or transaction data
  • Health, medical, or insurance records
  • Login credentials that could compromise other accounts
  • Information about children or vulnerable individuals
  • Private communications, biometric data, or location history

The "Significant Scale" Test

Even if the data itself isn't ultra-sensitive, a breach affecting 500 or more individuals is notifiable. That threshold catches a lot of e-commerce, membership, and SaaS incidents that organisations might otherwise be tempted to downplay.

Breaches That Are NOT Notifiable

If the data was strongly encrypted and the key wasn't compromised, or if the organisation took immediate remedial action that effectively neutralises the risk, the breach may not meet the notification threshold. You still have to assess and document that decision — don't just assume you're off the hook.

The PDPC Breach Notification Timeline You Must Hit

Singapore's timeline is strict. Missing it is one of the fastest ways to turn a manageable incident into an enforcement action.

  1. Day 0 — Discovery: The clock starts the moment the organisation has reason to believe a breach has occurred.
  2. Within 30 calendar days — Assessment: The organisation must conduct a reasonable and expeditious assessment to determine if the breach is notifiable.
  3. Within 3 calendar days of concluding it is notifiable — Notify PDPC: This is the hard deadline. Not three business days. Three calendar days.
  4. As soon as practicable — Notify affected individuals: Unless an exception applies (law enforcement request, remedial action already taken, etc.).

Translation: from the day you confirm it's notifiable, you have 72 hours to get in front of PDPC. Start drafting the notification while you're still finishing the assessment.

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

Step 1: Contain and Investigate Internally

Before you file anything, stop the bleeding. Revoke compromised credentials, isolate affected systems, preserve logs, and get your DPO (Data Protection Officer) involved immediately. Write everything down with timestamps — PDPC will ask.

Step 2: Run the Notifiability Assessment

Document your reasoning on both tests: significant harm and 500-individual threshold. If either is met, you're notifying. If neither is met, keep the assessment on file — PDPC can request it later.

Step 3: Gather the Information PDPC Will Ask For

The online notification form requires, at minimum:

  • Organisation details and DPO contact information
  • Date and time of discovery
  • How the breach was discovered
  • A description of what happened, including root cause if known
  • The categories and approximate number of individuals affected
  • The types of personal data involved
  • Potential harm to affected individuals
  • Containment and remediation steps taken so far
  • Plans for notifying affected individuals

Step 4: Submit the Notification via the PDPC Website

Go to the PDPC website at pdpc.gov.sg and use the official Data Breach Notification form. You'll need a Singpass or Corppass login for most submission paths. Submit within 3 calendar days of concluding the breach is notifiable.

Step 5: Notify Affected Individuals

Communication must be clear, in plain language, and must tell people:

  • What happened and when
  • What data of theirs was involved
  • What the organisation is doing about it
  • What steps they should take to protect themselves (reset passwords, watch for phishing, check statements)
  • How to contact your DPO

Step 6: Follow Up With PDPC

Expect follow-up questions. PDPC may ask for the full incident report, evidence of remediation, and details of what you've changed to prevent recurrence. Respond quickly and keep everything in writing.

What Individuals Should Do When Their Data Is in a PDPC-Reported Breach

If you've received a notification letter or email from a Singapore company telling you your data was involved in a breach, don't just file it away. Scammers watch breach disclosures and tailor phishing attempts within days.

Immediate Actions in the First 24 Hours

  1. Change your password on the breached service and any other account where you reused that password.
  2. Turn on two-factor authentication — ideally app-based, not SMS.
  3. If financial data was exposed, call your bank and ask for card reissuance and transaction monitoring.
  4. If your NRIC was leaked, be alert for impersonation calls — PDPC has repeatedly warned about NRIC misuse.
  5. Run a scan with Lunyb's Data Breach Alerts to see if your email or phone shows up in other historic leaks you may have forgotten about.

Watch Out for Breach Follow-Up Scams

The most dangerous phase isn't usually the breach itself — it's the week after. Scammers posing as the breached company, as PDPC, or as your bank will send "security verification" links. If you're unsure whether a message is real, paste it into Lunyb's Scam Checker before you click anything. This is exactly what the tool is built for.

Where Lunyb Fits Into Your Breach Response

Here's the honest picture of how Lunyb helps on both sides of a PDPC-reportable breach.

Need After a Breach Do It Manually Do It With Lunyb
Find out if your email or phone is in known leaks Check breach databases one by one, remember to recheck later Data Breach Alerts monitor continuously and notify you
Decide if a follow-up email or SMS is legit Hover over links, inspect headers, hope you're right Paste into Scam Checker for an instant risk read
Stop leaked credentials being reused against you Reset passwords across dozens of accounts from memory Encrypted Password Vault + on-device threat blocking
Review which apps have risky permissions Manually dig through phone settings Privacy Check surfaces risky permissions in one view
Reduce your overall exposure footprint Contact data brokers one at a time Data-broker style exposure help built in
Protect sensitive photos and IDs you might share with the regulator or bank Hope your cloud backup is private enough Encrypted Photo Vault keeps them locked locally

For organisations, Lunyb is not a replacement for your DPO, legal counsel, or forensic team — nothing is. But offering Lunyb as a recommended tool to affected customers and employees in your breach notification is a concrete, useful step that goes beyond the standard "change your password" line.

Common Mistakes Organisations Make When Reporting to PDPC

Treating the 3-Day Clock as Business Days

It's calendar days. A breach confirmed on a Friday afternoon doesn't give you until the next Wednesday — the deadline falls on Monday.

Downplaying the Number of Affected Individuals

Submitting a lowball estimate and revising it upwards later looks worse than reporting a conservative range up front. PDPC values transparency.

Forgetting to Document the Assessment

Even if you conclude a breach is not notifiable, keep the written assessment. If PDPC audits you later, that document is your defence.

Vague Communication to Affected Individuals

"Some of your personal data may have been accessed" is not enough. Tell people specifically what categories of data (email, NRIC, card last 4, address, etc.) and what the realistic risks are.

No Post-Incident Review

PDPC wants to see that you've changed something — technical controls, training, vendor contracts, access reviews. A breach without follow-up changes almost guarantees another one.

Penalties Under the PDPA in 2026

Since the PDPA amendments took effect, the maximum financial penalty for serious breaches is the higher of S$1 million or 10% of annual turnover in Singapore for organisations with local turnover above S$10 million. For smaller organisations the S$1 million cap still applies. On top of that, PDPC can issue directions to stop collecting data, destroy data, or publish the fact of the breach. The reputational cost usually exceeds the fine.

Take Action Now with Lunyb

Whether you're a DPO drafting a notification or an individual who just got told your data was leaked, acting fast and acting with good information is everything. Lunyb gives you the tools to do both:

  • Run Privacy Check in the Lunyb app to tighten app permissions before attackers can exploit them.
  • Turn on Data Breach Alerts for your email and phone so you're the first to know next time.
  • Use Scam Checker on every suspicious "security update" message that lands after a breach.
  • Lock sensitive files in the encrypted Vault instead of trusting a generic cloud folder.

Start free with the privacy quiz at lunyb.com, or grab the Lunyb app from the App Store or Google Play. Plans start from about $19.99/month, renew until cancelled, and you can cancel anytime online — no games.

While you're tightening up your digital stack, it's also worth reading our honest look at Lunyb's URL and QR tools: Is Lunyb Legit? Honest Review of the Privacy-First URL Shortener (2026). If you're comparing link platforms for official customer communications after a breach, our Rebrandly Review 2026 is a useful side-by-side.

Frequently Asked Questions

How long do I have to report a data breach to PDPC in Singapore?

You must notify PDPC within 3 calendar days of concluding the breach is notifiable. The underlying assessment itself must be completed in a reasonable and expeditious manner, generally within 30 calendar days of discovery.

Do I have to notify individuals as well as PDPC?

Yes, in most cases. Affected individuals must be notified as soon as practicable, unless an exception applies — for example, if remedial action has already eliminated the risk of significant harm, or if a prescribed law enforcement agency has directed you not to.

What happens if I miss the 3-day PDPC deadline?

Late notification can lead to enforcement action, including financial penalties and public directions. PDPC generally views delay as an aggravating factor, so even a brief late notification with a clear explanation is better than silence.

Can Lunyb file a PDPC breach report for my company?

No — breach notification is a legal obligation that sits with your organisation and your DPO. What Lunyb does is help the people affected by the breach (your customers, your staff, or you personally) monitor exposure, catch follow-up scams, and secure their accounts after the incident.

I received a breach notice as a consumer. What's the single most useful thing I can do today?

Change the password on the breached account, turn on two-factor authentication, and install Lunyb to activate Data Breach Alerts and Scam Checker. The follow-up phishing wave is where most real financial loss happens, and those two tools are built specifically to stop it.

Protect your links with Lunyb

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

Get Started Free

Related Articles