TRW & Co · PDPA and data protection
Cookie Consent and Online Tracking Under the PDPA

Cookie consent in Singapore is governed by the PDPA, not a cookie law. Consent is needed only where cookies collect personal data, and deemed consent can cover cookies for services users request. But the PDPC says targeted advertising through cookies collecting personal data requires consent, so most commercial sites need real on-site preference controls.
Key pointThe PDPC states that failing to manage browser settings does not imply consent, and that consent is required for ad targeting through cookies collecting personal data. A one-button 'OK' banner rarely proves valid consent for advertising tags.
At a glance
No standalone cookie law
Singapore regulates cookies through the PDPA's consent and notification obligations; cookies that do not collect personal data need no consent under PDPC guidance.
Requested services deemed consented
Cookies needed for activities users request, such as login, security, carts and preferences, may be covered by deemed consent where the purpose is clear.
Advertising needs consent
The PDPC says targeted advertising using cookies that collect personal data requires consent, and recommends on-site preference settings to enable or disable such cookies.
Browser defaults are not consent
Consent may be shown by deliberate browser configuration, but the PDPC states that failing to manage browser settings does not imply consent to all websites.
Notification route has limits
Deemed consent by notification requires a documented adverse-effect assessment and a reasonable opt-out period, and cannot be used for sending direct marketing messages.
Swipe or scroll →
The short answer: do you need a cookie banner in Singapore?
Not always. Singapore has no cookie-specific statute, and the rules on cookie consent in Singapore come from the general consent obligation in the Personal Data Protection Act 2012 (PDPA). Consent is needed only where a cookie or tracker collects, uses or discloses personal data. Cookies that collect no personal data need no consent, and cookies needed for activities the user has clearly requested may be covered by deemed consent.
The harder cases are analytics, advertising and third-party tracking. The PDPC's Advisory Guidelines on the PDPA for Selected Topics (revised 17 May 2022) state that where targeted advertising involves collecting and using personal data through cookies, the individual's consent is required. As good practice, the PDPC says organisations should let users set cookie preferences on the website to enable or disable advertising cookies.
So a banner is not mandatory, but for most commercial websites using marketing pixels, cross-site tracking or behavioural profiling, a preference tool is the most practical way to show valid consent. This guide explains when cookies collect personal data, how deemed consent works, and how to design a banner that stands up.

The legal framework: PDPA consent and PDPC guidance
The PDPA requires organisations to obtain consent before collecting, using or disclosing personal data, unless deemed consent or an exception applies, and to notify individuals of the purposes. Personal data means data from which an individual can be identified, alone or together with other information the organisation has or is likely to have access to. That definition is what decides whether a cookie is regulated.
Two PDPC documents do most of the work. Chapter 7 of the Selected Topics guidelines addresses online activities, IP addresses and cookies. The Advisory Guidelines on Key Concepts in the PDPA explain consent, deemed consent by conduct, deemed consent by notification and the exceptions. The guidelines are advisory, but the PDPC applies them in enforcement, and the courts have engaged with the same consent concepts.
The stakes are significant. Since 1 October 2022, the PDPC may impose financial penalties of up to the higher of S$1 million or 10% of annual turnover in Singapore for organisations whose turnover there exceeds S$10 million. Individuals who suffer loss directly from a contravention may also sue under the PDPA's private action provision.
When do cookies collect personal data?
The PDPC's starting point is that not all cookies collect personal data. Its guidelines give the example of session cookies that store only technical data needed to play a video. Consent is not needed for cookies that do not collect personal data.
The analysis changes once identifiers are linked. The PDPC notes that an IP address or tracking cookie may be matched with browsing history, purchase history, postal code, mobile numbers and shopping preferences so that an individual can be identified. It also observes that an IP address viewed in isolation may not be personal data, but the more data points an organisation associates with a unique IP address over time, the more likely an individual becomes identifiable.
In practice, logged-in experiences, CRM-linked analytics, advertising pixels that match hashed emails, and long-term behavioural profiles will usually involve personal data. Aggregated, unlinked analytics with short retention may not. The answer depends on your actual data flows, which is why a tag audit is the first step in any review of cookie consent in Singapore.
| Cookie or tracker | Typical PDPA position | Practical approach |
|---|---|---|
| Strictly technical session cookies (no personal data) | No consent needed (Selected Topics para 7.9) | Disclose in the privacy or cookie notice for transparency |
| Cookies for requested activities: login, security, cart, preferences, streaming | Consent may be deemed where the user knows the purpose and voluntarily provides data (para 7.10) | Explain purposes clearly; no opt-in toggle usually needed |
| First-party analytics linked to accounts or identifiers | Personal data likely collected; consent or a valid basis needed | Notify purposes; offer controls; consider deemed consent by notification after assessment |
| Advertising, retargeting and cross-site tracking | Consent required where personal data is collected and used (para 7.14) | Provide on-site preference settings to enable or disable |
| Third-party pixels and SDKs | Collecting party must obtain consent (para 7.13); website operator may also be collecting | Map who collects what; contract for compliance; gate tags behind consent |
Beyond cookies: apps, SDKs and fingerprinting
The same principles apply to trackers that are not technically cookies. The PDPC's guidelines list device fingerprints, hashed email addresses, customer IDs and IP addresses among the identifiers generated during online activity. Mobile app SDKs, advertising identifiers, server-side tagging and fingerprinting scripts can all collect personal data, often more persistently than a browser cookie.
Teams sometimes move tracking server-side or into apps on the assumption that cookie consent in Singapore only concerns browser cookies. That is a mistake. The PDPA question is always whether personal data is collected, used or disclosed and on what basis, whatever the technology. Consent tools for apps should cover SDKs, and server-side tags should respect the same user choices as their browser equivalents.
Deemed consent and browser settings
Deemed consent by conduct
Paragraph 7.10 of the Selected Topics guidelines says that for internet activities the user has clearly requested, there may be no need to seek separate consent where the individual is aware of the purposes and voluntarily provided the data. The PDPC's examples include storing what a user enters in a web form to complete an online purchase, and reasonable activities that cannot take place without cookies, such as authentication and security, user preferences, network management and streaming content.
This is narrower than it looks. The 2025 High Court decision in Piper v Singapore Kindness Movement stressed that deemed consent extends only to what the purpose genuinely requires. A login cookie is covered; reusing login data to build an advertising profile is not.
Browser settings are not blanket consent
The PDPC accepts that consent may be reflected in how a user configures their browser: a user who accepts cookies only from their bank and email provider has consented to those sites. But it adds a critical limit: the mere failure of an individual to actively manage browser settings does not mean they have consented to collection by all websites. Default browser settings are therefore weak evidence of cookie consent in Singapore.
Deemed consent by notification
Since the 2020 amendments, organisations may also rely on deemed consent by notification: the individual is told of the purpose and how to opt out, and does not opt out within a reasonable period. The PDPC's assessment checklist requires the organisation first to assess whether the processing is likely to have an adverse effect on the individual, consider mitigating measures, and proceed only if no residual adverse effect remains. The checklist notes that this basis cannot be relied on for sending direct marketing messages, and it recommends direct forms of notification by default.
For analytics, deemed consent by notification can be a sensible middle path: a clear notice, a working opt-out and a documented assessment. For targeted advertising, the PDPC's specific statement that consent is required, plus the direct marketing restriction, makes reliance on notification risky.
The PDPC places the consent obligation on the organisation actually collecting the data. If a third-party ad platform collects personal data through your site, it must obtain consent, but if you also receive or use that data, you are collecting too. Gate third-party tags behind your consent tool rather than assuming the platform has it covered.
Designing a banner for cookie consent in Singapore
A well-designed banner for cookie consent in Singapore is evidence. If the PDPC or a court later asks how consent was obtained, the answer should be visible in the interface and in logs. The following steps reflect the PDPC guidance and the practical lessons from regimes with stricter rules.
- Audit every tag. List cookies, pixels, SDKs and server-side tags, who sets them, what data they collect, whether it is linked to identifiers, and retention periods.
- Classify by purpose. Group into strictly necessary or requested-service cookies, analytics, functional enhancements, and advertising or cross-site tracking.
- Choose the basis for each group. Use deemed consent for requested services, documented deemed consent by notification where appropriate, and express consent for advertising.
- Write a plain notice. Explain each purpose, the third parties involved and how to change preferences. Link it from the banner and the privacy notice.
- Build real controls. Offer toggles per category, make declining as easy as accepting, and ensure tags actually fire only after the relevant choice.
- Log and test. Record consent choices with timestamps and banner versions, and test regularly that declined tags do not load.
- Review on change. Re-run the audit when marketing adds a new pixel, the site is redesigned, or a new market is added.
Illustrative scenario: an e-commerce retailer's tag audit
The following scenario is illustrative only and does not describe any real client or outcome.
A Singapore online retailer runs its storefront with a cart cookie, a login cookie, a first-party analytics tool, two advertising pixels and a chat widget. Its existing banner says 'By using this site you accept cookies' with a single 'OK' button, and every tag fires on page load.
A tag audit finds that the advertising pixels match hashed email addresses from the checkout, so they collect personal data. The retailer redesigns the flow: cart, login and security cookies run under deemed consent with a clear notice; analytics runs after a documented deemed consent by notification assessment with a working opt-out; advertising pixels are blocked until the user switches them on in a preference centre. Consent choices are logged against the banner version.
The point is not that one design fits every site, but that the retailer can now show, purpose by purpose, why each tag is lawful. For more on online selling obligations, see our e-commerce regulation practice.
Risks and common mistakes
Treating 'continued browsing' as consent for everything
A notice saying that continued use of the site means acceptance of all cookies may be enough for requested-service cookies where users understand the purpose, but it is weak for advertising and cross-site tracking. The PDPC has said consent is required for targeting through cookies that collect personal data, and that a failure to manage browser settings does not imply consent.
Where personal data feeds advertising, give users a genuine choice on the site. That approach also aligns more closely with the stricter EU and UK regimes, which makes a single global design easier to maintain.
Cookie walls that block access unless users accept all
The PDPA prohibits requiring consent, as a condition of providing a product or service, beyond what is reasonable to provide that product or service. Consent obtained in breach of that rule is not valid.
A wall forcing acceptance of advertising cookies to read a news article or browse a catalogue is therefore hard to defend. If the business model depends on advertising, consider alternatives such as contextual advertising or a clearly explained subscription option, and take advice on how the reasonableness test applies.
Forgetting children and young users
In March 2024 the PDPC issued Advisory Guidelines on the PDPA for Children's Personal Data in the Digital Environment, aimed at services likely to be accessed by children. They emphasise data minimisation, high-privacy defaults and care with features such as precise geolocation.
Platforms used by young people should review whether behavioural advertising and profiling cookies are appropriate at all, how consent is obtained, and whether parental involvement is needed. Our guide to children's data covers the guidelines in more depth.
Assuming the vendor handles compliance
Consent management platforms and ad platforms often market themselves as 'PDPA compliant'. The tools may be good, but they are only as compliant as their configuration. Misconfigured tags that fire before consent, or categories mislabelled as necessary, are the most common failures.
Contract with vendors for accurate classification, configuration support and audit rights, and keep your own records of what is deployed. Where data leaves Singapore, check the transfer limitation obligation, discussed in our cross-border transfers guide.
Cross-border angle: the EU, the UK and other markets
Singapore's approach is more flexible than the EU and UK, where electronic communications rules generally require prior consent for storing or accessing non-essential cookies on a user's device, regardless of whether personal data is involved. A Singapore company that targets EU or UK users may need to meet those stricter standards for that traffic.
Many regional groups operating across Singapore, the UK, the UAE, China and Bangladesh adopt one consent design that meets the strictest market they serve, then relax it where local law allows. That reduces engineering effort and audit risk. Where PDPA consent is the only regime in play, the practical floor for cookie consent in Singapore remains: no personal data, no consent; requested services, deemed consent; advertising, user choice.
Checklist: cookie consent in Singapore
- Complete a tag audit and identify which cookies collect or link to personal data.
- Map each group to a basis: no consent needed, deemed consent, deemed consent by notification, or express consent.
- Document any deemed consent by notification assessment using the PDPC checklist.
- Provide on-site preference settings for advertising and tracking cookies.
- Avoid cookie walls that demand consent beyond what the service reasonably requires.
- Check whether children are likely users and apply the 2024 guidelines.
- Align notices with your privacy policy and your wider consent framework.
For a review of your tags, banner and notices against the PDPA, or help building a single design for several markets, speak to our data protection team or contact TRW & Co. We also advise on AI governance where tracking data feeds personalisation models.
Frequently asked questions
01Is a cookie banner required by law in Singapore?
No statute requires a cookie banner as such. The PDPA requires consent and notification of purposes where cookies collect, use or disclose personal data. Cookies that collect no personal data need no consent, and cookies for services the user requests may rely on deemed consent. However, the PDPC says targeted advertising through cookies collecting personal data requires consent and recommends on-site preference settings. For most commercial sites using advertising or tracking tags, a banner with a preference centre is the practical way to obtain and evidence that consent.
02Are cookies personal data under the PDPA?
Sometimes. A cookie identifier or IP address viewed in isolation may not identify anyone, but the PDPC notes that once it is linked to browsing history, purchase history, contact details or account data, an individual may become identifiable and the data becomes personal data. The more data points linked to an identifier over time, the more likely it is personal data. Logged-in tracking, CRM-linked analytics and pixels matching hashed emails will usually involve personal data, so a tag-by-tag audit is needed.
03Do analytics cookies need consent in Singapore?
It depends on whether they collect personal data. Aggregated analytics that do not identify individuals may need no consent. Analytics linked to accounts, identifiers or long-term profiles usually involve personal data, so you need consent or another valid basis. Many organisations use deemed consent by notification for analytics, which requires a documented assessment showing no residual adverse effect, a clear notice and a reasonable opt-out period. Advertising-related analytics are better treated as requiring consent.
04Can I rely on browser settings for cookie consent?
Only to a limited extent. The PDPC accepts that a user who deliberately configures their browser to accept some cookies and reject others may have consented to the cookies accepted. But it states that the mere failure to actively manage browser settings does not imply consent to collection by all websites. Because most users never change defaults, relying on browser settings alone is weak evidence, particularly for advertising or cross-site tracking.
05Who is responsible for consent when third-party pixels collect data on my website?
The PDPC places the consent obligation on the organisation that collects the personal data, whether directly or through data intermediaries. If a third-party platform collects data through your site and you do not, the third party must obtain consent. In practice, website operators often receive or use the resulting data, making them collectors too. The safer approach is to map who collects what, gate third-party tags behind your consent tool, and allocate responsibilities in your contracts.
06Are cookie walls allowed under the PDPA?
There is no specific ban, but the PDPA prevents organisations from requiring consent, as a condition of providing a product or service, beyond what is reasonable to provide it. Consent extracted in breach of that rule is invalid. A wall forcing users to accept advertising cookies just to read content or browse products is therefore difficult to justify. Organisations relying on advertising should consider less intrusive alternatives and take advice on how the reasonableness test applies to their model.
Sources and official materials
- Personal Data Protection Act 2012 — Consent, notification and deemed consent obligations
- PDPC: Advisory Guidelines on the PDPA for Selected Topics — Chapter 7 on online activities, IP addresses and cookies
- PDPC: Advisory Guidelines on Key Concepts in the PDPA — Consent, deemed consent and exceptions
- PDPC: Assessment Checklist for Deemed Consent by Notification — Adverse-effect assessment and opt-out period
- PDPC: Amendments to enforcement (2022) — Financial penalty cap from 1 October 2022
General information only, current as at 20 October 2026. It is not legal advice and does not create a lawyer–client relationship. Singapore law and regulatory practice change; check current official sources and take advice on the facts of your matter.



