Singapore — startups · corporate
How to Report a Data Breach to PDPC in 72 Hours: Singapore Startup Guide
When personal data leaks from your startup's application or database, the regulatory clock starts immediately under Singapore privacy law. Failing to assess and report a notifiable breach within 72 hours exposes founders to heavy administrative fines and regulatory enforcement. This guide covers mandatory reporting criteria under the PDPA, practical containment steps, and how to execute your regulatory response.
This guide covers everyone. Your situation is yours.
The rules are the same for everybody, but what you should do depends on your dates, your documents, and what the other side has said. On Caunsel you write down what's actually going on and get answers about your situation, with the law they rely on, or just talk it through out loud. If it needs follow-up, you keep it as a case, and when there's paperwork, it'll suggest what you need, write it up, and you can e-sign it right there.
You've read a few of these by now.
None of them were about you. That's how generic guides work. They have to cover everybody. On Caunsel you write down what's actually going on and get answers about your situation, or just talk it through out loud. If it needs follow-up, you keep it as a case, and when there's paperwork, it'll suggest what you need, write it up, and you can e-sign it right there.
Singapore PDPA Breach Notification Rules and the 72-Hour Clock
In Singapore, startups handling user or customer data are subject to the Personal Data Protection Act 2012 (PDPA) and the Personal Data Protection (Notification of Data Breaches) Regulations 2021. Under Part 6A of the PDPA, organizations face a mandatory obligation to notify the Personal Data Protection Commission (PDPC) of any 'notifiable data breach'.
The critical timeline hinges on the moment of determination: once your startup confirms or has reasonable grounds to believe that a data breach meets the notifiable threshold, you must notify the PDPC as soon as practicable, and in any event no later than three calendar days (72 hours). While the PDPC expects an assessment to be completed expeditiously (generally within 30 calendar days of initial awareness), sitting on an unconfirmed breach will not shield you from regulatory penalties of up to S$1 million or 10% of annual turnover in Singapore.
Determining If Your Breach Meets the Mandatory Reporting Threshold
Not every technical glitch or minor leak requires a report to the PDPC. A breach is legally notifiable if it meets either of two statutory tests: significant harm or significant scale.
Under the Regulations, a breach is deemed to result in significant harm if it compromises prescribed sensitive personal data, including national identification numbers (such as NRIC or FIN), financial account numbers, credit card data without security verification codes, login credentials, biometric data, or medical records. Alternatively, any breach affecting 500 or more individuals meets the significant scale test and must be reported, regardless of the sensitivity of the exposed data.
If your startup acts as a data intermediary—such as a SaaS provider or cloud infrastructure vendor processing data on behalf of an enterprise client—you are legally obligated under Section 26C of the PDPA to notify your client immediately upon becoming aware of a breach, shifting the assessment and primary PDPC notification duty to them.
Filing the PDPC Notification and Managing Regulatory Risk
Submitting a report requires completing the PDPC's official incident notification form via the Singpass or Corppass portal. Your submission must articulate the date and circumstances of the breach, the classes and estimated volume of personal data compromised, the containment measures implemented, and your proposed communications to affected individuals.
Unless an exception applies—such as where immediate remedial action neutralised the risk before harm occurred, or where technological safeguards like end-to-end encryption rendered the data inaccessible—you must also notify affected individuals as soon as practicable once the PDPC has been informed.
Because early admissions in a regulatory filing can impact future liability and investor due diligence, founders should document every incident milestone carefully. You can use Caunsel to research PDPA compliance requirements, store your incident logs and communications securely inside a dedicated legal case, or connect with an independent corporate privacy lawyer to review your submission before sending it to the PDPC.
Steps
- Isolate compromised systems, revoke compromised API keys or credentials, and preserve server logs and forensic evidence without modifying system timestamps.
- Perform an expedited assessment to confirm whether the compromised data involves prescribed categories of sensitive data or affects 500 or more individuals.
- Draft your incident summary covering cause, scope, remedial actions taken, and planned notifications using the PDPC breach notification template.
- Submit the official notification to the PDPC via the Corppass portal within 72 hours of concluding that the breach is notifiable.
- Notify affected individuals with clear guidance on protective steps (e.g., password resets, fraud monitoring) unless a statutory exception under the Regulations applies.
These are the general steps. Caunsel works out which ones apply to you, with your dates and documents.
Get help for my businessCommon mistakes
- Starting the 72-hour clock only after engineering fully patches the vulnerability, rather than from the moment the breach was confirmed to be notifiable.
- Failing to notify enterprise clients immediately when acting as a B2B data intermediary processing personal data on their behalf.
- Sending rushed, speculative emails to all registered users before confirming the scope of exposure, triggering unnecessary panic and reputational damage.
- Overwriting forensic server logs during containment, making it impossible to establish how many individuals were actually affected.
Questions people ask
Does the 72-hour window run on business days or calendar days?
Under the PDPA Regulations, the 72-hour deadline runs on calendar days, meaning weekends and Singapore public holidays are included in the 3-day count once a notifiable breach is determined.
Do we have to notify users if the compromised database was encrypted?
If the personal data was encrypted using industry-standard techniques and the decryption keys were not compromised, the breach is generally not considered likely to result in significant harm, potentially exempting you from notifying affected individuals.
What happens if a startup fails to report a notifiable breach to the PDPC?
Failure to notify the PDPC of a notifiable breach is a statutory contravention under the PDPA that can result in administrative financial penalties, formal enforcement directions, and public publication of the breach decision.
Ask Caunsel to generate an incident assessment checklist or connect with an independent Singapore privacy lawyer to review your PDPC breach filing.
Research it with the advisor, keep documents in a case, or talk to an independent lawyer. Start a subscription for AI tools.
General information only, last updated 2026-11-17. Caunsel is not a law firm and does not practise law. AI answers and this guide are not legal advice. Verify filings, deadlines, and statutes with a licensed lawyer in Singapore — startups.