Digital Solutions Specialist Singapore
October 10, 2026
If your website collects names, emails, phone numbers or any other personal data, the Personal Data Protection Act (PDPA) applies to it. A PDPA-compliant website tells visitors clearly why their data is collected, gets proper consent, protects what it stores and lets people reach your Data Protection Officer. Here is what that looks like in practice for contact forms, cookies, newsletters and privacy policies.
For most Singapore SMEs, the website is where personal data enters the business: enquiry forms, quotation requests, appointment bookings, newsletter sign-ups, live chat and online checkouts. Every one of these is covered by the Personal Data Protection Commission (PDPC)‘s rules on how organisations collect, use and disclose personal data.
The stakes are real. For breaches from 1 October 2022, the PDPC can impose a financial penalty of up to S$1 million or 10% of an organisation’s annual turnover in Singapore, whichever is higher [2]. Beyond penalties, a data incident damages the trust that brought customers to your website in the first place.
| PDPA obligation | What it means on your website |
|---|---|
| Consent | Only collect data with the person’s consent; don’t pre-tick marketing boxes |
| Notification | Tell people why you collect their data, at the point of collection |
| Purpose limitation | Use enquiry data to answer the enquiry, not for unrelated purposes |
| Protection | Use HTTPS, secure your forms and admin areas, keep software updated |
| Retention limitation | Delete old form submissions you no longer need |
| Access and correction | Have a way for people to ask what data you hold and correct it |
| Accountability | Appoint a Data Protection Officer and publish their business contact details |
| Data breach notification | Notify the PDPC within 3 calendar days once a breach is assessed as notifiable |

Collect only what you need to respond. If you only need an email address to answer a question, don’t make NRIC numbers, home addresses or dates of birth mandatory. Add a short notice beside the submit button explaining how the data will be used, with a link to your privacy policy. If you want to send marketing later, ask for that separately with an unticked checkbox.
Marketing consent should be clear and specific. If you send marketing messages to Singapore phone numbers by call, SMS or WhatsApp, you also need to follow the PDPA’s Do Not Call provisions, which generally means checking numbers against the DNC Registry unless you have clear and unambiguous consent. Make it easy to unsubscribe from every email.
Analytics, advertising pixels and chat widgets can collect personal data through cookies. Use a clear cookie notice that explains what you use and why, and give visitors a way to manage non-essential cookies. The PDPC’s advisory guidelines discuss when consent is needed for cookies; your web developer should configure your tags so they match what your notice says.
Form submissions often sit in your website’s database or inbox for years. Protect them with HTTPS, strong admin passwords and two-factor authentication, limit who can access submissions, and keep your CMS, theme and plugins up to date. Proactive website maintenance and secure Singapore web hosting remove many common risks. Websentials itself holds the Cyber Essentials mark, so we apply the same security discipline to client websites.
Your privacy policy should explain, in plain language, what data you collect, why, who you share it with, how long you keep it and how to contact your Data Protection Officer. Link to it from your footer and from every form.
Decide in advance who assesses an incident, who contacts the PDPC and how affected customers will be informed. Once you determine that a breach is notifiable, the PDPC must be notified as soon as practicable and no later than 3 calendar days [1].
Yes. The PDPA applies to organisations of all sizes that collect, use or disclose personal data in Singapore, including sole proprietors and SMEs. A simple enquiry form is enough to bring your website into scope.
Yes. Organisations must designate at least one person to be responsible for PDPA compliance and make that person’s business contact information publicly available, for example on your website’s privacy policy or contact page.
Generally, organisations should not collect full NRIC numbers unless the law requires it or it is necessary to verify identity to a high degree of fidelity. For most website enquiries, a name and contact details are enough. Check the PDPC’s advisory guidelines on NRIC numbers before collecting them.
A PDPA-ready website protects your customers and your business. At Websentials, we build secure forms, sensible data retention and clear consent flows into our web development projects, and we can review your current site.
Contact the Websentials team today to review your website’s data protection.
This article is general information, not legal advice. Refer to the PDPC’s guidelines or seek legal advice for your specific situation.