
A customer emails: “What data do you hold about me? And please delete it.” Most Malaysian SMEs have no process for this. The data sits in a CRM, a Facebook lead export, an email newsletter tool and a salesperson’s WhatsApp, and nobody knows who should answer.
This guide explains what the Personal Data Protection Act 2010 requires when someone asks to see, correct or delete their data. It then gives you a step-by-step way to handle each request across your marketing systems. It comes from ZenWeb, a Malaysian Google Partner agency with 500+ clients. We build websites, lead forms, CRM flows and tracking; we are not a law firm. Rules are stated as at October 2026.
This post is general information, not legal or tax advice. Please confirm how the rules apply to your business with a licensed lawyer or tax agent before you act.
Can you find one customer’s data in under an hour?
We connect your website forms, lead ads and chat into one CRM, so a data request becomes a quick search instead of a week-long hunt. Explore our digital marketing services →
Before the detail, this webinar from a Malaysian cyber security research centre explains the 2024 PDPA amendments, which changed several of the rules covered below.
Source video: Centre of Research for Cyber Security and Network on YouTube. Recorded in August 2024, before the amendments came into force; it covers the amendments generally, not data requests specifically.
Quick Answer: Part IV of the PDPA gives customers six main rights over their data. They can access it, correct it, withdraw consent, stop direct marketing and stop processing that causes damage or distress. Since June 2025, they can also move it to another business. Each right starts with a written request or notice to you.
The Personal Data Protection Act 2010 (Act 709) covers every name, phone number and email your ads, forms and chats collect. The Personal Data Protection (Amendment) Act 2024 renamed the “data user” a “data controller”. If you decide why and how customer data is used, that is you.
| Right | Section | What the customer can ask |
|---|---|---|
| Access | 30 to 33 | Whether you hold their data, and a copy of it |
| Correction | 34 to 37 | Fix data that is inaccurate, incomplete, misleading or out of date |
| Withdraw consent | 38 | Stop processing data they had agreed to |
| Prevent damage or distress | 42 | Stop processing likely to cause them substantial damage or distress |
| Stop direct marketing | 43 | Cease, or never begin, marketing messages aimed at them |
| Data portability | 43A (from 1 June 2025) | Send their data directly to another business they choose |
Source: ZenWeb summary of Act 709 Part IV and Act A1727, as at October 2026. Licence.
Section 7 also says your privacy notice must tell people they can request access and correction, and how to contact you. This guide covers how to answer those requests; for the full list of PDPA duties in one place, use our PDPA compliance checklist for Malaysian marketers. Customer data you feed into AI tools is still covered; see AI and PDPA data privacy rules.
Quick Answer: Not as a stand-alone right. Unlike Europe’s GDPR, the PDPA has no general “right to erasure”. But a PDPA data deletion request usually works anyway, because it is also a consent withdrawal or marketing opt-out. The Retention Principle then requires deletion once you no longer need the data.
Treat every “please delete my data” message as carrying up to three legal effects at once:
So in practice, a deletion request for marketing data usually ends in deletion, but you may keep what another law requires, such as invoices kept for tax. Our guide to how long you can keep leads under PDPA covers that split. A WhatsApp “STOP” reply counts too; see consent rules for WhatsApp broadcasts.
Quick Answer: 21 days from receiving a written access or correction request. If you cannot finish, you must tell the person in writing before day 21, explain why, and do what you can. Everything must be done within 14 more days, so day 35 is the hard limit. Refusals also need written reasons within 21 days.
These deadlines come from sections 31, 33, 35 and 37 of Act 709. Section 30 also lets you charge a prescribed fee for access, capped by the Personal Data Protection (Fees) Regulations 2013. Many SMEs waive it, since chasing a small fee costs more than it brings in.
| Day | What must happen | Legal basis |
|---|---|---|
| 0 | Written request received; the clock starts | Sections 31(1), 35(1) |
| 1 to 3 | Acknowledge and verify identity (good practice) | Sections 32(1)(a), 36(1)(a) |
| By 21 | Comply in full, or send written refusal with reasons | Sections 31(1), 33, 35(1), 37 |
| By 21 (if late) | Written notice of delay with reasons, plus partial compliance | Sections 31(2), 35(2) |
| By 35 | Full compliance, no further extension | Sections 31(3), 35(3) |
Source: ZenWeb summary of Act 709 sections 31 to 37, as at October 2026. Days 1 to 3 are suggested practice, not a legal deadline. Licence.
If you corrected data that you shared with a third party in the previous 12 months, section 35 also asks you to send them the corrected copy where practicable. Someone needs to own the deadline; larger data users may need a formal data protection officer in Malaysia. For “send my data to another company” requests, see data portability under PDPA.
Quick Answer: Only on the grounds listed in section 32. The common ones are being unable to verify who is asking, lacking the detail to find the data, disproportionate effort, or exposing someone else’s data. Even then, give what you can and send written reasons within 21 days.
Refusal grounds are narrow. The table matches each one to a situation marketing teams actually meet.
| Ground | Marketing example | Suggested response |
|---|---|---|
| Identity not verified, s32(1)(a) | Request from an email that is not on file | Ask them to confirm from the registered email or phone |
| Cannot locate data, s32(1)(b) | “Delete everything” with no name, phone or email | Ask which contact details they used |
| Disproportionate burden, s32(1)(c) | Years of raw web server logs | Supply CRM and form data; explain the rest |
| Other people’s data, s32(1)(d) | Group chat or shared referral records | Redact other names and numbers, then send |
| Confidential commercial information, s32(1)(g) | Internal lead score formula | Give the data, withhold the model |
Source: ZenWeb mapping of Act 709 section 32 to common SME marketing cases, as at October 2026. Examples are illustrative; confirm any refusal with a lawyer. Licence.
Identity checks matter most. Sending a stranger someone’s purchase history could itself be a personal data breach; our guide to data breach notification in Malaysia explains what follows. If you sent hashed customer lists to an ad platform, note that in your reply; see Meta Conversions API and PDPA for how that data flows.
Need a request channel on your website?
We add a simple data request form, identity check and CRM ticket to your site, so every request is logged with its 21-day deadline. See what your contact form PDPA notice should say →
Quick Answer: In more places than most owners expect: the CRM, lead ad exports, email tools, WhatsApp phones, ad audience lists, website form entries and sometimes an agency’s files. A request is only complete when every copy is found, which is why scattered data makes each request slow and risky.
Here is a worked example. A home renovation company in Shah Alam receives a PDPA data deletion request from a past lead. The search finds the person in:
If an agency holds the files, the contract should make it act on your instructions; see your agency’s data processor duties. Keep admin access to your own ad accounts too, because a restricted Business Manager can lock you out of lead data you must delete.
| Data setup | Staff hours | Relative effort |
|---|---|---|
| Scattered: exports, inboxes, phones | 8 | |
| CRM, but manual copies remain | 4 | |
| Single CRM fed directly by forms and ads | 1 |
Source: Illustrative scenario by ZenWeb; modelled estimates, not client data or a benchmark. As at October 2026. Licence.
Never refill a cleaned list with bought data; our guide to buying lead lists under PDPA explains why. Website testing tools also store visitor data, so include them when you map systems; our CRO process guide lists the tools a typical test uses.
Quick Answer: Log the request, verify identity, stop marketing at once, find every copy, decide what must legally stay, delete or correct the rest, and reply in writing within 21 days. The same steps work for access and correction requests, with the copy or correction replacing the deletion step.
Use this as your practical checklist for every PDPA data deletion request:
Member and points databases need extra care because customers may lose their rewards; see loyalty programme data under PDPA. Your privacy notice should explain how to make a request, in both languages; see our guide to the website privacy policy under PDPA.
Data requests are rare for most SMEs, which is exactly why they go wrong when one arrives. As at October 2026, check that you have:
Our digital marketing services team builds forms, CRM flows and tracking that make each PDPA data deletion request a quick, logged task. Your lawyer confirms the legal calls.
Not as a general right. But withdrawing consent, opting out of direct marketing and the Retention Principle together usually mean you must stop using and delete marketing data once asked.
21 days from receiving the written request. If you cannot finish, tell the person in writing before day 21 and complete it within 14 more days.
Section 30 allows a prescribed fee, capped by the Personal Data Protection (Fees) Regulations 2013. Many SMEs choose not to charge.
Access and correction requests, consent withdrawals and marketing opt-outs are made in writing under the Act. Email, web forms and written chat messages are commonly treated as writing, so log them.
No. ZenWeb builds the forms, CRM pipelines and suppression flows that make requests easy to handle. Legal decisions on refusals or retention should be confirmed with a licensed lawyer.
Cite this page: ZenWeb (2026). Data Access and Deletion Requests: PDPA Steps for SMEs. https://zenweb.my/blog/data-deletion-request-pdpa/
You may quote our data with this credit and a link. See our Terms of Use.
Answer every data request in minutes, not weeks
Talk to ZenWeb about request forms, one-CRM lead flows and same-day marketing suppression. We handle the marketing systems; your lawyer confirms the legal calls.
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.