ZenWeb - Blog - Heatmaps and Session Recordings: PDPA Risks on Your Site

Heatmaps and Session Recordings: PDPA Risks on Your Site

November 3, 2026

Share this post:

Heatmaps and Session Recordings: PDPA Risks on Your Site
TL;DR: Heatmaps are usually low risk because they combine many visits. Session recordings are different: they replay one visitor’s clicks, scrolls and screens, and can capture names, phone numbers or account details. Under the PDPA, that recorded data is personal data once a visitor can be identified. Mask every form and account page, say so in your privacy notice, keep recordings short-lived and check the tool vendor’s data terms.

Heatmap and session recording tools are now standard on Malaysian business websites. Microsoft Clarity is free, Hotjar has a free plan, and both install in minutes. Most owners switch them on to fix a leaky lead form and never look at the privacy settings again.

This guide explains where session recording PDPA risk comes from, which rules apply as at October 2026, and how to set up recordings so they help your conversion rate without exposing customer data. It comes from ZenWeb, a Malaysian Google Partner agency with 500+ clients. We build websites, lead forms and tracking; we are not a law firm.

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.

Not sure what your recordings can see?

We build websites with forms, checkouts and member areas masked from day one, so your UX data stays useful and your visitors’ details stay private. See our web design services →

First, this short video from the Microsoft Clarity team shows the privacy controls most SMEs never open: IP blocking, content masking and cookie settings.

Microsoft Clarity's Approach to Data Privacy

Source video: Microsoft Clarity on YouTube, published August 2024. It covers the tool's features, not Malaysian law.

1. Is Session Recording Data Personal Data Under PDPA?

Quick Answer: Often, yes. The PDPA covers information about a person who can be identified from it, directly or with other data you hold. A recording that shows someone typing their name, or that links to a logged-in user ID, CRM record or lead, is personal data. A purely aggregated heatmap with no identifiers usually is not.

The definition in section 4 of the Personal Data Protection Act 2010 (Act 709) turns on whether a person is identifiable from that information plus other information you hold. That second part matters for marketers. An anonymous session becomes personal once you match it to a form submission, a WhatsApp chat or a customer account.

Heatmaps and recordings sit at very different points on that scale. If you need a refresher on how the tools work, see what a heatmap is and our guide to using session recordings to find drop-offs. This post covers only the privacy side.

What each behaviour tool captures, and its PDPA exposure
Data table comparing aggregated heatmaps, scroll maps, anonymous session recordings and identified session recordings by what they capture and their likely exposure under Malaysia’s PDPA.
Tool outputWhat it capturesLikely PDPA exposure
Click or tap heatmapCombined clicks from many visits on one pageLow, if no identifiers are attached
Scroll mapHow far visitors scroll, averagedLow
Anonymous session recordingOne visitor’s journey, device, location, page contentMedium: personal if unmasked text or a match to other data reveals who it is
Identified session recordingA journey tied to a login, email, user ID or lead recordHigh: personal data, all PDPA principles apply

Source: ZenWeb classification based on the personal data definition in Act 709, section 4, as at October 2026. Exposure levels are a practical guide, not a legal ruling. Licence.

Key takeaway: The risk is not the tool, it is what the tool can see and what you can link it to. Plan as if every session recording may contain personal data.

2. Which PDPA Principles Apply to Heatmaps and Recordings?

Quick Answer: Once recordings hold personal data, the seven PDPA principles apply, plus the cross-border transfer rule. The ones that bite hardest are Notice and Choice, Security and Retention. Since the 2024 amendments, breaching a principle can cost up to RM1 million, three years’ jail, or both.

The Personal Data Protection (Amendment) Act 2024 (Act A1727) raised the penalty under section 5 from RM300,000 and two years to RM1 million and three years. It also made data processors, such as an agency or tool vendor handling data on your behalf, directly responsible for the Security Principle.

PDPA principles mapped to session recording, as at October 2026
Grouped table mapping the seven PDPA principles and the cross-border transfer rule to what each means for a Malaysian website using heatmaps and session recordings.
Principle (section)What it means for recordings
General (6)Have a lawful purpose, collect only what that purpose needs
Notice and Choice (7)Tell visitors recordings happen, why, and who receives the data
Disclosure (8)Do not share recordings beyond the purpose stated, such as with ad partners
Security (9)Mask sensitive fields, limit who can watch, secure tool logins
Retention (10)Do not keep recordings longer than the purpose needs
Data Integrity and Access (11, 12)Be ready if a user asks what you hold about them
Cross-border transfer (129)Most tools store data overseas; check the conditions are met

Source: ZenWeb summary of Act 709 as amended by Act A1727, as at October 2026. Licence.

In April 2026 the Commissioner also issued a Data Protection by Design Guideline. Its core idea suits recordings well: collect nothing by default, then switch on only what you need. For the full list of duties, use our PDPA compliance checklist for marketers.

Key takeaway: A free UX tool can create a RM1 million exposure if it records what it should not. Security and retention settings are where most SMEs fall short.

3. Do You Need Consent for Session Recording in Malaysia?

Quick Answer: The law is not settled. As at October 2026, the Commissioner has issued no cookie or tracking guideline. Section 6 needs consent for processing personal data, so identifiable recordings need it. Fully masked, anonymous recordings are a grey area. The safe course is a clear notice plus an opt-in banner choice.

Here is how the session recording PDPA position looks for a typical SME site:

  • Identified recordings need consent. If recordings link to logins or leads, treat them like any other personal data and get consent through your banner or sign-up flow.
  • Anonymous, masked recordings are unclear. No Malaysian ruling says whether they are personal data. Do not assume they are exempt.
  • Your notice must mention them either way. A privacy notice that lists “analytics” but not recordings leaves visitors uninformed. Our website privacy policy guide and bilingual privacy notice rules show what to include.

Vendors are moving faster than Malaysian law. Microsoft says Clarity has enforced consent signals since 31 October 2025, but only for visitors from the EEA, UK and Switzerland. For Malaysian visitors, Clarity sets its cookies by default unless you turn on its Consent Mode. Whether you need a banner at all is covered in our PDPA cookie banner guide. Connecting the banner to your tags is explained in Consent Mode and PDPA for GA4.

Key takeaway: Where the rule is unclear, notice plus choice is cheap insurance. Load the recording script only after the visitor accepts analytics cookies.

Want recordings that wait for consent?

We wire your cookie banner to Clarity, Hotjar and GA4 so each tag fires only after the visitor says yes. Check the cost of a proper tracking setup →


4. Which Pages Leak the Most Data Into Recordings?

Quick Answer: Pages that show customer data back to the visitor: account dashboards, order confirmations, checkout summaries and “thank you” pages that repeat the lead’s name. Typed form fields are usually masked by default, but text the page displays often is not. URLs carrying an email or phone number also leak.

Most owners worry about forms, yet tools already hide typed input. Microsoft’s Clarity documentation says input boxes and drop-downs are masked in every mode. The bigger gaps are elsewhere:

  • Displayed personal text. “Thanks, Aisyah! We’ll call 012-xxx” on a thank-you page is page content, not an input.
  • Account and order pages. Addresses, order history and IC numbers shown on screen.
  • Query strings. A form that redirects to ?email=… puts the address into the recorded URL.
  • Chat widgets and embedded forms. Third-party widgets may render outside your masking rules.
Illustrative scenario: exposure risk by page type on an SME website
Bar chart table scoring six common page types on a Malaysian SME website from 1 to 10 for the risk that session recordings capture personal data.
Page typeRisk score (1–10)Relative risk
Member account / order history9
Checkout summary8
Personalised thank-you page7
Lead form page4
Blog article2
Service or pricing page1

Source: Illustrative scenario by ZenWeb, scored on how much personal data each page typically displays. Modelled estimates, not client data or a benchmark. As at October 2026. Licence.

Forms still need care when they collect health, religious or financial details; see sensitive personal data in lead forms. On card checkouts, keep recording scripts off payment pages entirely, in line with PCI DSS rules for small online stores.

Key takeaway: Check what the page shows, not just what the visitor types. Exclude account, checkout and payment pages from recording unless you have a strong reason.

5. How Should You Set Masking in Microsoft Clarity?

Quick Answer: Keep Clarity on its default Balanced mode or move to Strict, never Relaxed. Then mask high-risk elements individually with the data-clarity-mask attribute or a CSS selector in settings. Changes apply only to new recordings and can take up to an hour, so test before relying on them.

Clarity’s three masking modes, as described in Microsoft’s masking guide, behave very differently:

Microsoft Clarity masking modes compared, as at October 2026
Comparison table of Microsoft Clarity’s Strict, Balanced and Relaxed masking modes, showing what each masks and a suggested use for Malaysian SME websites.
ModeWhat is maskedSuggested use
StrictAll text contentSites with member areas or sensitive services
Balanced (default)Numbers, email addresses, inputs, drop-downsMost brochure and lead-generation sites
RelaxedOnly inputs and drop-downsAvoid: names shown on screen are recorded

Source: Microsoft Learn, Clarity masking documentation; suggested use by ZenWeb. As at October 2026. Licence.

Two traps catch site owners. Clarity does not mask content inside style sheets, and masking cannot be applied backwards to old recordings. Hotjar works on the same idea, suppressing typed input by default. Compare the tools in our Microsoft Clarity review and Hotjar review.

Worked example: a Penang tuition centre’s thank-you page reads “Thanks, Mei Ling, we will WhatsApp 016-xxx”. In Balanced mode, the phone number is masked but the name is not. Adding data-clarity-mask="True" to that message block fixes it. The WhatsApp follow-up itself must meet the WhatsApp marketing consent rules.

Key takeaway: Default masking catches numbers and emails, not names or addresses in plain text. Mask those blocks yourself, then watch a test recording to confirm.

6. How Long Can You Keep Recordings, and Where Are They Stored?

Quick Answer: The PDPA sets no fixed period; the Retention Principle says keep data only as long as its purpose needs. Tool defaults decide much of this for you. Recordings are usually stored on the vendor’s servers overseas, so the cross-border rule and processor contracts also apply.

Retention is the session recording PDPA issue most owners never check. The timeline below shows how long Clarity keeps data by default, according to Microsoft’s recordings overview:

Microsoft Clarity recording retention timeline
Time-series table showing how long Microsoft Clarity retains session recordings by default, from day 0 to nine months, and the PDPA action an SME should take at each point.
Time after recordingWhat Clarity keepsYour PDPA action
Day 0 to 30All recordingsReview, fix issues, then move on
Day 31 onwardA sample: 1% of recordings or 10 a day, whichever is higherMention sampled retention in your notice
Up to 9 monthsSampled and favourited recordingsFavourite only recordings you truly need

Source: Microsoft Learn, Clarity recordings overview, as at October 2026; actions by ZenWeb. Vendors change these periods, so recheck yearly. Licence.

Set the same discipline you use for leads; our guide to how long you can keep lead data applies here. Overseas storage is covered in cross-border data transfer under PDPA. If an agency runs the tool for you, its duties are set out in your agency’s data processor duties.

Three more points worth knowing:

  • Breaches. A leaked tool login exposes every stored recording. Our guide to data breach notification in Malaysia explains the steps if that happens.
  • Access requests. If recordings link to a user ID, they may fall inside an access request, and possibly a data portability request.
  • DPO trigger. The Commissioner’s DPO guideline lists “regular and systematic monitoring” as one reason to appoint a data protection officer. Its examples cover tracking and profiling for behavioural advertising. Whether plain UX recordings count is not stated, so ask your lawyer if you link recordings to ad audiences.
Key takeaway: Short retention, few favourites and tight tool access reduce what any breach or request can expose. Keep recording data separate from ad audiences.

7. Session Recording PDPA Checklist: 8 Steps for Your Site

Quick Answer: Decide your purpose, update your notice, gate the script behind consent, choose strict masking, exclude high-risk pages, test a recording, limit retention and access, and review once a year. Most steps take under an hour on a standard WordPress site.

  1. Write down the purpose. For example, “find where visitors drop off the quote form”. It keeps recording scope narrow.
  2. Update your privacy notice. Name the tool, what it captures and where data is stored, in English and Bahasa Malaysia.
  3. Gate the script behind consent. Load recordings only after the visitor accepts analytics cookies.
  4. Use Balanced or Strict masking. Never Relaxed on a site with names or addresses on screen.
  5. Exclude high-risk pages. Account, checkout and payment pages stay off by default.
  6. Test a recording. Submit a dummy lead and watch it back to see what is visible.
  7. Limit retention and access. Few favourites, few admins, two-step login on the tool.
  8. Review yearly. Recheck vendor terms, masking and notices as tools and rules change.

Your on-site lead forms deserve the same notice wording you use in Facebook lead ad forms under PDPA. Build these steps in at launch through our web design service rather than retrofitting them later.

Key takeaway: Step 6 is the one most teams skip. A two-minute test recording shows exactly what your tool stores, which beats any assumption.

8. Conclusion: Use Recordings Without Recording Too Much

Heatmaps and recordings are among the cheapest ways to fix a weak website. The session recording PDPA risk comes from careless settings, not from the tools themselves. Mask by default, tell visitors, ask for consent, keep data briefly, and you get the insight without the exposure.

Like buying lead lists or buying Google reviews, careless tracking looks like a shortcut until it becomes a complaint. Most SME sites are also outside the Cyber Security Act 2024, so the PDPA is the law that matters here.


9. Frequently Asked Questions

1. Are heatmaps allowed under the PDPA?

Yes. Aggregated heatmaps with no identifiers carry little PDPA risk. Still mention them in your privacy notice and keep the tool’s masking switched on.

2. Is Microsoft Clarity PDPA compliant?

No tool is compliant on its own. Clarity offers masking, consent mode and retention limits, but you must configure them and update your notice. Compliance depends on your setup.

3. Do I need a cookie banner for session recordings?

Malaysia has no cookie-specific rule as at October 2026. If recordings can identify visitors, you need consent, and a banner is the simplest way to get it.

4. Can I record logged-in members?

Only with care. Those recordings are personal data, so get consent, mask account details and limit access. Many SMEs simply exclude member areas.

5. Can ZenWeb set this up for us?

Yes, for the website side: masking, consent-gated scripts and notice placement. Legal judgments, such as whether you need a DPO, should be confirmed with a licensed lawyer.

Cite this page: ZenWeb (2026). Heatmaps and Session Recordings: PDPA Risks on Your Site. https://zenweb.my/blog/session-recording-pdpa/

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

Get the insights, skip the privacy risk

Talk to ZenWeb about a website with PDPA-friendly tracking: masked recordings, consent-gated scripts and a clear privacy notice. We handle the website; 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.