ZenWeb - Blog - Loyalty Programme Data Under PDPA: Points, Profiles, Consent

Loyalty Programme Data Under PDPA: Points, Profiles, Consent

November 3, 2026

Share this post:

Loyalty Programme Data Under PDPA: Points, Profiles, Consent
TL;DR: A loyalty programme is a personal data machine: names, phone numbers, birthdays and every purchase a member makes. Under the PDPA you need a bilingual notice at sign-up, consent that matches each purpose, a separate opt-in for promotions, and a plan to delete dormant accounts. Using purchase history to profile members for targeted offers is where the extra risk starts, including a possible duty to appoint a DPO.

Points cards, member apps and “sign up for 10% off” forms are everywhere in Malaysia, from cafés in Petaling Jaya to online stores shipping nationwide. They are one of the best ways to win repeat sales. They are also one of the biggest stores of customer data an SME will ever build.

This guide explains loyalty programme PDPA rules as at October 2026: what data you collect, what consent you need, where profiling crosses a line, and how long to keep member records. It comes from ZenWeb, a Malaysian Google Partner agency with 500+ clients. We build member sign-up pages, CRM links and marketing; we are not a law firm. For loyalty tactics rather than data rules, read our guide to loyalty marketing that keeps customers coming back.

This post is general information, not legal or tax advice. Please confirm how the rules apply to your business with a licensed lawyer before you act.

Building a member portal or points app?

We build member sign-up flows with bilingual notices, separate marketing opt-ins and secure member logins from day one. See our membership website development →

Before the detail, this short legal podcast from a Malaysian law firm sets out what the 2024 PDPA amendments changed for businesses that hold customer data.

Understanding Malaysia's Personal Data Protection (Amendment) Act 2024

Source video: The Legal Insight Podcast on YouTube, published February 2025. It covers the amendments in general, not loyalty programmes specifically.

1. What Member Data Does a Loyalty Programme Collect?

Quick Answer: More than most owners realise. Beyond name and phone number, a typical programme holds birthdays, email, points balances, every receipt, store visits and redemption history. Once linked to a member ID, all of it is personal data under the PDPA, because it relates to a person you can identify.

Section 4 of the Personal Data Protection Act 2010 (Act 709) covers information that identifies a person directly or together with other data you hold. A purchase log means little alone. Tied to a phone number, it shows what someone buys, where and when. The inventory below is the starting point for every loyalty programme PDPA review.

Typical loyalty programme data and its PDPA status
Data table listing seven common types of loyalty programme data, how each is typically used, and its status under Malaysia’s Personal Data Protection Act.
Data typeTypical usePDPA status
Name, phone, emailMember ID, login, receiptsPersonal data
BirthdayBirthday rewardsPersonal data; ask only day and month if the year is not needed
Points and tierRewards, member statusPersonal data once tied to a member
Purchase historyPoints earning, personalised offersPersonal data; profiling raises extra duties
IC or passport numberIdentity checksPersonal data; usually excessive for a points card
Face scan or fingerprintCheck-in, app loginSensitive personal data (biometric) since 1 April 2025
Health or dietary notesProduct suggestionsMay be sensitive personal data; needs explicit consent

Source: ZenWeb classification based on section 4 of Act 709 and Act A1727, as at October 2026. A practical guide, not a legal ruling. Licence.

Section 6(3) adds a useful test: data must be “adequate but not excessive” for its purpose. An IC number for a coffee stamp card rarely passes. For the full rules on the riskier rows, see our guide to sensitive personal data in lead forms.

Key takeaway: List every field your sign-up form and POS capture, then delete the ones the programme does not truly need. Less data means less to protect, explain and delete later.

2. Does Joining a Loyalty Programme Count as Consent?

Quick Answer: Only for running the programme. Signing up covers what the member clearly expects: tracking points, sending statements, processing rewards. Promotional messages are direct marketing under section 43, so ask for a separate, unticked opt-in and let members refuse it without losing their points.

Section 7 requires a written notice in both Bahasa Malaysia and English when you first collect the data. It must state the purposes, the classes of third parties who receive the data, whether each field is compulsory, and how members can access or correct their records. The Personal Data Protection Regulations 2013 also expect consent to be recorded and kept.

Section 43(5) defines direct marketing as advertising or marketing material sent “by whatever means” to particular individuals. Birthday vouchers sent by SMS, WhatsApp or email count. In practice, three consents should stay apart:

  • Programme consent. Collecting and using data to run the membership. Covered by the sign-up notice.
  • Marketing consent. A separate checkbox, unticked by default, naming the channels you will use. Our WhatsApp marketing consent rules explain why channel matters.
  • Sharing consent. Needed before passing member data to partners outside the classes listed in your notice, such as a co-branded merchant.

Members can withdraw consent in writing at any time under section 38, and stop direct marketing under section 43. Your sign-up page wording should match the patterns in our contact form PDPA notice guide and Facebook lead ad consent wording. Notice wording itself is covered in the website privacy policy guide.

Pending change: the Commissioner’s Public Consultation Paper No. 4/2025 proposed clearer consent rules, reasonable checks when a parent or guardian consents, and DPO contact details in notices. As at October 2026 we could not find a gazetted version, so treat these as proposals, not law.

Key takeaway: Never make promotions a condition of earning points. One sign-up, two clear choices: join the programme, and separately, receive offers.

3. When Does Purchase Profiling Trigger a DPO Duty?

Quick Answer: When the programme moves from managing accounts to monitoring behaviour. The Commissioner’s DPO guideline says a loyalty programme may not count as “regular and systematic monitoring” if it only manages member accounts. Using purchase data to profile members and recommend offers is closer to the monitoring examples it gives.

The Guideline on the Appointment of Data Protection Officer, issued 25 February 2025, sets three triggers for appointing a DPO. You need one if you process personal data of more than 20,000 people, sensitive or financial data of more than 10,000, or carry out regular and systematic monitoring. It names loyalty programmes directly, and it treats a retail site that recommends products from searches and purchases as monitoring. The comparison below shows where most SME programmes sit.

Account-only vs profiling loyalty programmes, as at October 2026
Grouped comparison table contrasting an account-only loyalty programme with a profiling loyalty programme across five features, and how each relates to the DPO monitoring test.
FeatureAccount-only programmeProfiling programme
Purchase data useCalculate points onlySegment members by habits
OffersSame offer for every memberPersonalised by past purchases
Ad audiencesNoneMember lists uploaded to Meta or Google
Web and app trackingLogin onlyBrowsing tied to member ID
DPO monitoring testGuideline says may not applyCloser to the guideline’s monitoring examples

Source: ZenWeb comparison based on paragraph 4.3 of the Commissioner’s DPO Guideline (25 February 2025), as at October 2026. The guideline gives examples, not a fixed line; confirm your position with a lawyer. Licence.

Personalised pricing is the next line. The Commissioner’s Automated Decision-Making and Profiling Guideline, published in 2026, lists a decision that gives one person a lower price than another as an example of a “significant” effect. If software, not staff, decides which members get bigger discounts, read that guideline before launch.

Profiling also changes your notice. If purchase history drives offers, say so plainly. If you upload member lists to Google Ads Customer Match or a Meta custom audience, name ad platforms as a class of recipient. Sending purchase events server-side carries its own rules, set out in Meta Conversions API and PDPA. Who must appoint a DPO, and how, is covered in our DPO guide.

Key takeaway: A programme with 20,000+ members needs a DPO on headcount alone. Below that, profiling is the feature that can still pull you in, so decide on it deliberately.

4. Can You Share Member Data With Partners and Platforms?

Quick Answer: Only within what your notice disclosed, or with fresh consent. Section 8 limits disclosure to the original purpose and the classes of third parties you named. Coalition partners, ad platforms and overseas loyalty software each need to fit that notice, and selling member lists is never safe.

Most SME loyalty programmes run on someone else’s software, which means data leaves your hands on day one. Check each flow:

  • Loyalty and CRM vendors. They act as data processors. Since 1 April 2025, processors must meet the Security Principle directly, but you still need a contract with security terms. See data processor duties under PDPA.
  • Overseas hosting. Many platforms store data in Singapore or the US. The rules are in cross-border data transfer under PDPA.
  • Partner merchants. A café sharing members with a nearby gym needs those members’ consent, unless the notice already named such partners.
  • Bought or swapped lists. Adding outside contacts to your member base brings the problems in buying lead lists under PDPA.

AI tools add a newer flow. Pasting member exports into a chatbot to “find segments” is a disclosure too; our AI and PDPA guide explains the safer options.

Key takeaway: Map every system member data touches, then check each one against the third-party classes in your notice. Anything missing needs a notice update or fresh consent.

Want member offers that stay inside the rules?

We plan consent-based CRM, email and remarketing campaigns that use your member data the way your notice says you will. Explore our digital marketing services →


5. What Are the Penalties for Getting Member Data Wrong?

Quick Answer: The heaviest is up to RM1 million, three years’ jail, or both, for breaching the data protection principles, raised by the 2024 amendments. Separate offences cover failing to report a breach, processing sensitive data without explicit consent, and ignoring a member’s withdrawal of consent.

The maximum fines below come from Act 709 and the Personal Data Protection (Amendment) Act 2024 (Act A1727). Each offence also carries possible imprisonment.

Maximum PDPA fines relevant to loyalty programmes (RM)
Bar chart table showing the maximum fines in ringgit for six PDPA offences relevant to loyalty programmes, from RM1 million for breaching the principles to RM100,000 for ignoring a withdrawal of consent.
Offence (section)Max fine / jailRelative size
Breaching the principles (5(2))RM1,000,000 / 3 years
Processing without required registration (16(4))RM500,000 / 3 years
Not notifying the Commissioner of a breach (12B(3))RM250,000 / 2 years
Sensitive data without explicit consent (40(3))RM200,000 / 2 years
Ignoring a Commissioner order on direct marketing (43(4))RM200,000 / 2 years
Processing after consent is withdrawn (38(4))RM100,000 / 1 year

Source: Act 709 as amended by Act A1727, maximum penalties on conviction, as at October 2026. Licence.

Registration applies only to businesses in the 13 classes set by the Class of Data Users Order, so check whether your sector is listed. A breach of the member database also triggers the steps in data breach notification in Malaysia. Weak member logins are a common cause; our PDPA-ready web systems are built to close those gaps.

Key takeaway: The fine that matters most is the RM1 million principles offence, because notice, consent, security and retention failures all fall under it.

6. How Long Can You Keep Dormant Member Accounts?

Quick Answer: The PDPA sets no fixed period. Section 10 says keep data only as long as its purpose needs, then destroy or permanently delete it. For loyalty programmes, the natural trigger is inactivity: once points expire and a member stays silent, the purpose has usually ended.

Points expiry gives you a ready-made retention clock, one of the simplest loyalty programme PDPA wins. The timeline below is an example policy, not a legal requirement; set your own periods and write them into your terms and notice.

Illustrative scenario: a member data retention timeline
Time-series table showing an example retention policy for loyalty programme member data, from the last purchase through points expiry, a reminder, and deletion or anonymisation.
Time since last activityAccount statusData action
0 to 12 monthsActiveFull profile kept
12 monthsPoints expireStop profiling; marketing only if opted in
21 monthsDormantSend one “keep my account?” reminder
24 monthsClosedDelete or anonymise; keep sales totals without names

Source: Illustrative policy by ZenWeb based on section 10 of Act 709, as at October 2026. Periods are examples only; tax records such as invoices may need to be kept longer under other laws. Licence.

Three related rights apply while you hold the data:

Key takeaway: Link deletion to points expiry and you get a retention rule members already understand. Anonymised totals keep your sales reporting intact.

7. Loyalty Programme PDPA Checklist: 7 Steps

Quick Answer: Trim the sign-up fields, publish a bilingual notice, separate marketing consent, decide on profiling, check every data recipient, set a retention rule, and handle requests quickly. A typical SME can complete the website side in one or two weeks.

  1. Trim the sign-up form. Name, mobile and birthday day/month cover most programmes. Drop IC numbers unless you truly need them.
  2. Publish a bilingual notice. Bahasa Malaysia and English, shown at sign-up on web, app and in-store forms.
  3. Separate marketing consent. An unticked checkbox per channel, recorded with date and source.
  4. Decide on profiling. If purchase data drives offers or ad audiences, disclose it and check the DPO tests.
  5. Check every recipient. Vendors, partners, ad platforms and overseas servers must match your notice.
  6. Set a retention rule. Tie deletion or anonymisation to points expiry and inactivity.
  7. Handle requests. Give staff a simple way to process opt-outs, access, correction and portability requests.

Worked example: a bakery chain in Klang collects name, mobile, full birth date and IC number at the counter, with a pre-ticked “receive promotions” box. After review, it drops the IC number and birth year, unticks the box, adds a bilingual notice, and closes accounts after 24 months of inactivity. If it later wants WhatsApp birthday offers, only members who ticked the WhatsApp option receive them. Those opt-ins also make its email marketing and first-party data worth more, because every contact has agreed to hear from it.

On the website, the member sign-up form and any cookie banner need to work together. Our guide to Consent Mode and PDPA for GA4 covers tags. If analytics drops after the banner goes live, use the GA4 showing no data fix to find out why.

Key takeaway: Steps 1 and 3 fix most loyalty programme PDPA problems at the source: collect less, and ask for marketing consent separately.

8. Conclusion: Rewards Work Better With Trust

Loyalty programme PDPA compliance is mostly about matching what you do with what you told members. Collect only what the programme needs, keep marketing consent separate, be open about profiling, and close dormant accounts on a clear schedule. Members who trust how you handle their data are more likely to stay, spend and open your offers, which is the point of the programme. For the wider picture on keeping buyers, see our customer retention guide.


9. Frequently Asked Questions

1. Do I need consent to run a loyalty programme in Malaysia?

Yes. Under the PDPA’s General Principle, you need the member’s consent to process their data, given at sign-up with a bilingual notice. Marketing messages need a separate opt-in.

2. Can I send birthday promotions to members?

Only to members who agreed to receive marketing through that channel. A birthday voucher is direct marketing under section 43, and members can tell you to stop at any time.

3. Can children join my loyalty programme?

For members under 18, the PDPA treats a parent or guardian as the person who consents. Many SMEs simply set 18 as the minimum age for membership.

4. Does a loyalty programme need a Data Protection Officer?

Yes if you hold data on more than 20,000 people. Below that, the Commissioner’s guideline says account-only programmes may not count as monitoring, but behaviour profiling might.

5. Can ZenWeb build a PDPA-friendly member sign-up?

Yes, for the website and marketing side: sign-up forms, bilingual notices, consent records and secure logins. Legal questions, such as whether you need a DPO, should go to a licensed lawyer.

Cite this page: ZenWeb (2026). Loyalty Programme Data Under PDPA: Points, Profiles, Consent. https://zenweb.my/blog/loyalty-programme-pdpa/

You may quote our data with this credit and a link. See our Terms of Use.

Grow your member base without the data headaches

Talk to ZenWeb about member sign-up pages, consent-based CRM campaigns and PDPA-friendly tracking. We handle the website and marketing; your lawyer confirms the legal calls.

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.