Yuki Chong Mei Yoke (Partner)


5 minutes


ARC News   •   26 September, 2025

The Amendment Act is strict, but compliance is not out of reach. By taking practical, structured steps, corporates can turn obligations into opportunities to build trust. Below are six practical steps, with legal context and real-world illustrations.

The Amendment Act makes the appointment of a Data Protection Officer (DPO) mandatory for both data controllers and processors. The DPO is not a token appointment; regulators expect a named individual with sufficient authority, independence, and resources.

Example:

A listed telecommunications company designates a senior compliance manager as DPO. Her responsibilities include auditing marketing campaigns for consent compliance, vetting cross-border data transfer agreements, and reporting annually to the board. By documenting her role and notifying the Commissioner, the company shows proactive compliance.

Under the General Code of Practice, data users must disclose retention periods, disposal methods, and third-party disclosures. Policies must be accurate, accessible, and up to date.

Example:

An insurance company updates its privacy notice to state that claims data will be retained for seven years in line with Bank Negara requirements, and disposed of via certified shredding thereafter. By explicitly stating this, the company demonstrates compliance with both sectoral regulations and PDPA obligations.

The Amendment Act now makes data processors directly liable for breaches of the Security Principle. However, corporates remain primarily accountable as data controllers. This makes robust contractual safeguards essential.

Example:

A bank amends its outsourcing agreements with IT vendors to include:

• PDPA-compliant data protection clauses,

• audit rights for the bank,

• 24-hour breach notification requirements, and

• indemnities for processor negligence.

This ensures compliance and gives the bank recourse if regulators investigate.

Mandatory breach notification requires corporates to notify the Commissioner “as soon as practicable” and affected data subjects “without unnecessary delay.” Delays can trigger penalties, even if the breach was beyond the company’s control.

Example:

A regional healthcare group creates a breach response playbook:

• The IT team must report suspected intrusions within one hour.

• The DPO convenes a crisis team (legal, IT, PR).

• A regulator notification template is pre-drafted.

When a ransomware attack hits, the group notifies within 36 hours, mitigating penalties and demonstrating due diligence.

With the removal of the whitelist system, corporates must now assess whether recipient countries have laws “substantially similar” to the PDPA or implement equivalent safeguards (e.g., contractual clauses, binding corporate rules).

Example:

A Malaysian fintech hosting data in the U.S. conducts a legal adequacy assessment. It then enters into model contractual clauses with its cloud provider, requiring: encryption of data, restrictions on onward transfer, and liability provisions. The assessment and contracts are documented for audit purposes.

The definition of “sensitive personal data” now includes biometric identifiers. Processing such data requires explicit consent and heightened security measures.

Example:

A corporate office introduces biometric entry gates. Employees sign a consent form that clearly states the purpose (access control), retention period (data deleted when employment ends), and security measures (encryption, restricted HR access only). This prevents allegations of unlawful processing.


Key Takeaway

Compliance is not just about avoiding fines. Done properly, it strengthens governance, reassures stakeholders, and creates competitive advantage in a data-driven economy.

This article concludes our three-part series on the PDPA Amendment Act 2024. If you haven’t yet, do check out:

– Part 1: Key Changes Corporates Must Know PDPA: Part 1

– Part 2: Consequences of Non-Compliance PDPA: Part 2

Together, the series gives you the full picture: what changed, why it matters, and how to respond

Disclaimer: Every attempt to ensure the accuracy and reliability of the information provided in this publication has been made. This publication does not constitute legal advice and is not intended to be used as a substitute for specific legal advice or opinions. Please contact the authors for a specific technical or legal advice on the information provided and related topics.