ZenWeb - Blog - Your Agency and PDPA: Data Processor Duties Since 2025

Your Agency and PDPA: Data Processor Duties Since 2025

November 2, 2026

Share this post:

Your Agency and PDPA: Data Processor Duties Since 2025
TL;DR: When a marketing agency, web developer or CRM vendor handles your customers’ data on your behalf, it is a data processor under the PDPA. Since 1 April 2025, processors must follow the Security Principle themselves, with fines up to RM1 million. You are still the data controller, so put security, breach alerts, overseas tools and data return in a written contract.

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.

Key Amendments to Malaysia's Personal Data Protection Act 2010

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.

1. What Is a Data Processor Under the PDPA?

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:

  • Who decides the purpose? If you decide why the data is collected and used, you are the controller.
  • Does the outside firm use it for itself? If the agency only follows your instructions, it is a processor. If it reuses your leads for its own list, case study or product, it acts as a controller for that use.

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.

Key takeaway: The label depends on what the firm does with the data, not on its job title. The same agency can be your processor for ads and a controller for its own mailing list.

2. What Changed for Data Processors in 2025?

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.

PDPA amendment timeline and what each phase means for data processors, as at October 2026
Time-series table listing the three commencement dates of Malaysia’s Personal Data Protection (Amendment) Act 2024, the main changes in each phase, and the impact on data processors such as marketing agencies.
Date in forceMain changesImpact on processors
1 January 2025Administrative and saving provisionsNo new duties
1 April 2025“Data controller” term, biometric data as sensitive, higher penalties, new cross-border rulesMust 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 2025Data protection officer, breach notification, data portabilityMust 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.

Key takeaway: Since April 2025 a careless agency can be fined in its own name. That helps you, but it does not move your own duties onto the agency.

3. Is Your Marketing Agency a Data Processor or a Controller?

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.

Likely PDPA role of common marketing service providers
Data table showing the likely PDPA role, data processor or data controller, of six common marketing service provider setups used by Malaysian SMEs, and the reason for each.
SetupLikely roleWhy
Agency running your Google or Meta ads with your customer listProcessorUses your data only for your campaigns
Web developer hosting your site and form entriesProcessorStores enquiries on your behalf
CRM, email or WhatsApp API vendorUsually processorDepends on its terms; check for its own uses
Lead vendor collecting leads on its own pagesControllerDecides the purpose and sells the data
Agency reusing your leads for its own case study or toolController for that useOwn purpose; needs your approval and a legal basis
Your in-house marketing staffNeitherEmployees 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.

Key takeaway: List every outside firm that touches customer data and label each one. Any firm that also uses the data for itself needs a closer look.

4. What Must an Agency Do as a Data Processor?

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:

  • Secure the accounts. Two-factor login on ad, CRM and website accounts, named user access instead of shared passwords, and access removed when staff leave.
  • Secure the files. Customer lists for Customer Match or Custom Audiences should not sit in personal email or open shared folders.
  • Appoint a DPO when required. The DPO guideline applies the same thresholds to processors: over 20,000 data subjects, over 10,000 for sensitive or financial data, or regular and systematic monitoring.
  • Report breaches to you. The breach notification guideline says section 12B does not apply to processors directly, but controllers must require them by contract to notify promptly and help.

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.

Key takeaway: Ask any agency to describe its security in plain terms: who can log in, how files are stored, and how fast it will call you after an incident. Vague answers are a warning sign.

5. How Much Personal Data Does Your Agency Actually Touch?

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.

Illustrative scenario: personal-data exposure by marketing service (score out of 10)
Bar chart table scoring, in an illustrative scenario, how much customer personal data five types of marketing service provider typically handle, with the main data involved.
ServiceExposure scoreMain data involved
SEO and content2

Analytics access, rarely named records
Google Ads6

Customer Match lists, lead form extensions
Meta Ads7

Lead Ads, Custom Audiences, Conversions API
Website build and hosting8

Form entries, orders, database backups
CRM and WhatsApp automation9

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.

Key takeaway: Spend your review time on the providers that hold full customer records. A website host or CRM vendor with weak terms is a bigger risk than an SEO consultant.

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 →


6. Which Clauses Should Your Agency Contract Include?

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.

Data processing clauses for a Malaysian agency contract, grouped by stage
Grouped table listing eight data processing clauses for a marketing agency contract, grouped into setup, during the contract and exit, with what each clause should say and the PDPA source it supports.
StageClauseWhat it coversPDPA source
SetupInstructions onlyUse client data only for the agreed servicess.4 definition
Security measuresTwo-factor login, named access, secure file storages.9(2)
Sub-processors and overseas toolsList tools used and where data is storeds.129
During the contractBreach alertNotify the client promptly, with a set time, and assistBreach guideline para 12.2
DPO contactName the agency’s DPO if it meets the thresholdss.12A(2)
Customer requestsHelp with access, correction, deletion and portability requestsAccess rights, s.43A
ExitReturn or deletionHand back or delete client data and confirm in writings.10 Retention
Evidence on requestShow proof of the security measures when askedSupports 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.

Key takeaway: One page of data processing terms is enough for most SME agency contracts. The breach alert time and the exit deletion clause are the two you will be glad you had.

7. Worked Example: A Leak at Your Agency and the 72-Hour Clock

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:

  1. Agency finds the leak. It contains it by changing passwords and removing the stolen login, then alerts you the same day.
  2. Your clock starts. The 72 hours run from the agency’s alert, or from your own clear evidence if that came first.
  3. You assess the harm. Names and phone numbers carry less risk than identity card numbers or financial details.
  4. You notify the Commissioner. As soon as practicable and no later than 72 hours.
  5. You notify affected people if needed. Where there is significant harm, within 7 days of notifying the Commissioner.
  6. You record it. Keep the breach in a register for at least two years, even if it did not need notifying.

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.

Key takeaway: Write a breach alert deadline into the contract, such as 24 hours. Without one, “promptly” can mean whatever the agency decides on the day.

8. Data Processor PDPA Checklist for SMEs

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:

  1. List your processors. Agencies, web host, CRM, email and WhatsApp tools, call centres.
  2. Label each role. Processor, controller, or both, using the table in section 3.
  3. Sign data processing terms. Cover the eight clauses above, starting with high-exposure providers.
  4. Own the accounts. Keep ad, website and CRM accounts in your company’s name and grant agency access through user roles.
  5. Share less. Give only the fields each provider needs, and stop emailing full customer lists.
  6. Update your notice. Your privacy notice should name the classes of third parties, such as service providers.
  7. Test the breach alert. Confirm who calls whom, and record contact details for both sides.
  8. Close out at exit. Remove access and get written confirmation that copies are deleted.

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.

Key takeaway: Start with the two or three providers that hold full customer records. Getting those contracts right covers most of your real risk.

9. Conclusion: Shared Work, Separate Duties

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:

  • You, the controller, own the notice, the purpose, retention, customer requests and breach notification.
  • Your agency, the processor, owns its security, a DPO where required, and a fast breach alert to you.
  • The contract joins the two, covering instructions, overseas tools, help with requests and deletion at exit.

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.


10. Frequently Asked Questions

1. Is a digital marketing agency a data processor under the PDPA?

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.

2. When did data processor duties start in Malaysia?

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.

3. Does the agency report a data breach to the Commissioner?

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.

4. What is the penalty for a data processor that breaks the Security Principle?

Under the amended Act, a fine of up to RM1,000,000, imprisonment of up to three years, or both.

5. Does ZenWeb sign data processing terms with clients?

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.

Book a free consultation →

Table of Contents
Table of Contents

Get A Free Proposal

Complete the form and our team will contact you to discuss your goals. Let’s grow your business.