
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.
Source video: The Legal Insight Podcast on YouTube, published February 2025. It covers the amendments in general, not loyalty programmes specifically.
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.
| Data type | Typical use | PDPA status |
|---|---|---|
| Name, phone, email | Member ID, login, receipts | Personal data |
| Birthday | Birthday rewards | Personal data; ask only day and month if the year is not needed |
| Points and tier | Rewards, member status | Personal data once tied to a member |
| Purchase history | Points earning, personalised offers | Personal data; profiling raises extra duties |
| IC or passport number | Identity checks | Personal data; usually excessive for a points card |
| Face scan or fingerprint | Check-in, app login | Sensitive personal data (biometric) since 1 April 2025 |
| Health or dietary notes | Product suggestions | May 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.
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:
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.
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.
| Feature | Account-only programme | Profiling programme |
|---|---|---|
| Purchase data use | Calculate points only | Segment members by habits |
| Offers | Same offer for every member | Personalised by past purchases |
| Ad audiences | None | Member lists uploaded to Meta or Google |
| Web and app tracking | Login only | Browsing tied to member ID |
| DPO monitoring test | Guideline says may not apply | Closer 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.
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:
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.
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 →
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.
| Offence (section) | Max fine / jail | Relative 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.
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.
| Time since last activity | Account status | Data action |
|---|---|---|
| 0 to 12 months | Active | Full profile kept |
| 12 months | Points expire | Stop profiling; marketing only if opted in |
| 21 months | Dormant | Send one “keep my account?” reminder |
| 24 months | Closed | Delete 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:
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.
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.
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.
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.
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.
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.
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.
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.
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.