Not automatically. Singapore's PDPA doesn't have a rule that says "every website must show a cookie banner". What matters is whether your site collects personal data through cookies, and for what. The PDPC's guidance says consent isn't needed for cookies that don't collect personal data, but it is needed where personal data is collected, and specifically where behavioural targeting involves collecting and using personal data (PDPC Advisory Guidelines on the PDPA for Selected Topics, section 6, revised 31 Aug 2018, checked 9 Nov 2026). So the real job is finding out what your site loads. We're not lawyers, and this is general information rather than legal advice.

What a cookie is, briefly

A cookie is a small text file your browser stores for a website. The PDPC describes two kinds: session cookies, which "typically expire at the end of a browser session", and persistent cookies, which stay until they expire or are deleted (para 6.5).

Some cookies keep a site working, such as remembering what's in a booking form or keeping a video playing. Others measure visits or track people across sites for advertising. Those differences matter.

What the PDPC guidance says

From section 6 of the Selected Topics guidelines (the 2018 revision we could read; check the PDPC website for anything newer):

  • Not every cookie needs consent. "Not all cookies collect personal data", and consent isn't needed for those that don't. The PDPC's example is session cookies that "only collect and store technical data needed to play back a video" (para 6.7).
  • Requested activities can involve deemed consent. Where someone voluntarily gives details for something they asked for, such as storing what they type into an online purchase form, consent may be deemed for that purpose (para 6.8).
  • Browser settings count, partly. Someone who sets their browser to accept some cookies and reject others may be taken to consent to the ones accepted. But "the mere failure of an individual to actively manage his browser settings does not imply that the individual has consented" (para 6.9).
  • Behavioural targeting needs consent where it involves collecting and using personal data (para 6.11).
  • The collector is responsible. The duty to get consent "rests with the organisation that is collecting such personal data", including a third party collecting through another organisation's website (para 6.10).

The PDPC also notes that an IP address alone may not identify anyone, but the more data points linked to it, the more likely it becomes personal data (paras 6.1 to 6.3).

The PDPA was amended in 2020, adding further bases for processing such as deemed consent by notification and a legitimate interests exception. These came after the 2018 cookie paragraphs, and whether either fits your particular tracking is a question for a lawyer, not a blog post.

Step one: find out what your site actually loads

Most small business owners don't know, because the cookies arrived with plugins, themes, embedded maps or chat widgets. A quick way to look:

  1. Open your site in Chrome in a private window.
  2. Open DevTools (right-click, Inspect), go to the Application tab and look under Cookies for your domain and any others listed.
  3. Note each third-party name you recognise: analytics tools, advertising pixels, social media embeds, video embeds, chat widgets.
  4. Ask whoever built your site what each one is for, and whether it's still needed.

It's common to find tools nobody uses any more, such as an old ad pixel from a campaign that ended years ago. Removing what you don't need is the simplest privacy improvement there is, and it often makes the site faster too.

Which situation are you in?

What your site loads What it suggests
Only cookies the site needs to work (forms, security, a video player) A banner is probably not needed for these; explain them in your privacy notice
Analytics to count visits Grey area; depends on what's collected and how. Be open about it, and take advice if unsure
Advertising pixels, retargeting or cross-site tracking Consent is likely needed under the guidance on behavioural targeting
Third-party embeds that set their own cookies Check what they collect; the PDPC puts responsibility on whoever collects

If you deliberately target visitors in the EU or elsewhere, stricter local rules may apply. That's another reason to get advice rather than copy someone else's banner.

If you do use a banner, make it honest

A banner that only says "This site uses cookies. OK" doesn't do much. Given para 6.9's point that doing nothing isn't consent, a useful banner:

  • says plainly what the non-essential cookies are for (for example, "to measure visits" or "to show you our ads on other sites");
  • lets people say no as easily as yes;
  • doesn't load the tracking until someone agrees;
  • links to a privacy notice written in plain English;
  • doesn't cover your contact details or enquiry button on a phone screen.

Whatever you decide about banners, keep a privacy notice that explains what you collect through the site, why and who to contact. People should be able to find it from every page.

A hypothetical example

[Business name], a tuition centre, finds four third-party tools on its site: analytics, an embedded map, a chat widget it stopped using last year and an advertising pixel from a campaign two years ago. It removes the chat widget and the old pixel, updates its privacy notice to explain the analytics and map, and asks a lawyer whether its analytics set-up needs consent. The site gets simpler, and the centre can actually explain what it does with visitor data.

What's in your control, and what isn't

In your control: what your site loads, removing tools you don't need, how clearly you explain your cookies and whether you ask before tracking.

Not in your control: how the PDPC or a court would view a specific set-up. Guidance can change, and the 2018 paragraphs pre-date the 2020 amendments. If you rely heavily on advertising tracking, or serve visitors outside Singapore, get proper legal advice.