
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.
Source video: Clym on YouTube. A general PDPA overview; it does not cover the two-language rule in detail.
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 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.
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.
| Touchpoint | Notice, choice or both | Bilingual approach |
|---|---|---|
| Privacy policy page | Notice (full version) | Full BM and English versions, linked to each other |
| Contact and quote forms | Notice (short version) | Two short paragraphs above the submit button |
| Marketing opt-in checkbox | Choice | One box, label in both languages |
| Cookie banner | Both | Banner text and buttons follow the page language, with a switch |
| Facebook and Google lead forms | Both | Custom disclaimer in both languages; bilingual privacy link |
| WhatsApp opt-in message | Both | Short bilingual opt-in line plus “STOP / BERHENTI” reply |
| Chatbot pre-chat form | Notice | Bilingual line before name and phone are asked |
| E-invoice request form | Notice | Bilingual line naming LHDN as a recipient |
| Unsubscribe and preference page | Choice | Both 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.
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.
| Layout | Score | Relative accessibility |
|---|---|---|
| Malay version as a PDF download | 2 | |
| Side-by-side columns | 4 | |
| Separate BM page linked only in the footer | 5 | |
| Language switch at the top of the policy | 8 | |
| Stacked short notice on the form itself | 9 |
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:
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 →
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 term | Term in the Malay Act text | Usage note |
|---|---|---|
| Personal data | data peribadi | Use consistently; avoid “maklumat peribadi” in one place and “data peribadi” in another |
| Data subject | subjek data | In customer-facing text, “anda” (you) is often clearer |
| Third party | pihak ketiga | Name the class too, e.g. “penyedia perkhidmatan IT” |
| Direct marketing | pemasaran langsung | Use in the opt-in label and the opt-out line |
| Consent | persetujuan | Pair with “tarik balik” for withdrawal of consent |
| Notice and Choice Principle | Prinsip Notis dan Pilihan | Useful as a policy heading |
| Data user (now “data controller” in English) | pengguna data | Act A1727 renamed the English term; check the latest official Malay text before using an updated term |
| “national and English languages” | bahasa kebangsaan dan bahasa Inggeris | The 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:
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.
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.
| Date | Milestone | What it means for your notice |
|---|---|---|
| June 2010 | Act 709 receives Royal Assent with section 7(3) | Notice and choice must be in BM and English |
| 1 January 2025 | First 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 rules | Update terms; describe overseas tools and service providers accurately |
| 1 June 2025 | Data protection officer, breach notification and portability | Add DPO contact details if you must appoint one |
| October 2026 | Position at the date of this guide | Section 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:
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:
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.
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:
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.
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.
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.
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.
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.
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.
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.