PDPA & Customer Data: What Singapore SMEs Must Know Before Using AI

In October 2025, the PDPC fined Marina Bay Sands S$315,000 after a breach exposed the personal data of 665,495 patrons — and the root cause was a manual process with a single point of failure (Recording Law citing PDPC, 2025). If you run an AI agent that chats with customers, the short answer is this: every message it captures is regulated personal data under Singapore's PDPA, and you are legally responsible for it. This guide translates the law into a checklist you can actually use — consent, chat logs, NRIC, and the WhatsApp marketing rules most SME blogs get wrong.

Does the PDPA apply to my AI chatbot?

Yes — completely. Singapore's Personal Data Protection Act 2012 (PDPA) governs how any organization collects, uses, discloses, stores, and transfers customer personal data, and an AI agent that chats with customers does all five of those things. The law is administered and enforced by the Personal Data Protection Commission (PDPC), a body under the Infocomm Media Development Authority (IMDA).

There is no "it's just a bot" exemption. The moment a customer types their name, phone number, booking details, or any other identifying information into your chat widget, you have collected personal data and the full set of obligations kicks in. The technology is new; the law treats it like any other data-collection channel you operate.

This matters because the penalties are real. Since the 2020 PDPA amendments, the PDPC can impose financial penalties of up to S$1 million, or 10% of your annual Singapore turnover, whichever is higher (ICLG Data Protection 2025-2026, Singapore). For a small business, even a fraction of that is existential.

It also matters because regulators have shifted from warnings to enforcement. The PDPC has issued AI-specific guidance — the Advisory Guidelines on AI Recommendation and Decision Systems (Mar 2024) and the Guidelines on Securing AI Systems (Oct 2024) — which tells you the direction of travel: the regulator now expects organizations deploying AI to have thought about data protection up front. Treating your chatbot as outside the rules is the fastest way to end up on the wrong side of a decision.

What are the PDPA obligations for a chatbot, in plain English?

There are ten data protection obligations currently in force under the PDPA, and your chatbot triggers nearly all of them. The PDPC's official "Data Protection Obligations" page groups them under three themes: collection of personal data, care of personal data, and the individual's autonomy over their own data (pdpc.gov.sg, published Apr 2023).

A note on counting, because it trips people up: many commercial guides advertise "11 obligations" by including Data Portability. That eleventh obligation was passed in the Personal Data Protection (Amendment) Act 2020 but is not yet in force pending regulations (confirmed by CMS and Withers, 2025-2026). The legally accurate count of in-force obligations is ten.

Here is how each one maps to an AI agent handling customer conversations:

The three you are most likely to overlook are Retention Limitation, Transfer Limitation, and Accountability. We'll come back to each.

Do I need consent before my AI agent collects customer data?

Yes — the Consent and Notification Obligations require you to tell customers what data you're collecting and why, before or at the point of collection, and to obtain their consent unless a valid exception applies. In practice, that means a short, visible notice when the chat opens: what you capture, what you'll use it for, and a link to your privacy policy.

The Purpose Limitation Obligation is where SMEs most often slip up. If a customer gives you their phone number to confirm a table reservation, you collected it for that booking — you cannot later blast that number with promotional offers without fresh consent. Data collected for one purpose stays locked to that purpose.

The PDPC has also clarified how this works for AI specifically. On 1 March 2024, it published the Advisory Guidelines on Use of Personal Data in AI Recommendation and Decision Systems (pdpc.gov.sg/guidelines-and-consultation/2024/02). These explain when you can rely on the Business Improvement and Research exceptions, and set out best practices for transparency and vendor management when you use a third-party AI developer. They are not legally binding, but the PDPC has stated it will enforce the PDPA consistently with them (Lexology, Bird & Bird, Rajah & Tann, 2024). One important limit: these guidelines explicitly do not cover generative-AI training and deployment use cases, so don't treat them as blanket cover for everything an LLM-based agent does.

How long can I keep chat logs, and where can they be stored?

You must stop retaining chat logs once the purpose for collecting them has been served — that's the Retention Limitation Obligation. There is no fixed "keep for X years" rule; the test is whether you still genuinely need the data for the purpose you collected it. A booking confirmed and completed three months ago usually does not justify holding that conversation forever.

This is the obligation most chatbot setups quietly fail, because logs accumulate by default. Build a deletion schedule into your process: decide a retention window for each type of conversation, and actually purge on that cadence rather than hoarding everything "just in case."

Where the data lives matters too. Many AI and LLM tools host data overseas, which engages the Transfer Limitation Obligation — overseas transfers require comparable protection or appropriate contractual safeguards. Before you sign with any vendor, ask three questions:

1. Where are chat logs physically stored, and in which countries?
2. What security measures protect them, and is there multi-factor authentication on admin access?
3. Will you sign a data processing agreement that commits to PDPA-comparable protection?

The Protection Obligation is not theoretical. Beyond the Marina Bay Sands fine, the PDPC fined Air Sino-Euro Associates Travel S$47,000, citing inadequate security, outdated systems, and no multi-factor authentication (Recording Law citing PDPC, 2025). "Reasonable security arrangements" means real controls, not good intentions. If you're weighing tools, our guide on customer data privacy for AI in SMEs walks through the vendor questions in more depth.

Can my chatbot collect or use NRIC numbers?

Be very careful here — and the rule is changing fast. As of the latest PDPC guidance, you must never use NRIC numbers as passwords or for authentication, and you should avoid collecting them at all unless genuinely necessary. NRIC numbers remain subject to the full set of PDPA obligations even though they're widely known.

The timeline matters. After ACRA's revamped Bizfile portal launched on 9 December 2024 and full NRIC numbers became searchable, the Ministry of Digital Development and Information stated on 13 December 2024 that an NRIC number is "a unique identifier" that is "assumed to be known, just as our real names are known" (MDDI reply, acra.gov.sg). The next day, on 14 December 2024, the PDPC clarified that NRIC numbers must not be used for authentication but remain protected under the PDPA (Mothership; Online Citizen, Dec 2024).

Then it got firmer. On 26 June 2025, the PDPC and the Cyber Security Agency issued a joint advisory against using NRIC numbers for authentication. And on 2 February 2026, the PDPC announced that all private organizations must stop using full or partial NRIC numbers for authentication by 31 December 2026, with stepped-up enforcement — directions and financial penalties — from 1 January 2027 (pdpc.gov.sg press release). The practical rule for your chatbot is simple: never use NRIC as a login, verification credential, or default password; don't ask for it unless you truly need it; and if you do hold it, protect it strongly.

Do the DNC and WhatsApp marketing rules apply to my AI agent?

Yes — and this is the single most misunderstood point in Singapore SME content. The Do-Not-Call (DNC) provisions in Part 9 of the PDPA apply to telemarketing sent via WhatsApp and Telegram, because those apps use a telephone number as an identifier (PDPC, Individual's Guide to the DNC Registry). Plenty of blogs wrongly imply WhatsApp marketing is unregulated. It isn't.

Before sending a marketing "specified message" to a Singapore phone number, you must check the relevant DNC register — a check is valid for 30 days — unless you have the recipient's clear and unambiguous consent, or an exemption applies. The common exemptions are an ongoing relationship, transactional messages (order and delivery updates, warranty info), and genuine B2B messages. To screen numbers, you open a DNC account for a one-time S$30 (or S$60 from overseas).

Here's a clean way to think about which messages are which:

• Transactional and allowed — booking confirmations, order-status updates, delivery alerts, appointment reminders. These keep your AI agent useful without tripping the DNC rules.
• Marketing and regulated — promotions, discount blasts, "we miss you" win-back campaigns. These need consent or a valid DNC check first.
• Separate regime to know — the Spam Control Act 2007, enforced by IMDA, governs bulk unsolicited commercial email, SMS, and fax, and requires clear sender identification plus a working opt-out. WhatsApp sits outside the Spam Control Act's technical scope but is still caught by the PDPA's consent and DNC rules (marketingagency.sg, 2026).

The teeth are real: the first PDPA DNC prosecution, Star Zest Tuition (2014), drew a S$39,000 fine, and DNC breaches can attract financial penalties up to S$1 million. The good news is that an AI agent built to take actions — confirming bookings, routing leads, sending order updates — lives almost entirely in transactional territory, where you're on solid ground. If channel choice is on your mind, see how to choose the right messaging channel for an AI agent.

What should an SME owner actually do first?

Start with the four things that carry the highest penalty risk and the lowest effort to fix. You don't need a law firm on retainer to get the basics right; you need a short notice, a deletion habit, a named person, and clean marketing consent.

Concretely, in priority order:

1. Add a chat-open notice stating what you collect and why, with a privacy-policy link — this satisfies Consent and Notification in one move.
2. Appoint a Data Protection Officer and publish their contact details. The Accountability Obligation requires a DPO with publicly available contact info; for a small business this can be an existing staff member, not a new hire.
3. Set a retention schedule for chat logs and actually delete on it, so you satisfy Retention Limitation instead of hoarding data you no longer need.
4. Separate transactional from marketing messages and only run promotions to numbers with consent or a valid 30-day DNC check.

Tools matter here, because the platform you pick either helps you comply or quietly makes it harder. Omago, an AI agent platform that helps SMEs automate customer conversations across WhatsApp, Telegram, and web chat, is the kind of tool where you'll want to confirm the vendor answers the storage, security, and data-processing-agreement questions above before you commit. The point isn't the brand — it's that an AI agent which takes actions (capturing and routing leads, running guided multi-step flows) touches a lot of personal data, so compliance has to be a buying criterion, not an afterthought.

Be clear-eyed about what AI can and cannot do for compliance. An AI agent can enforce a clean consent flow, keep transactional and marketing traffic separate, and apply consistent handling — that genuinely reduces human error of the kind that caused the Marina Bay Sands breach. What it cannot do is take responsibility off your shoulders: you remain the organization the PDPC holds accountable. It also cannot interpret the law for you in genuinely novel situations — a bot that confidently tells a customer "we don't need consent for that" is a liability, not a compliance feature.

One last thing worth saying plainly, because the hype machine tends to skip it: deploying an AI agent does not make your data footprint smaller — if anything it grows, because the bot is now collecting and logging conversations around the clock, including after hours when no human is watching. That's exactly why the boring obligations — retention, transfer, and protection — deserve the most attention. Get the consent notice, the deletion schedule, the named DPO, and the marketing-message separation in place first, and you'll have covered the four things that drive almost every PDPC enforcement action against a small business. For the bigger picture on staying on the right side of regulators, our AI governance guide for small businesses ties these threads together.

Frequently Asked Questions

Is my chatbot PDPA compliant by default?

No. Compliance depends on how you configure and operate it, not on the software itself. At minimum you need a collection notice, a lawful basis (consent or a valid exception), secure storage of chat logs, a retention and deletion schedule, and a published DPO contact. The tool can make these easy, but the legal responsibility sits with you as the organization.

Do I need a Data Protection Officer for a small business?

Yes. The PDPA's Accountability Obligation requires every organization to appoint at least one DPO and make their contact details publicly available (pdpc.gov.sg). There is no exemption for small size. The DPO can be an existing employee — for many SMEs it's the owner or an office manager — so this is a process step, not a new salary.

Can my AI agent message customers on WhatsApp without consent?

Only for transactional messages like booking confirmations and order updates. Marketing messages sent via WhatsApp or Telegram are caught by the PDPA's DNC rules because those apps use a phone number as an identifier (PDPC, Individual's Guide to the DNC Registry). For promotions you need the recipient's clear consent or a valid DNC register check, which stays valid for 30 days.

What happens if my chatbot has a data breach?

The Data Breach Notification Obligation, in force since 1 Feb 2021, requires you to notify the PDPC within 3 calendar days of assessing a notifiable breach — one that causes significant harm or affects 500 or more individuals — and to notify the affected individuals. Penalties for protection failures can reach up to S$1 million or 10% of annual Singapore turnover (ICLG 2025-2026), as the S$315,000 Marina Bay Sands fine over 665,495 patrons shows (PDPC, Oct 2025).

Can I ask for NRIC numbers in chat?

Avoid it unless genuinely necessary, and never use NRIC for authentication or as a password. From 31 December 2026, all private organizations must stop using full or partial NRIC numbers for authentication, with enforcement from 1 January 2027 (pdpc.gov.sg press release, 2 Feb 2026). If you do hold NRIC data for a legitimate reason, the full PDPA protection obligations apply and you must secure it strongly.

Sources: PDPC Data Protection Obligations (pdpc.gov.sg, 2023); PDPC Advisory Guidelines on Use of Personal Data in AI Recommendation and Decision Systems (1 Mar 2024); PDPC press release on NRIC authentication (2 Feb 2026); PDPC Individual's Guide to the DNC Registry; Recording Law citing PDPC (2025); ICLG Data Protection 2025-2026, Singapore; CMS Expert Guide and Withers (2025-2026); MDDI reply via acra.gov.sg (Dec 2024); Mothership and Online Citizen (Dec 2024); marketingagency.sg (2026).