
PDPA Compliance for Singapore SMEs: What Your ERP and AI Agents Must Do
PDPA compliance for a Singapore SME is mostly a systems problem: your customer records, ERP, CRM, HR files and AI tools must be able to show what personal data you hold, why you hold it, who can see it and when it will be deleted. The Personal Data Protection Act carries penalties of up to 10% of annual gross turnover in Singapore or S$1 million, whichever is higher, according to a JD Supra summary of the amendments. This guide translates the obligations into what your systems must do, including when an AI agent reads personal data. It is general information, not legal advice.
What does the PDPA require in operational terms?
It requires you to control the full life of personal data: collect it with consent, use it only for stated purposes, keep it accurate and secure, transfer it responsibly, delete it when it is no longer needed and respond to breaches quickly. The table turns each main obligation into a system requirement and the evidence you should be able to produce.
| Obligation | What your systems must do | Evidence to keep |
|---|---|---|
| Consent and purpose | Capture consent where it is collected, record the purpose, and stop other uses without new consent | Consent record per person, with date and purpose |
| Accuracy | Validate data at entry and update it when people tell you about changes | Change history on customer and employee records |
| Protection | Limit access by role, protect sensitive fields and log who accessed what | Access list, audit log, review dates |
| Retention limitation | Apply defined retention periods and archive or delete on schedule | Retention policy and deletion records |
| Transfer limitation | Know which cloud services and models hold data outside Singapore and protect it by contract | Vendor list with data locations and contract terms |
| Access and correction | Locate and produce everything held about one person, and process corrections | Request log with response dates |
| Breach management | Detect, assess, contain and report breaches within the legal timeline | Incident plan and breach register |
| Accountability | Appoint a data protection officer and publish contact details | Named officer and a published contact |
How fast must a data breach be reported?
Notify the PDPC no later than three calendar days after you determine that the breach is notifiable. A breach is notifiable if it causes, or is likely to cause, significant harm to individuals, or if it affects 500 or more individuals. Affected individuals must be told as soon as practicable if the breach is likely to cause them significant harm, and a data intermediary must tell the organisation it works for without undue delay once it has credible grounds to believe a breach occurred, according to JD Supra and Baker McKenzie. The clock starts when you determine notifiability, so you need to be able to assess scope fast. That depends on audit logs and a rehearsed incident process.
Which systems hold most of your personal data?
- CRM and customer records. Consent capture, marketing preferences, retention by customer status, role-based access and an audit log. You must be able to extract everything held about one person.
- HR and payroll. Employee identification numbers, bank details and health information need the same access control, logging and retention rules, with extra care for sensitivity.
- Website and e-commerce. Consent captured on forms and checkouts must reach the operational system, or the record will not match what the customer agreed to.
- ERP. Customers, suppliers, delivery addresses and contacts sit in sales, purchasing and accounting records. The ERP is often where role-based access and audit trails are easiest to enforce.
Does the PDPA apply when an AI agent reads personal data?
Yes. If the data is personal data, the same obligations apply whether a person or an AI agent reads it. An agent that drafts customer emails, reconciles invoices or answers staff questions can touch personal data, so it needs to be inside your controls, not beside them.
- Purpose. Use an agent only for tasks consistent with the purposes the individual agreed to.
- Access. Give the agent its own identity with the minimum permissions for its task, so its actions can be logged and limited. See why AI agents need ERP guardrails.
- Transfers. If the agent sends data to a model hosted outside Singapore, treat it as a transfer and check the contract terms.
- Vendors. If an AI provider processes personal data on your behalf, check whether it acts as your data intermediary and what the contract requires of it. The PDPA keeps you responsible for personal data processed on your behalf, so take legal advice on the contract.
- Staff tools. Unapproved AI tools are a data leak route. Read our guide to shadow AI.
What breaks without system-level controls: staff export customer lists to personal spreadsheets, someone pastes customer details into an unapproved AI tool, nobody can find all the data held about one person within the response time, and a breach is discovered days later with no log to show what was accessed.
What are five practical steps to get compliant?
- Map your personal data. List what you collect, where it is stored, why, and who can access it. Expect to find data in old email archives, personal laptops and legacy backups.
- Audit consent. Check that every collection point records consent and purpose, and that the record is retrievable.
- Review access. Remove access that staff no longer need, including former employees, and add logging where it is missing.
- Set and apply retention rules. Define a period for each data category and automate deletion or archiving where the system allows.
- Write and rehearse a breach plan. Name who assesses a breach, who decides notifiability and who contacts the PDPC, so that the three-day limit is realistic.
What no system can own: the decision about what purposes you tell people about, the legal assessment of a specific breach and the contract terms with your vendors. Those need a named person in your business and, where uncertain, legal advice.
Frequently asked questions
What is the maximum PDPA financial penalty?
Up to 10% of annual gross turnover in Singapore or S$1 million, whichever is higher, according to a JD Supra summary of the amendments. Confirm the current position with the PDPC.
How quickly must I report a data breach?
Notify the PDPC no later than three calendar days after you determine the breach is notifiable. A breach is notifiable if it is likely to cause significant harm or affects 500 or more individuals.
Does the PDPA apply to small businesses?
Yes. The PDPA applies to organisations that collect, use or disclose personal data in Singapore, whatever their size. Small businesses with customer, staff or supplier records are covered.
Do I need a data protection officer?
Organisations are expected to appoint at least one person responsible for PDPA compliance and make a business contact available. The role can be an existing employee, but it needs time and authority.
Do AI tools change my PDPA obligations?
They do not remove any obligation. They add places where personal data can flow, so you must control access, purpose, overseas transfers and vendor terms for each AI tool or agent.
A question for you: if a customer asked today for everything you hold about them, how many systems would you need to search?
Sources
- JD Supra: Extensive changes to Singapore’s data protection law
- Baker McKenzie: Singapore security requirements and breach notification
- Personal Data Protection Commission Singapore (check current guidance)
By Willie Loo, Managing Director, Mxgsoft Pte Ltd and Moxogo Pte Ltd, Singapore. Last reviewed 10 November 2026. This article is general information and not legal advice.
Next step: pick the one system that holds most of your customer data and test whether you can list everything held about one named person within a day. If you want a second opinion, talk to us about a Resource Master Audit.


