Skip to content
Website.sg
Our workThe offerWho it's forPricingFAQGuides
+65 8064 4822Get Your Website

Cookie Consent in Singapore: Do You Need a Banner?

Guide · 12 min read · Updated 27 Oct 2026

Do you need a cookie banner in Singapore? Understand PDPA consent and notification, what your site really collects, and what to check with the PDPC.
yourbusiness.sg/contact

There is no simple yes or no that fits every site. In Singapore, the PDPA focuses on how organisations collect, use and disclose personal data, and cookies matter when they are used to collect it. Whether you need a banner depends on what your site actually does, so start by finding out, then check the current guidance at the PDPC.

This guide is general information, not legal advice. Rules and guidance change. Check the current position at pdpc.gov.sg and speak to a qualified adviser for your specific situation.

Key takeaways

  • ✓Singapore's PDPA is built around consent, notification and purpose, not around a universal cookie banner rule.
  • ✓What matters is what your site collects: analytics, ads pixels, chat widgets, forms and embedded content.
  • ✓Audit your site first. You cannot write an honest notice about cookies you have not found.
  • ✓Tell visitors in plain English what you collect and why, and make it easy to contact you.
  • ✓Check pdpc.gov.sg for the current guidance instead of copying a European-style banner by default.

What cookies actually are

A cookie is a small file your browser stores for a site. Some are needed for the site to work, like keeping a shopping cart. Others measure visits, remember preferences or help advertisers recognise people across sites.

Cookies are one of several tools, along with tracking pixels, scripts and local storage, that can identify or follow a visitor. The legal question is rarely about the cookie itself. It is about whether personal data is involved and how you handle it.

Common cookie types on small business sites

PurposeTypical sourceThink about
EssentialKeeps the site working, such as a cart or securityYour platform or hostingUsually explain; hard to switch off
AnalyticsCounts visits and actionsGA4 or similarSay what you measure and why
AdvertisingRemarketing and ad measurementAd pixels from ad platformsMore sensitive; be clear and careful
Embedded contentMaps, videos, social feedsThird-party providersThey may set their own cookies
Chat and formsRemembers conversation or collects detailsChat widgets, form toolsOften involves personal data directly

How the PDPA looks at this

The PDPA, which the PDPC administers, sets out obligations about personal data. In plain terms, organisations are expected to tell people why they collect data, get appropriate consent where needed, use the data only for stated purposes, protect it, and let people ask about it.

Consent

Consent generally means the person knows what they are agreeing to. A hidden tick box or a vague "by using this site" line may not be enough where you need real consent.

Notification

Notification means telling visitors what you collect and why. This is where a clear, readable privacy notice does most of the work for a small site.

Purpose and retention

Collect what you need, use it for the reason you gave, and do not keep it forever. An enquiry from three years ago does not need to sit in a spreadsheet.

If you collect names and numbers through forms and chat, read PDPA for website owners and PDPA and WhatsApp marketing as well.

Step 1: audit what your site really does

Many owners are surprised by what their site loads. Plugins, themes and embeds can quietly add trackers. Work through this list.

Site tracking audit

Scripts and tags

  • Analytics such as GA4
  • Ad pixels from Google, Meta or TikTok
  • Heatmap or session tools
  • Tag manager containers

Things that collect details

  • Contact and quote forms
  • Newsletter sign-ups
  • Live chat or chatbot widgets
  • Booking or payment tools

Embeds

  • Google Maps
  • YouTube or Vimeo videos
  • Social feeds and share buttons
  • Review widgets
Ask your web provider for a list, or use your browser's developer tools or a free cookie scanner to check.

Step 2: decide what you really need

A plain brochure site with no analytics, no ad pixels and a basic contact form needs very little beyond a clear privacy notice. A site with ad pixels, remarketing and several third-party tools has more to explain and more to control.

How much attention does your site need?

Little personal dataLots of personal data

Notice and care

Forms and chat collect details. Be clear about purpose and keep records tidy.

Closest scrutiny

Ads, trackers and personal data together. Get proper advice.

Light touch

A short privacy notice and contact route is the main job.

Explain and offer choice

Heavy tracking, little data collected. Think about a consent tool.

Few trackersMany trackers

Do you need a banner?

A cookie banner is a tool, not a legal magic wand. It makes sense when you use non-essential trackers and want a way to ask visitors before they run. It does less good when it just sits on top of a site that has already loaded everything.

Banners are worth considering if you:

  • run advertising or remarketing pixels,
  • use several third-party analytics or marketing tools,
  • serve visitors from other regions with their own cookie rules,
  • want to give visitors a clear choice about non-essential tracking.

If your visitors are overseas, such as European customers, other countries' laws may apply on top of Singapore's. That is a question for a qualified adviser.

If you use a banner

Do

  • ✓Make sure non-essential scripts really wait until the visitor agrees.
  • ✓Use plain words: what you collect and why.
  • ✓Make Reject as easy to find as Accept.
  • ✓Link to your privacy notice and your contact route.

Avoid

  • ✕Show a banner while trackers already fire in the background.
  • ✕Hide the reject option in small print.
  • ✕Copy a template that describes tools you do not use.
  • ✕Forget to update the banner after adding a new tool.

Write a privacy notice people can read

For a small Singapore site, a short notice covering these points is a sensible starting place.

Privacy notice outline

Adapt to your site
What we collect: the details you send us through our form, WhatsApp or chat, and basic visit information through analytics. Why we collect it: to reply to your enquiry, provide our service and understand how our website is used. Who sees it: our team and the service providers who help run our website, chat and messaging. How long we keep it: only as long as we need it for the purposes above. Your choices: contact us at [email] to ask about, correct or withdraw your details.
Have a qualified adviser review your final wording.

A worked scenario: a tuition centre

A small tuition centre in Bishan runs a site with a trial-lesson form, a Google Maps embed, GA4 and a Meta pixel for ads. The owner audits the site and finds the pixel, the maps cookies and the analytics.

She keeps analytics but removes an old heatmap tool she no longer uses. She adds a clear privacy notice to the footer, mentions the trial form's purpose next to the submit button, and adds a consent tool because she runs ads. She tests it by opening the site in a fresh browser window and checking that the ad pixel does not fire before she clicks Accept. Then she puts a quarterly reminder in her calendar to re-check after any site change.

A practical order of work

  1. 1

    Audit

    List every script, form and embed.

  2. 2

    Trim

    Remove tools you do not use.

  3. 3

    Notify

    Publish a clear privacy notice.

  4. 4

    Choose

    Decide whether a consent tool fits your tracking.

  5. 5

    Test

    Check what loads before and after consent.

Another scenario: a home bakery with online ordering

Mei runs a home bakery in Tampines. Her site has an order form, a payment link supplied by a payment provider, an embedded Instagram feed and GA4. She has no ad pixels. After her audit she realises the order form collects names, addresses and phone numbers, which is the most important item on the list, far more than the cookies.

She writes a short notice that says the details are used to fulfil the order and arrange delivery, adds a line near the submit button, and decides how long she will keep old orders. She also removes the Instagram feed because it was loading third-party scripts on every page and adding little value. Since she runs no ads, she decides with her adviser that a simple notice and a contact route suit her setup, rather than a full consent tool. Your own decision may differ, which is why the audit comes first.

Words to put next to your forms

The place where a small business collects the most personal data is usually a form or a chat, not a cookie. A short line beside the button does a lot of the notification work.

Short notice beside a contact form

Adapt to your site
We will use your name, number and message to reply to your enquiry and, if you go ahead, to provide our service. We do not keep your details longer than we need to. To ask about or withdraw your details, contact us at [email]. Read our privacy notice at [link].
Have a qualified adviser review your final wording, and make sure it matches what you actually do.

Short line for a WhatsApp button

Adapt to your site
Chat with us on WhatsApp. We will use your number and messages to reply to your enquiry. See our privacy notice at [link].
Useful where a click opens a chat that will carry the visitor's phone number and message.

Troubleshooting: how to test what loads

A banner is only honest if the site behaves the way it says. Here is a simple way to check without technical skills.

A five-minute consent test

  1. 1

    Open a fresh window

    Use a private or incognito window so old cookies do not confuse the result.

  2. 2

    Do not click anything

    Look at what your browser tools or a free scanner list before any choice is made.

  3. 3

    Click Reject

    Reload and check that non-essential trackers still stay quiet.

  4. 4

    Click Accept

    Confirm that the tools you described now run, and only those.

  5. 5

    Repeat on mobile

    Some themes load a different set of scripts on a phone.

What should happen to a non-essential tracker

Visitor arrives

Only essential items load.

→

Notice and choice

Plain words, equal buttons.

→

Choice recorded

Stored so you do not nag.

→

Tools run or stay off

Matching the choice.

If trackers fire before the choice is made, the banner is decoration. Ask your provider to fix the loading order.
  • Banner shows but pixels fire early: the scripts were added directly to the theme, not through the consent tool. Ask your provider to route them through it.
  • Reject does nothing: the banner may only remember the choice and never block anything. Test again after a fix.
  • Banner disappears after a theme update: re-test after every update or redesign.
  • An old tool keeps appearing in the scan: find where it was installed and remove it completely, not just from the dashboard.

Quarterly privacy check

  • List any new plugin, pixel, chat tool or embed added this quarter.
  • Check the privacy notice still describes what you collect.
  • Delete old enquiries you no longer need.
  • Test the forms and chat so messages still arrive.
  • Confirm the contact route for data requests still works.
Put the date in your calendar. Small regular checks beat a panic after something goes wrong.

Mistakes to avoid

  • Banner without control: the banner looks fine, but the scripts ignore it.
  • Forgetting WhatsApp and chat: messages carry personal data, even though no cookie is involved.
  • No contact route: visitors should know how to ask about their data.
  • Treating it as one-off: every new plugin or pixel changes your position.
  • Assuming a template is compliant: a copied notice may describe a different business.

Frequently asked questions

Does Singapore have a law that says every site must show a cookie banner?
We are not aware of a rule that requires one on every site, but we cannot give legal advice. The PDPA's consent and notification principles still apply to personal data, so check the current guidance at pdpc.gov.sg.
Do I need consent just for Google Analytics?
It depends on how it is configured and what data it collects. Tell visitors you use it, and check the PDPC's current guidance on whether and how consent applies in your case.
Does the PDPA apply to a one-person business?
The PDPA generally applies to organisations, which can include sole proprietors. Confirm your own position with the PDPC or an adviser.
What about visitors from Europe?
Other countries' laws may apply to their residents. If you actively target overseas customers, get proper advice.
Who sets up the banner, me or my web provider?
Usually your provider installs it, but you decide what you track and what the notice says. Ask them to show you what loads before and after consent.

Your next step

Run the tracking audit this week and write down every tool you find. Then read the current guidance at pdpc.gov.sg and decide what to notify and what to ask consent for. If you want a site where chat, forms and follow-up are set up in one place, see what Website.sg includes. Related reading: PDPA for website owners, website analytics setup and website security basics.

Want a website without the hassle?

Website.sg builds your website and sets up web chat, WhatsApp follow-up and Google reviews for one monthly price.

See pricing

Related services

Website.sgWebsite design SingaporeWhat a well-designed small-business website actually does, and how we approach the design.Website.sgWebsite design cost SingaporeWhat drives the price of a website in Singapore, and what S$97 a month covers.

Keep reading

GuideGoogle review policy for small business ownersGuideWebsite Speed Guide for Small Business OwnersGuideReview Rating Page Explained: The Compliant Way

Website.sg

Operated by Shaminder Tech · UEN 53524745A · Singapore

60 Paya Lebar Rd, #06-28, Singapore 409051

hello@website.sg

Privacy PolicyTerms of Service
© 2026 Shaminder Tech. Website.sg is not affiliated with, or endorsed by, Google, Meta or WhatsApp.