ZenWeb - Blog - Bilingual Privacy Notice: PDPA’s Bahasa Malaysia Rule

Bilingual Privacy Notice: PDPA’s Bahasa Malaysia Rule

November 2, 2026

Share this post:

Bilingual Privacy Notice: PDPA's Bahasa Malaysia Rule
TL;DR: Section 7(3) of Malaysia’s PDPA says a privacy notice must be in the national language and English, and so must the way people make their choices, such as a marketing opt-in. An English-only privacy notice, cookie banner or lead form misses the rule. Publish your privacy notice in Bahasa Malaysia and English with matching content, place both where data is collected, and keep the two in sync whenever one changes.

Many Malaysian websites have a privacy policy page. Far fewer have a privacy notice in Bahasa Malaysia. The English version is often copied from a template, and the Malay version is either missing or a rough machine translation that nobody has read since launch.

This guide looks at one specific rule: the requirement for a privacy notice in Bahasa Malaysia as well as English. It covers what the law says, which parts of your website and ads it touches, layout choices, translation pitfalls and a short checklist. It comes from ZenWeb, a Malaysian Google Partner agency with 500+ clients that builds business websites. We handle the website side; we are not a law firm. Rules are stated as at October 2026.

This post is general information, not legal advice. Please confirm your notice wording and translation with a licensed lawyer before you rely on it.

Need a bilingual website that stays in sync?

We build sites with Bahasa Malaysia and English versions of every notice, form and consent box, set up so both languages update together. See our web design services →

First, this short overview explains what Malaysia’s PDPA asks of any business that collects customer data.

Malaysia's PDPA: What Your Business Should Know

Source video: Clym on YouTube. A general PDPA overview; it does not cover the two-language rule in detail.

1. Does PDPA Require a Privacy Notice in Bahasa Malaysia?

Quick Answer: Yes. Section 7(3) of the Personal Data Protection Act 2010 says the written notice “shall be in the national and English languages”. It also says people must get a clear, readily accessible means to make their choice in both languages where a choice is needed. Bahasa Malaysia is the national language, so English alone is not enough.

The rule sits inside the Notice and Choice Principle, called Prinsip Notis dan Pilihan in the Malay text of the Personal Data Protection Act 2010 (Act 709). Read it as two separate duties:

  • The notice itself. The eight items in section 7(1), such as the data collected, the purpose and the third parties, must appear in both languages.
  • The means of choice. Where people can limit processing, for example by ticking a marketing box or opting out, that control must also be offered in both languages.
  • Timing still applies. Under section 7(2), the notice is due when you first ask for the data, so the Malay version must be there at that moment too, not added later.

The rule applies to businesses processing personal data in commercial transactions. Under section 2, that includes any business established in Malaysia, wherever its website is hosted. The Personal Data Protection (Amendment) Act 2024 (Act A1727) raised the maximum penalty for breaching a principle to RM1 million, three years’ jail, or both. For how the notice content works on a policy page, see our guide to a website privacy policy under PDPA.

Key takeaway: The two-language rule covers both what you tell people and how they say yes or no. A Malay policy page with English-only opt-in boxes still falls short.

2. Which Website and Marketing Touchpoints Need Both Languages?

Quick Answer: Any place where you ask for personal data or offer a choice about it. On a typical SME website that means the privacy policy page, every form notice, consent and marketing checkboxes, the cookie banner’s choices, lead ad disclaimers, WhatsApp opt-in messages, chatbot pre-chat forms and the unsubscribe page.

Most businesses fix the policy page and forget the smaller touchpoints. This table maps where section 7(3) usually reaches in a marketing setup.

Where the PDPA two-language rule reaches on a typical SME website and ad funnel, as at October 2026
Data table listing nine common website and marketing touchpoints, whether each carries a PDPA notice or a choice, and the bilingual approach suggested for each.
TouchpointNotice, choice or bothBilingual approach
Privacy policy pageNotice (full version)Full BM and English versions, linked to each other
Contact and quote formsNotice (short version)Two short paragraphs above the submit button
Marketing opt-in checkboxChoiceOne box, label in both languages
Cookie bannerBothBanner text and buttons follow the page language, with a switch
Facebook and Google lead formsBothCustom disclaimer in both languages; bilingual privacy link
WhatsApp opt-in messageBothShort bilingual opt-in line plus “STOP / BERHENTI” reply
Chatbot pre-chat formNoticeBilingual line before name and phone are asked
E-invoice request formNoticeBilingual line naming LHDN as a recipient
Unsubscribe and preference pageChoiceBoth languages on one page; buttons labelled in both

Source: ZenWeb mapping of Act 709 section 7 to common Malaysian SME website and ad touchpoints. As at October 2026. Licence.

Each touchpoint has its own guide. Form wording is in our contact form PDPA notice post, lead forms in Facebook lead ads and PDPA, broadcasts in WhatsApp marketing and PDPA, and cookie choices in PDPA cookie banners. If you sell online, the request form behind a consolidated e-invoice for online sales needs a bilingual notice too.

Key takeaway: The policy page is only one of about nine places the rule reaches. Audit every point where a visitor types data or clicks a choice.

3. How Should a Bilingual Privacy Notice Look on a Website?

Quick Answer: The Act sets the languages, not the layout. For short notices on forms, stack English and Bahasa Malaysia one after the other. For the full policy, use two linked pages or a language switch at the top. Avoid hiding the Malay version in a PDF or a footer link nobody finds.

Layout decides whether the Malay version is actually “readily accessible”. This modelled comparison scores five common layouts on a phone screen.

Illustrative scenario: how accessible five bilingual layouts are on mobile (score out of 10)
Bar chart table scoring, in an illustrative scenario, five bilingual privacy notice layouts out of 10 for how easily a mobile visitor can reach the Bahasa Malaysia version.
LayoutScoreRelative accessibility
Malay version as a PDF download2
Side-by-side columns4
Separate BM page linked only in the footer5
Language switch at the top of the policy8
Stacked short notice on the form itself9

Source: Illustrative scenario by ZenWeb. Scores are judgement-based assumptions about mobile accessibility, not measured client data or a legal standard. As at October 2026. Licence.

Side-by-side columns look tidy on a desktop but squeeze into unreadable strips on a phone. In practice, a layered setup works best:

  • On the form: two short stacked paragraphs, English then Bahasa Malaysia, or the reverse if most visitors are Malay speakers.
  • On the policy page: a clear “English | Bahasa Malaysia” switch at the top, with each version on its own HTML page.
  • On a bilingual site: the Malay pages link to the Malay policy, so visitors never land in the wrong language. Our guide on choosing a website language covers the wider site setup.
Key takeaway: Short notices are stacked on the form; the full policy gets two linked HTML pages with a visible switch. Never bury the Malay version in a PDF.

Is your Malay policy hidden in a PDF?

We rebuild privacy pages as linked bilingual HTML with a clear language switch, and add stacked notices to every form. Ask about a bilingual website refresh →


4. Translating a Privacy Notice into Bahasa Malaysia: Key Terms

Quick Answer: Use the terms that appear in the official Malay text of the Act, such as data peribadi, subjek data, pihak ketiga and pemasaran langsung. Do not let a free translation tool invent its own words. Then make sure both versions say the same thing, because a mismatch can leave readers of one language under-informed.

For a privacy notice in Bahasa Malaysia, machine translation is a fair first draft, but legal terms often come out wrong or inconsistent. This glossary pulls the key terms from the bilingual edition of Act 709 published by the Personal Data Protection Department.

English to Bahasa Malaysia terms for a privacy notice, taken from the official Act 709 text
Grouped glossary table matching eight English privacy notice terms to the Bahasa Malaysia terms used in the official text of Malaysia’s Personal Data Protection Act 2010, with a usage note for each.
English termTerm in the Malay Act textUsage note
Personal datadata peribadiUse consistently; avoid “maklumat peribadi” in one place and “data peribadi” in another
Data subjectsubjek dataIn customer-facing text, “anda” (you) is often clearer
Third partypihak ketigaName the class too, e.g. “penyedia perkhidmatan IT”
Direct marketingpemasaran langsungUse in the opt-in label and the opt-out line
ConsentpersetujuanPair with “tarik balik” for withdrawal of consent
Notice and Choice PrinciplePrinsip Notis dan PilihanUseful as a policy heading
Data user (now “data controller” in English)pengguna dataAct A1727 renamed the English term; check the latest official Malay text before using an updated term
“national and English languages”bahasa kebangsaan dan bahasa InggerisThe wording of section 7(3) itself

Source: ZenWeb glossary compiled from the bilingual edition of Act 709 published by the Personal Data Protection Department, read with Act A1727. As at October 2026. Licence.

Three translation habits cause most problems:

  • Translating once, updating once. The English page gets a new CRM or ad partner added; the Malay page never does. The two versions drift apart.
  • Literal word-for-word output. Long English legal sentences become stiff, hard-to-read Malay. Plain, short sentences work in both languages.
  • No language clause. Many Malaysian businesses add a line saying which version prevails if the two differ. Ask your lawyer whether you need one, and keep both versions accurate either way.

For checking individual words, the Pusat Rujukan Persuratan Melayu by Dewan Bahasa dan Pustaka is the official Malay language reference. AI tools help with drafts, but the same care applies when you feed customer data into them; see AI and PDPA for Malaysian marketers.

Key takeaway: Borrow the Act’s own Malay terms, write short sentences, and update both language versions in the same edit, every time.

5. When Must the Bilingual Notice Be Updated?

Quick Answer: Whenever the facts in it change: a new purpose, a new class of third party, a new overseas tool or a new form. Section 7(2) also requires notice before data is used for a new purpose or disclosed to a third party. Both language versions must change together, on the same day.

The two-language rule itself has stayed the same since 2010, but the 2024 amendments changed much of what a notice needs to describe. This timeline shows the milestones relevant to a marketing website.

PDPA milestones that affect what a bilingual privacy notice must say, 2010 to 2026
Time-series table listing PDPA milestones from 2010 to October 2026 and what each means for a bilingual website privacy notice.
DateMilestoneWhat it means for your notice
June 2010Act 709 receives Royal Assent with section 7(3)Notice and choice must be in BM and English
1 January 2025First phase of Act A1727 (administrative provisions)Little direct change; notices and documents can be served electronically
1 April 2025“Data controller” rename, biometric data, processor security duty, higher penalties and new cross-border rulesUpdate terms; describe overseas tools and service providers accurately
1 June 2025Data protection officer, breach notification and portabilityAdd DPO contact details if you must appoint one
October 2026Position at the date of this guideSection 7(3) unchanged; review both versions after any tool change

Source: ZenWeb timeline from Act 709, Act A1727 and the Personal Data Protection Department’s amendment notices. As at October 2026. Licence.

Common marketing changes that trigger an update in both languages:

Key takeaway: The language rule is old; the content rules are new. Every tool, partner or purpose change is a two-language edit.

6. Bilingual Privacy Notice Checklist: 6 Steps

Quick Answer: List every touchpoint, write the English notice first in plain language, translate with the Act’s own Malay terms, have a fluent reviewer and your lawyer check it, publish both versions where data is collected, and set a rule that every future edit happens in both languages at once.

Here is a worked example: a Shah Alam furniture shop runs a website, a Facebook lead form and WhatsApp broadcasts. Its policy exists only in English, and its forms say nothing. It fixes this in six steps:

  1. List every touchpoint. Policy page, two web forms, one lead form, the WhatsApp opt-in, the cookie banner and the unsubscribe page: seven items.
  2. Write the English notice in plain language. Cover the eight section 7(1) items in short sentences.
  3. Translate with the Act’s terms. Use the glossary in Section 4 so both versions match in meaning.
  4. Get two reviews. A fluent Malay speaker checks readability; a lawyer checks the legal content of both versions.
  5. Publish both versions at every touchpoint. Stacked on forms, linked pages for the policy, bilingual buttons and opt-in labels.
  6. Lock the update rule. No change to one language goes live without the other. Keep dated copies of both.

Two related processes should also work in both languages. People may ask to see or delete their data in Malay; see data access and deletion requests. And contacts from a bought list never saw your notice in any language; see buying lead lists under PDPA. For the full set of principles, use our PDPA compliance checklist.

Key takeaway: The hard part is not the first translation; it is keeping two versions identical for years. Make “both languages, same edit” a fixed rule.

7. Conclusion: Two Languages, One Notice

A privacy notice in Bahasa Malaysia is not optional extra polish. As at October 2026, section 7(3) still requires the notice and the means of choice in both the national language and English. In practice that means:

  • Both languages at every touchpoint, not just on the policy page.
  • Layouts that work on a phone: stacked on forms, linked HTML pages for the policy.
  • The Act’s own Malay terms, reviewed by a fluent speaker and a lawyer.
  • Every update made in both versions on the same day.

If your site also targets Malay searchers, the same bilingual pages support multilingual SEO in Malaysia. For a website built bilingual from day one, talk to our web design team.


8. Frequently Asked Questions

1. Is an English-only privacy policy legal in Malaysia?

Generally no, if your business is covered by the PDPA. Section 7(3) requires the notice to be in the national language and English, so an English-only policy misses the language requirement.

2. Can I use Google Translate for a privacy notice in Bahasa Malaysia?

As a first draft only. Machine translation often gets legal terms wrong or uses them inconsistently. Use the Act’s own Malay terms and have a fluent speaker and a lawyer review the result.

3. Do I also need a Chinese or Tamil version?

The PDPA requires Bahasa Malaysia and English. Adding Chinese or Tamil is optional, but it can help if many of your customers read those languages best.

4. Does the two-language rule apply to opt-in checkboxes?

Yes. Section 7(3) says people must be given a clear and readily accessible means to make their choice in both languages where a choice is needed, which covers marketing opt-ins and opt-outs.

5. Can ZenWeb translate our privacy notice?

We build the bilingual pages, form notices, consent boxes and language switches. The final legal wording in both languages should be checked by a licensed lawyer.

Cite this page: ZenWeb (2026). Bilingual Privacy Notice: PDPA’s Bahasa Malaysia Rule. https://zenweb.my/blog/bilingual-privacy-notice-pdpa/

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

Build a website that speaks both languages properly

Talk to ZenWeb about a bilingual website with matching privacy pages, form notices and consent boxes that update together. We handle the design and build; your lawyer confirms the legal wording.

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.