Ascentis Malaysia

Malaysia > PDPA and Loyalty Programmes

Building a PDPA-Compliant Loyalty Program in Malaysia

A loyalty programme can process names, contact details, identifiers, transaction histories, preferences, locations and engagement behaviour at significant scale. In Malaysia, those activities should be designed around the Personal Data Protection Act 2010 (Act 709), the 2024 amendments and the Commissioner's current circulars and guidelines.

Draft — legal/DPO review pending. Last editorial review: 10 September 2026. Legal reviewer and legal review date: pending confirmation.

This guide explains practical questions for business, marketing, technology and procurement teams. It is general information, not legal advice. Your organisation remains responsible for compliance and should obtain advice from its Data Protection Officer, legal counsel and security team.

What changed under Malaysia’s PDPA amendments?

The Personal Data Protection (Amendment) Act 2024 introduced changes in phases during 2025. Among the changes relevant to loyalty and CRM programmes are stronger accountability for data processors under the Security Principle, mandatory Data Protection Officer requirements for organisations that meet the Commissioner’s criteria, data breach notification duties, and updated cross-border transfer considerations.

The Amendment Act also increased the maximum penalty for contravening the Personal Data Protection Principles from RM300,000 or two years’ imprisonment to RM1,000,000 or three years’ imprisonment, or both. Penalties depend on the specific offence and facts; obtain legal advice rather than using a headline figure as a complete risk assessment.

Sources: Act A1727 and commencement Gazette.

The seven Personal Data Protection Principles

Act 709 is built around seven principles for handling personal data. A loyalty programme should translate each principle into product requirements and operating procedures.

General Principle

Process personal data for a lawful purpose connected to the programme and avoid collecting more than is necessary for that purpose.

Notice and Choice Principle

Provide a clear personal data protection notice explaining what is collected, why, how it is used, who receives it and how people can exercise their rights.

Disclosure Principle

Do not disclose personal data beyond the stated purpose or approved class of third parties without an applicable legal basis or consent where required.

Security Principle

Apply practical safeguards against loss, misuse, unauthorised access, disclosure, alteration or destruction. Data processors now have direct obligations under the Security Principle.

Retention Principle

Keep personal data only for as long as needed for the purpose, legal requirements and defensible business needs, then delete or anonymise it securely.

Data Integrity Principle

Take reasonable steps to keep the personal data used by the programme accurate, complete, not misleading and up to date.

Access Principle

Provide processes for data subjects to request access to and correction of their personal data, subject to the Act’s conditions and exceptions.

When is a Data Protection Officer required?

The Commissioner’s current guidance states that a data controller or data processor must appoint one or more DPOs if its processing meets any of the following conditions:

  • Personal data relating to more than 20,000 data subjects.
  • Sensitive personal data, including financial information, relating to more than 10,000 data subjects.
  • Activities that require regular and systematic monitoring of personal data, such as online user behaviour tracking.

A large enterprise loyalty database may meet one or more criteria, but the assessment must be based on the organisation’s actual processing. Where a DPO is required, the Commissioner should be notified within 21 days of appointment through the Personal Data Protection System. The organisation remains responsible for compliance; appointing a DPO does not transfer that responsibility to the individual.

Source: DPO Guideline.

What are the data breach notification timeframes?

The Commissioner’s Data Breach Notification Guideline states that a qualifying breach should be notified to the Commissioner as soon as practicable and no later than 72 hours from the occurrence of the personal data breach. The Guideline explains when the clock begins for different discovery scenarios.

Where a breach causes or is likely to cause significant harm, affected data subjects must be notified without unnecessary delay and no later than seven days after the initial notification to the Commissioner. A loyalty programme therefore needs an incident process that can detect, investigate, escalate, assess harm and communicate quickly.

Source: Data Breach Notification Guideline. Legal/DPO review must confirm the notification trigger and clock-start scenarios before publication.

Cross-border transfers require a documented basis

Section 129 regulates transfers of personal data out of Malaysia. The Commissioner’s 2025 guideline explains the conditions that may support a transfer, including a receiving jurisdiction with substantially similar law or an adequate level of protection, and other statutory conditions such as consent, contractual necessity or reasonable precautions and due diligence where applicable.

The data controller should inform data subjects about the transfer through the personal data protection notice or another written notice, use appropriate processor or third-party contracts, secure the transfer and keep records showing the receiver, country, data type, purpose and basis for the transfer. A Transfer Impact Assessment may be relevant depending on the basis used.

Source: Cross-Border Transfer Guideline.

A ten-step PDPA checklist for loyalty programmes

1. Define roles and purposes

Identify the data controller, data processors and other recipients. Document the purpose for every data field and processing activity.

2. Map data flows

Record where data is collected, stored, accessed, transferred, enriched and deleted across POS, eCommerce, apps, CRM, analytics, vendors and support tools.

3. Minimise collection

Collect only what is needed for the stated programme and avoid making optional profile details mandatory without a clear purpose.

4. Design notice and choice

Present an understandable privacy notice at or before collection. Separate programme terms from privacy information and make direct-marketing choices clear.

5. Manage preferences and rights

Maintain reliable processes for consent or preferences where applicable, withdrawal, direct-marketing objections, access and correction requests.

6. Set permissions and security

Use role-based access, strong authentication, secure integrations, logging, monitoring and suitable protection for data in transit and at rest, based on verified product capabilities.

7. Govern processors and vendors

Assess vendors, define security and processing duties in contracts, limit access and maintain oversight through the service lifecycle.

8. Define retention and deletion

Set retention periods by data category and purpose. Include deletion, anonymisation, backups and end-of-contract handling.

9. Prepare for incidents

Create a breach playbook with owners, contact lists, evidence preservation, 72-hour assessment workflow and affected-person communication process.

10. Review cross-border transfers

Identify every receiving country and recipient, document the applicable Section 129 basis, notices, contracts, safeguards and records.

What to ask a loyalty platform vendor

Which party acts as data controller and which acts as data processor for each service?

Where is production data, backup data and support-access data hosted or accessed?

What encryption, authentication, access control, logging and monitoring capabilities apply to our proposed configuration?

How are data subject access, correction, preference, export and deletion requests supported?

How are retention rules, backups and end-of-contract deletion handled?

Which subprocessors are involved, and how are changes communicated?

What incident notification, investigation and evidence support will be provided?

What independent certifications or assurance reports are current, and what systems and locations are in scope?

How are integrations authenticated, limited, monitored and recovered after failure?

What documentation will we receive for our risk assessment, procurement and DPO review?

How Ascentis can support the technology discussion

Ascentis can work with business, technology, security and privacy stakeholders to map the proposed customer journeys, data flows, integrations and platform configuration. Ascentis states that it holds ISO/IEC 27001:2022 certification and SOC 2 Type 2 compliance; request the current scope and relevant assurance material during procurement.

The selected technology and certification do not replace your organisation’s legal responsibilities. Compliance depends on the complete programme, including purposes, notices, data collection, integrations, people, procedures, contracts, security, retention and incident response.

Bring your DPO, security, legal and technology stakeholders so the proposed data flows and platform controls can be reviewed together.

Review before publication

This draft requires Malaysian legal counsel or DPO, security, product and marketing approval. Confirm the named author and legal reviewer, update the legal review date after sign-off, and recheck official guidance at least every six months.

The regulator also lists guidance on Data Protection Impact Assessment, Data Protection by Design, and Automated Decision-Making and Profiling. The legal/DPO reviewer should assess their relevance and any additions needed to this guide before publication.

Frequently asked questions

Not automatically. A DPO is required when the data controller or data processor meets at least one of the Commissioner’s criteria, including the stated data-subject thresholds or regular and systematic monitoring. Assess the actual processing with qualified advice.

Act 709 requirements depend on the processing activity and applicable provisions. Do not assume one consent covers every purpose. Provide proper notice, limit processing to stated purposes and obtain legal advice for the programme design.

Cross-border transfers may be possible if the requirements of Section 129 and current guidance are met. Identify the recipient and country, select and document the applicable basis, notify data subjects as required, apply safeguards and maintain records.

No. These frameworks can provide security and control assurance within their scope, but PDPA compliance depends on the organisation’s complete legal, technical and operational processing model.

The current Commissioner guideline states that a qualifying breach should be notified to the Commissioner as soon as practicable and no later than 72 hours from occurrence. Where significant harm is caused or likely, affected data subjects must be notified without unnecessary delay and within the guideline’s stated timeframe.

Request a PDPA-focused solution workshop with Ascentis Malaysia.