
A leaked lead spreadsheet. A newsletter with every address in the CC line. A hacked WooCommerce plugin. For most SMEs, the first personal data breach starts in marketing, not the server room.
This guide covers the rules from the website, e-commerce and lead generation side. It comes from ZenWeb, a Malaysian Google Partner agency with 500+ clients. We build websites, lead forms and tracking; we are not a law firm. Every rule below comes from the Commissioner’s Data Breach Notification Guideline (Version 1.0, issued 25 February 2025), as at October 2026.
This post is general information, not legal or tax advice. Please confirm your own position with a licensed lawyer, and check the latest guidance on the Commissioner’s website before you act.
Worried your forms or plugins are the weak spot?
We audit WordPress sites for exposed form data, stale plugins and loose admin access before anything leaks. See our web development services →
Before the detail, this short explainer from a Malaysian law firm walks through the mandatory regime as it was introduced in 2025.
Source video: HHQ on YouTube. Recorded in April 2025; check the Commissioner's website for the current rules.
Quick Answer: A personal data breach is any event that leads, or is likely to lead, to the breach, loss, misuse or unauthorised access of personal data. It can be accidental or deliberate, internal or external. Sending customer data to the wrong person, a misconfigured system or a hacker extracting records all count, as does losing access to data.
Section 12B of the Personal Data Protection Act 2010, added by the Personal Data Protection (Amendment) Act 2024, created the duty. The Commissioner’s Data Breach Notification Guideline lists examples in paragraph 4.2. Translated into marketing terms, these are the ones we see most:
Not every website incident triggers data breach notification in Malaysia. A defaced homepage or scraped blog content is a security or copyright problem; see our steps for when your website content is copied. Prevention sits in our guide to PDPA security for web systems; this post covers what happens after a leak.
Quick Answer: Under data breach notification in Malaysia, you must notify the Commissioner only when a breach causes or is likely to cause “significant harm”. That covers risk of physical harm or financial loss, misuse for illegal purposes, sensitive personal data, data that could enable identity fraud, or significant scale, meaning more than 1,000 affected people. Telling customers uses the same test minus the scale limb.
Paragraphs 5.2, 5.3 and 8.2 of the guideline set the test. The table shows who you must tell under each limb.
| Criterion (para 5.2) | Notify Commissioner | Notify affected people | Marketing example |
|---|---|---|---|
| Physical harm, financial loss, credit or property damage | Yes | Yes | Customer home addresses plus order history leaked |
| Misuse for illegal purposes | Yes | Yes | Lead list stolen and used for scam calls |
| Sensitive personal data | Yes, at any volume | Yes | Form answers on religious belief or health |
| Combined data enabling identity fraud | Yes | Yes | Names with IC numbers and phone numbers |
| Significant scale (more than 1,000 people) | Yes | Not by scale alone | Newsletter sent with 3,000 addresses in CC |
Source: Personal Data Protection Commissioner, Data Breach Notification Guideline, paragraphs 5.2, 5.3 and 8.2; examples are ZenWeb’s. As at October 2026. Licence.
The sensitive data row is why we push clients to remove unnecessary questions from lead forms; our guide to sensitive personal data in lead forms explains which fields qualify. Card data is a separate risk again, covered by the PCI DSS rules for small online stores.
Quick Answer: Notify the Commissioner as soon as practicable and no later than 72 hours from the breach. The guideline’s examples start the clock when you are told of a loss, realise a mis-send, or confirm your system was compromised. If your agency or software vendor holds the data, it starts when they tell you or you find clear evidence, whichever is earlier.
Paragraph 6.1 says 72 hours “from the occurrence”, while the worked examples in paragraph 6.2 count from awareness or confirmation. That wording gap is not fully settled, so plan on the earlier reading. The guideline gives no extension for weekends or public holidays. Here is the full timeline.
| When | What must happen | Guideline paragraph |
|---|---|---|
| Hour 0 | Incident detected or reported; preliminary investigation begins | 6.2 |
| Within 72 hours | Notify the Commissioner with all mandatory form fields | 6.1, 7.2 |
| After 72 hours (if late) | Written reasons for the delay with supporting evidence | 7.7 |
| Within 7 days of notice | Notify affected people, if significant harm is likely | 9.1 |
| Within 30 days of notice | Send remaining details in phases | 7.5 |
| At least 2 years | Keep the breach register, including unreported breaches | 14.1 |
Source: ZenWeb compilation from the Commissioner’s Data Breach Notification Guideline (Version 1.0, 25 February 2025), as at October 2026. Licence.
Agencies and SaaS tools are usually data processors. Under paragraph 12 the duty does not apply to them directly, so your contract must require them to tell you promptly. For overseas tools, also check cross-border data transfer under PDPA.
Quick Answer: Contain first, then assess, then report. Isolate the affected system, disable compromised logins and stop whatever caused the leak. Work out what data, how many people and which systems were involved. Decide whether the significant harm test is met, file with the Commissioner inside 72 hours, and log everything in your breach register.
Paragraph 13 of the guideline covers containment and assessment. Here is our data breach notification Malaysia checklist for a website or marketing leak:
Not sure if you need a DPO? Read who must appoint a data protection officer in Malaysia. Here is an illustrative, not client-based, use of the 72 hours.
| Phase | Hours | Share of 72 hours |
|---|---|---|
| Confirm the breach (hours 0–6) | 6 | |
| Contain and lock down (hours 6–18) | 12 | |
| Count and classify data (hours 18–42) | 24 | |
| Prepare the form and approvals (hours 42–60) | 18 | |
| File and get confirmation (hours 60–72) | 12 |
Source: Illustrative scenario by ZenWeb; 72-hour limit from paragraph 6.1 of the Commissioner’s Data Breach Notification Guideline, as at October 2026. Licence.
Counting usually takes longest, because leads sit in several tools. Leave a filing buffer in case the online form or email fails.
Need the website side cleaned up fast?
We help lock down WordPress, close exposed form folders and pull the logs your lawyer and DPO will ask for. Read our WordPress website security guide →
Quick Answer: Use one of three channels in paragraph 7.1: the online notification form on the Department of Personal Data Protection website, the Annex B form emailed to dbnpdp@pdp.gov.my, or a hard copy of Annex B delivered to the Commissioner. The report only counts as submitted once you receive the Commissioner’s confirmation notice.
The online route is the Lapor DBN page, and the Commissioner publishes a DBN report guide for organisations. The Annex B form asks for these details, so prepare them as you assess:
One point is unclear: the guideline cites “Circular No. 2/2025”, while the Commissioner’s website lists the data breach circular as No. 1/2025. Ask your lawyer which to cite. Critical information infrastructure entities also notify the National Cyber Security Agency; see the Cyber Security Act 2024 and your website for who that covers.
Quick Answer: Yes, if the breach is likely to cause them significant harm. Tell them directly and individually, in plain language, within 7 days of notifying the Commissioner. Explain what happened, the likely consequences, what you are doing, what they can do, and who to contact. Send it separately from newsletters or promotions.
Paragraph 10 lists email, SMS, direct messaging and post as individual channels. A website or social media notice is allowed only where direct contact is impractical, such as outdated contact details. Three practical rules:
One exception from the guideline’s examples: if strong security made the data unreadable to the attacker, customers may not need a notice, though the Commissioner still does.
Quick Answer: For data breach notification in Malaysia, most marketing leaks turn on two facts: how many people are affected and whether the data includes IC numbers, financial details or sensitive fields. A small mis-sent list of names and emails is usually record-only. A large exposed lead sheet or any leak with IC numbers usually needs a report to the Commissioner.
The table applies the test to scenarios we see on SME websites. It is ZenWeb’s reading, not an official ruling.
| Scenario | Commissioner | Customers |
|---|---|---|
| 200 lead names and emails sent to the wrong vendor | Unlikely | Unlikely |
| Newsletter sent with 3,000 addresses visible in CC | Yes (scale) | Assess |
| Public lead sheet with 1,500 names and phone numbers | Yes (scale) | Assess |
| Form entries with IC numbers exposed by a plugin flaw | Yes | Yes |
| Online store database with addresses and orders stolen | Yes | Likely |
| Ransomware locks the CRM with no backup | Yes | Likely |
Source: ZenWeb’s reading of paragraphs 5.2 to 8.3 of the Commissioner’s Data Breach Notification Guideline, as at October 2026. Interpretation only; confirm with a lawyer. Licence.
Check two newer leak routes. Session recordings can capture typed form fields; see heatmaps and session recordings under PDPA. Server-side ad events send customer data to platforms; read Meta Conversions API and PDPA.
Quick Answer: Data breach notification in Malaysia also means record-keeping. Keep a breach register for at least two years, covering every breach including those you did not report. Have a written response plan with escalation steps, roles, containment, notification decisions, communications and a post-incident review. Failing to notify under section 12B can mean a fine of up to RM250,000, up to two years’ jail, or both.
The penalty is stated in paragraph 2.2 of the Commissioner’s guideline. Paragraph 14 says the register should record, at minimum:
Holding less data shrinks future breaches. Set a retention period using our guide to how long you can keep leads under PDPA. After any fix to your forms, re-test them as part of your normal CRO process so security changes do not quietly break conversions. For the wider duty list, see our PDPA compliance checklist for marketers.
Data breach notification in Malaysia is a 72-hour test of preparation. As at October 2026, you must notify the Commissioner when a breach risks significant harm or affects more than 1,000 people, tell affected customers within 7 days if harm is likely, and log every incident for two years. Have three things ready: a short response plan, a blank Annex B form, and forms that collect only the data they need. For the website side, our web development team can help.
Yes. Since 1 June 2025, section 12B of the Personal Data Protection Act 2010 requires data controllers to notify the Commissioner of breaches that cause or are likely to cause significant harm, and to notify affected people where harm is likely.
No later than 72 hours to the Commissioner, and no later than 7 days after that notice to affected people. Missing details can follow in phases within 30 days.
Yes. Size is not part of the test; the type of data and the number of people affected are.
Not directly. The guideline says the duty sits with the data controller, so your contract should require your agency or vendor to tell you promptly and help you report.
No. ZenWeb handles the website and marketing side, such as securing forms, plugins and tracking. Confirm your notification duties with a licensed lawyer.
Cite this page: ZenWeb (2026). Data Breach Notification Malaysia: Steps After a Leak. https://zenweb.my/blog/data-breach-notification-malaysia/
You may quote our data with this credit and a link. See our Terms of Use.
Make your website harder to leak
Talk to ZenWeb about lean lead forms, secure plugins and PDPA-friendly tracking, so a bad day stays small. We handle the website side; your lawyer handles the legal advice.
Get A Free Proposal
Complete the form and our team will contact you to discuss your goals. Let’s grow your business.
Chat with us on WhatsApp
Tell us a little about what you need. We'll open WhatsApp with your message ready to send.