
Most Malaysian SMEs hand customer data to outside firms every week. The agency uploads your customer list to Google Ads, the web developer can see every website enquiry, and the WhatsApp vendor stores every chat. Until 2025, the PDPA mostly left these firms to your contract.
That changed with the 2024 amendments. This guide explains PDPA data processor duties for your agency, what stays your job, and which contract clauses to ask for. It comes from ZenWeb, a Malaysian Google Partner agency with 500+ clients. We act as a processor for our own clients, so we see both sides. Rules are stated as at October 2026.
This post is general information, not legal or tax advice. Please confirm how the PDPA applies to your business with a licensed lawyer.
Choosing an agency that takes data seriously?
Ask how they store your leads, who can log in and what happens to your data when the contract ends. See how ZenWeb works as your digital marketing agency →
For background on what the 2024 amendments changed overall, this recorded webinar from a Malaysian university research centre is a useful primer before we get to agencies.
Source video: Centre of Research for Cyber Security and Network on YouTube. Recorded in August 2024, before the amendments came into force; check dates against the official sources below.
Quick Answer: A data processor is any person, other than your own employee, who processes personal data solely on your behalf and not for their own purposes. Your business decides why the data is collected, so you are the data controller. An agency running your ads with your customer list is usually your processor.
The definition sits in section 4 of the Personal Data Protection Act 2010 (Act 709). The amendments renamed the “data user” as the “data controller”, but the test is the same. Ask two questions:
Your staff are not processors; they act as part of your business. That is why the PDPA compliance checklist for Malaysian marketers treats staff training and vendor contracts as separate tasks.
Quick Answer: The Personal Data Protection (Amendment) Act 2024 came into force in three phases. From 1 April 2025, processors must comply with the Security Principle directly and face their own penalties. From 1 June 2025, processors that meet set thresholds must also appoint a data protection officer.
Before 2025, the law told the data user to make sure its processor gave security guarantees, so a leaking processor was mainly a contract problem. Act A1727 moved part of that duty onto the processor itself. The dates below follow the Minister’s commencement order.
| Date in force | Main changes | Impact on processors |
|---|---|---|
| 1 January 2025 | Administrative and saving provisions | No new duties |
| 1 April 2025 | “Data controller” term, biometric data as sensitive, higher penalties, new cross-border rules | Must comply with the Security Principle (s.5(1A), s.9); fine up to RM1,000,000, jail up to 3 years, or both |
| 1 June 2025 | Data protection officer, breach notification, data portability | Must appoint a DPO if thresholds are met (s.12A(2)); must alert the controller of breaches under contract |
Source: Act A1727 and the commencement order, compiled by ZenWeb. As at October 2026. Licence.
Notice what did not change: breach notification to the Commissioner stays with you, the controller. The processor’s job is to tell you fast. Our guide to data breach notification in Malaysia covers your side of that process.
Quick Answer: For normal client work, an agency is a data processor: it runs your ads, builds your forms and manages your CRM under your instructions. It becomes a controller when it uses the data for its own purposes, such as collecting leads on its own pages and selling them, or reusing your list elsewhere.
Most SMEs work with several outside firms at once. Here is how common marketing setups usually split.
| Setup | Likely role | Why |
|---|---|---|
| Agency running your Google or Meta ads with your customer list | Processor | Uses your data only for your campaigns |
| Web developer hosting your site and form entries | Processor | Stores enquiries on your behalf |
| CRM, email or WhatsApp API vendor | Usually processor | Depends on its terms; check for its own uses |
| Lead vendor collecting leads on its own pages | Controller | Decides the purpose and sells the data |
| Agency reusing your leads for its own case study or tool | Controller for that use | Own purpose; needs your approval and a legal basis |
| Your in-house marketing staff | Neither | Employees act as part of the controller |
Source: ZenWeb reading of the “data processor” definition in s.4 of Act 709. Roles depend on the facts and your contracts. As at October 2026. Licence.
The lead vendor row matters most. Bought leads come from someone else’s controller relationship, which is why buying lead lists under PDPA carries more risk than hiring an agency to run your own campaigns. If your CRM vendor stores data overseas, the cross-border rules also apply; see using overseas CRMs under PDPA.
Quick Answer: Under amended section 9, a processor must give sufficient guarantees on its technical and organisational security measures and take reasonable steps to make sure those measures are followed. It must appoint a DPO if it meets the thresholds, and your contract should require it to alert you quickly after a breach.
For a marketing agency, the PDPA data processor duties translate into four practical jobs:
One grey area: the DPO guideline treats tracking and profiling people for behavioural advertising as regular and systematic monitoring. As at October 2026, the guideline does not say how this applies to an agency that only manages client ad accounts, so a careful agency records its reasoning. Our guide on who must appoint a data protection officer explains the thresholds in full.
Quick Answer: It depends on the service. SEO and content work rarely touch customer records. Paid ads involve uploaded customer lists and lead forms. Website hosting, CRM and WhatsApp automation give the provider direct access to every enquiry, so those contracts deserve the strictest processor terms.
This illustrative scenario scores typical personal-data exposure by service type for a Malaysian SME, so you can focus your contract checks where the risk is highest.
| Service | Exposure score | Main data involved |
|---|---|---|
| SEO and content | 2 | Analytics access, rarely named records |
| Google Ads | 6 | Customer Match lists, lead form extensions |
| Meta Ads | 7 | Lead Ads, Custom Audiences, Conversions API |
| Website build and hosting | 8 | Form entries, orders, database backups |
| CRM and WhatsApp automation | 9 | Full contact records, chat history, notes |
Source: Illustrative scenario by ZenWeb. Scores are judgement-based assumptions to show relative exposure, not measured data or a legal standard. As at October 2026. Licence.
Meta setups are covered in Meta Conversions API and PDPA and Facebook lead ads and PDPA. WhatsApp vendors hold chat history and opt-outs, so read WhatsApp marketing and PDPA too. Member databases built by an agency raise similar issues; see loyalty programme data under PDPA.
Is your website the weakest link?
We build sites with secured form storage, named admin access and PDPA-friendly enquiry forms from day one. Explore our web design service →
Quick Answer: A short data processing clause or schedule should cover eight points: instructions only, security measures, breach alerts, sub-processors and overseas tools, DPO contact, help with customer requests, return or deletion at exit, and evidence on request. Each one links to a specific PDPA rule or guideline.
Many agency contracts cover fees and lock-in but say nothing about personal data. Use this list with our guide to marketing agency contract terms.
| Stage | Clause | What it covers | PDPA source |
|---|---|---|---|
| Setup | Instructions only | Use client data only for the agreed services | s.4 definition |
| Security measures | Two-factor login, named access, secure file storage | s.9(2) | |
| Sub-processors and overseas tools | List tools used and where data is stored | s.129 | |
| During the contract | Breach alert | Notify the client promptly, with a set time, and assist | Breach guideline para 12.2 |
| DPO contact | Name the agency’s DPO if it meets the thresholds | s.12A(2) | |
| Customer requests | Help with access, correction, deletion and portability requests | Access rights, s.43A | |
| Exit | Return or deletion | Hand back or delete client data and confirm in writing | s.10 Retention |
| Evidence on request | Show proof of the security measures when asked | Supports your s.9(1) duty |
Source: ZenWeb mapping of Act 709 as amended and the Commissioner’s breach notification guideline. Not a template contract; have a lawyer draft the final wording. As at October 2026. Licence.
The exit clauses connect to account ownership. When you change Google Ads agency or change Facebook ads agency, ask the old agency to confirm that copies of customer lists are deleted. Keeping the accounts themselves is a separate step, covered in agency account ownership. For deletion requests from customers, see data access and deletion requests and data portability under PDPA.
Quick Answer: If your agency leaks your leads, you still notify the Commissioner. The breach guideline says your 72-hour clock starts when the processor tells you, or when you get clear evidence yourself, whichever is earlier. A slow agency alert eats into time you never get back.
Imagine an agency’s shared website login is stolen, exposing 600 enquiry form entries. This is an illustrative scenario, but the steps follow the Commissioner’s breach notification guideline:
The agency may also have breached its own data processor duty under the PDPA, which can now lead to action against it directly. A good processor contract rules out shared logins.
Quick Answer: List your processors, label each role, sign data processing terms, own the accounts, limit what you share, update your notice, test the breach alert and close out data at exit. Most SMEs can complete a first pass in two to three weeks, with contract changes taking longest.
Run this review for every agency, developer and software vendor that touches customer data:
For the notice wording, see our guide to contact form PDPA notice wording. Retention limits for old leads are in lead data retention under PDPA. If an agency uses AI tools on your data, read AI and PDPA for Malaysian marketers.
Since 2025, data processor PDPA duties make your agency responsible in its own right, not just a name in your contract. As at October 2026, the split looks like this:
Where a point is still unclear, such as how the DPO monitoring test applies to agencies, take the careful reading until the Commissioner says more. To work with an agency that puts this in writing, talk to our digital marketing agency team.
Usually, yes. When an agency handles your customer data only to run your campaigns, website or CRM, it is a data processor. It becomes a controller for any use it makes of the data for its own purposes.
The direct Security Principle duty for processors started on 1 April 2025. The data protection officer requirement, which also covers processors that meet the thresholds, started on 1 June 2025.
No. Under the Commissioner’s guideline, section 12B notification applies to the data controller. The agency must alert you promptly under your contract, and you then notify within 72 hours.
Under the amended Act, a fine of up to RM1,000,000, imprisonment of up to three years, or both.
We can agree data processing terms covering security, access, breach alerts and deletion at exit. We handle the marketing and website side; please have your lawyer confirm the final legal wording.
Cite this page: ZenWeb (2026). Your Agency and PDPA: Data Processor Duties Since 2025. https://zenweb.my/blog/agency-data-processor-pdpa/
You may quote our data with this credit and a link. See our Terms of Use.
Work with an agency that protects your customer data
Talk to ZenWeb about campaigns, websites and lead forms run with named access, secure storage and clear exit terms. We handle the marketing; your lawyer confirms the legal wording.
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.