The Personal Data Protection Act applies whenever an automated workflow collects, uses or discloses personal data. Before launch, confirm you have a clear purpose and valid consent, collect only what you need, protect the data, control retention and overseas transfers, and know who is responsible for handling access requests and data breaches.
This guide is general information, not legal advice. Have your legal adviser review any workflow that touches personal data.
Where the PDPA meets automation
Chatbots, lead engines, HR workflows and invoice automation often handle names, emails, phone numbers or other personal details. The PDPA applies to that data however it is processed, so the rules apply to automated workflows as much as to manual ones.
The checklist
| Obligation | What it means for your workflow | Practical step |
|---|---|---|
| Purpose and consent | Use personal data only for stated purposes, with consent where required | Write down the purpose for each workflow and how consent is obtained |
| Notification | Tell people why their data is collected | Add clear notices to forms and chat windows |
| Collect only what you need | Do not gather data without a reason | Remove unneeded fields from forms and prompts |
| Protection | Keep the data secure | Use encryption, access controls and logging |
| Retention | Do not keep data longer than needed | Set deletion rules for chats, files and logs |
| Overseas transfers | Data sent abroad must be protected to a comparable standard | Check where your AI and cloud providers process data |
| Access and correction | People can ask to see or correct their data | Know where the data lives and who handles requests |
| Data breaches | Some breaches must be assessed and notified | Have an incident plan and contact list |
| Accountability | Someone is responsible | Appoint a data protection officer and keep policies current |
Working with AI providers
- Ask where data is processed and stored.
- Ask whether your data is used to train the provider’s models.
- Agree retention and deletion terms in the contract.
- Ask about sub-processors and security certifications.
- Confirm who is responsible for what, in writing.
Marketing messages and Do Not Call rules
If a workflow sends marketing calls or text messages to Singapore numbers, the Do Not Call Registry provisions may apply. Check the current rules before you switch on outreach automation.
Document it
- A map of what personal data each workflow handles
- The purpose and legal basis for each use
- Retention periods and deletion steps
- The list of vendors and where they process data
- Who approved the workflow and when
Frequently asked questions
Does the PDPA apply to chatbots?
Yes, whenever a chatbot collects, uses or discloses personal data, such as names, contact details or account information.
Do we need consent to use AI on customer data?
It depends on the purpose and on exceptions in the law. Confirm with your legal adviser before you launch.
Who is responsible, us or the AI vendor?
Organisations remain responsible for personal data in their possession or control. Vendors may have their own obligations, so set out roles clearly in your contract.
Do we need a Data Protection Officer?
Under the PDPA, organisations in Singapore must appoint at least one person responsible for data protection, and make their business contact details available. Check the PDPC’s guidance for the details.
Can personal data be sent to AI providers overseas?
It can, but the PDPA’s transfer limitation obligation applies: you must make sure the data stays protected to a comparable standard, usually through contract terms with the provider.