
Most Malaysian business websites have a contact form, and most of those forms say nothing about personal data. Some carry one line in small grey text: “By submitting this form, you agree to our privacy policy.” That line feels safe. It usually is not enough.
This guide explains the contact form PDPA rules as they apply to the form itself: what the notice must cover, where it should sit, sample wording in both languages, and how the wording changes for quote, newsletter and careers forms. It comes from ZenWeb, a Malaysian Google Partner agency with 500+ clients that designs and 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 own notice wording with a licensed lawyer before you rely on it.
Building or refreshing your website?
We design enquiry forms with bilingual notices, separate consent boxes and clean data routing built in from the first draft. See our web design services →
Before the form-level detail, 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 website forms specifically.
Quick Answer: Yes. A name, phone number or email typed into your form is personal data collected in a commercial transaction, so the PDPA applies. Section 7 requires a written notice “when the data subject is first asked” to provide the data. For a website, that moment is the form itself.
The Personal Data Protection Act 2010 (Act 709) lists eight things the notice must tell people. The privacy policy can hold the long version; the form carries the short version, because that is where the visitor is.
| Section 7(1) item | On the form | In the privacy policy |
|---|---|---|
| (a) Data being processed | Short: “your name, phone and email” | Full list, including IP and cookies |
| (b) Purpose | Short: “to reply to your enquiry” | All purposes across the business |
| (c) Source of the data | Usually obvious (the visitor typed it) | Other sources, such as referrals |
| (d) Access, correction and contact | One email address | Full request process |
| (e) Third parties | Class only: “our service providers” | Each class with examples |
| (f) Choices to limit processing | Optional marketing checkbox | How to opt out later |
| (g) Obligatory or voluntary | Mark required fields with * | Not needed |
| (h) Effect of not supplying | “Without a phone or email we cannot reply” | Not needed |
Source: ZenWeb mapping of Act 709 section 7(1) to a standard website enquiry form. As at October 2026. Licence.
The Personal Data Protection (Amendment) Act 2024 (Act A1727) renamed the “data user” a “data controller” and raised the maximum penalty for breaching a principle to RM1,000,000, three years’ jail, or both. For the policy page itself, see our guide to a website privacy policy under PDPA.
Quick Answer: Directly above the submit button, in readable text, with a link to the full privacy policy. This “layered” approach puts the key points where the visitor’s eyes already are. A link in the site footer, or a notice that only appears after submission, misses the “first asked” timing in section 7(2).
Placement decides whether anyone sees the notice. This modelled comparison estimates reach before submission for five common placements.
| Notice placement | Likely to see it | Relative reach |
|---|---|---|
| Footer privacy link only | About 20 | |
| Shown after submission | 0 before submitting | |
| Grey fine print below the button | About 250 | |
| Readable notice above the button | About 650 | |
| Notice above button plus consent tick box | About 850 |
Source: Illustrative scenario by ZenWeb. Figures are assumptions to show relative visibility, not measured client data or a legal standard. As at October 2026. Licence.
Three design details help the notice work without hurting enquiries:
Quick Answer: One short paragraph per language that names your business, the data, the purpose, who may receive it and a contact email, plus a link to the full policy. Add a separate, unticked box for marketing. Section 7(3) requires both the notice and the choice to be offered in the national language and English.
Here is illustrative wording for a fictional Petaling Jaya interior design firm, Ruang Kemas Interiors. Replace the company name, purposes and email with your own, and have your lawyer review the final text.
English: Ruang Kemas Interiors Sdn Bhd will use the name, phone number, email and project details you enter here to reply to your enquiry and prepare a quotation. We may share them with our IT and email service providers for this purpose only. Fields marked * are required; without them we cannot reply. To access or correct your data, email privacy@ruangkemas.example. See our Privacy Notice for full details.
Bahasa Malaysia: Ruang Kemas Interiors Sdn Bhd akan menggunakan nama, nombor telefon, e-mel dan butiran projek yang anda masukkan di sini untuk membalas pertanyaan anda dan menyediakan sebut harga. Kami mungkin berkongsi butiran ini dengan penyedia perkhidmatan IT dan e-mel kami untuk tujuan ini sahaja. Ruangan bertanda * adalah wajib; tanpanya kami tidak dapat membalas. Untuk mengakses atau membetulkan data anda, e-mel privacy@ruangkemas.example. Lihat Notis Privasi kami untuk butiran penuh.
Then add one optional checkbox, unticked by default and not required to submit:
Why no consent box for the enquiry? Section 6(2)(b) allows processing needed for steps the person requested towards a contract, and replying to a quote request fits. Marketing is a separate purpose, so it gets its own choice. See the bilingual privacy notice rule for layouts, and WhatsApp marketing and PDPA for what the opt-in allows.
Quick Answer: Usually not on its own. The catch-all line tells visitors nothing about the data, the purpose or who receives it, so it rarely covers the section 7 items. It also bundles enquiry handling and marketing into one assumed “agreement”, which makes any later marketing consent hard to prove.
Many sites copy this line from large companies. The problem is what it leaves out:
The same trap appears when businesses buy or swap contact lists to “top up” form leads; our guide to buying lead lists under PDPA explains why those contacts never saw your notice at all.
Quick Answer: The structure stays the same, but the purpose, the third parties and the consent box change with each form. A newsletter form exists for marketing, so its consent is the point. A careers form collects more sensitive detail. An e-invoice request form collects tax identifiers, which need their own purpose line.
One generic notice copied onto every form will be wrong somewhere. Adjust each one:
| Form type | Purpose line | Consent approach |
|---|---|---|
| Contact / enquiry | Reply to your enquiry | Notice only; optional marketing box |
| Quote request | Prepare a quotation; arrange a site visit | Notice; name any subcontractors as a class |
| Newsletter sign-up | Send updates and promotions | Signing up is the opt-in; unsubscribe link in every email |
| Careers / job application | Assess your application | Notice; state how long CVs are kept |
| E-invoice request | Issue your e-invoice through MyInvois | Notice; name LHDN as a recipient |
| Member or rewards sign-up | Run your account and points | Notice; separate box for profiling and offers |
Source: ZenWeb guidance based on Act 709 sections 6, 7 and 43. Adjust to your own purposes. As at October 2026. Licence.
An e-invoice request form on your website collects TINs and IC or company numbers, so its notice must say they go to LHDN. A rewards sign-up builds a profile over time; see loyalty programme data under PDPA.
Five forms, five different notices?
We audit every form on your site and set up the right notice, fields and consent box for each one, without slowing your enquiries. Get a website form review →
Quick Answer: Usually to more places than the owner thinks: an email inbox, the form plugin’s database, a CRM, an anti-spam service and sometimes an ad platform. Your notice must name these classes of third party, and each copy must be secured under the Security Principle, which Act A1727 extended to data processors.
Before writing the “who we share it with” line, trace one test submission through your site:
| Destination | Name in notice? | Main risk |
|---|---|---|
| Email inbox | As “email service provider” | Forwarded to personal accounts; never deleted |
| Form plugin database | As “website hosting provider” | Entries pile up for years in WordPress |
| CRM or sales tool | As “customer management service” | Shared logins; former staff keep access |
| Anti-spam service (e.g. reCAPTCHA) | Yes, with its own disclosure | Badge hidden without the required text |
| Ad platform (conversion upload) | Yes, as “advertising partners” | Customer data shared without being mentioned |
Source: ZenWeb review of common Malaysian SME website setups, read against Act 709 sections 7(1)(e), 8 and 9 and Act A1727. As at October 2026. Licence.
On reCAPTCHA, Google’s reCAPTCHA FAQ lets you hide the badge only if the reCAPTCHA branding stays visible in the user flow. The other destinations each have a PDPA guide:
Delivery problems create stray copies too, so fix form emails going to spam and a contact form flooded with spam at the source.
Quick Answer: List every form, trace where its data goes, trim the fields, write a bilingual notice above each submit button, add an optional marketing box, update the privacy policy, and keep a dated screenshot. A typical small-business site with three to five forms can usually be fixed in a day.
Work through this list for every form on your website, including pop-ups and landing pages:
For the wider set of principles beyond forms, use our PDPA compliance checklist for Malaysian marketers. If your site also runs tracking scripts, check whether you need a PDPA cookie banner on your website.
Contact form PDPA compliance is mostly about telling people the truth at the right moment. As at October 2026, every form on your site should have:
The same logic applies to Facebook lead ads and PDPA. Paying overseas plugin vendors brings its own admin; see the CP37 withholding tax form. If a form is not delivering at all, start with a contact form not sending emails. For forms built right from day one, talk to our web design team.
Yes. Any form that collects a name, phone number or email in a commercial setting is collecting personal data. Section 7 of the PDPA expects a written notice when you first ask for that data, so a short notice on the form itself is the safest approach.
Usually not on its own. A link alone rarely tells visitors the purpose, the recipients or how to contact you. Use a short notice on the form and keep the link for the full detail.
Yes. Section 7(3) of the PDPA requires the notice, and any means of making a choice, to be in the national and English languages.
Generally no. Replying to a request the visitor made is allowed as a step towards a contract. You do need a separate, clear choice for ongoing marketing such as newsletters and promotions.
We design the forms, the bilingual notice layout, the consent boxes and the data routing. The final legal wording should be checked by a licensed lawyer.
Cite this page: ZenWeb (2026). Website Contact Form PDPA Notice: Wording That Complies. https://zenweb.my/blog/contact-form-pdpa-notice/
You may quote our data with this credit and a link. See our Terms of Use.
Get website forms that win trust and enquiries
Talk to ZenWeb about a website with clear PDPA notices, clean consent records and forms that still convert. 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.