In this guide · 8 sections
- 01What the CSA-IMDA advisory is
- 02Rule 1: what staff must not put into AI tools
- 03Rule 2: approved tools only, and watch the extensions
- 04Rule 3: verify AI output before it leaves the company
- 05Rule 4: people decide, and the account stays secure
- 06One-page staff checklist based on the advisory
- 07Do it yourself or get help?
- 08Frequently asked questions
Short answer
The CSA-IMDA advisory asks people to safeguard their information, verify AI content before using or sharing it, and keep healthy boundaries with AI. For a business, that means: no confidential or personal data in unapproved tools, a human checks every output, and staff only use tools the company has approved.
What the CSA-IMDA advisory is
CSA lists it as advisory AD-2026-008, titled Safe and Secure Use of Generative AI for Individuals, dated 28 July 2026. It is a short two-page PDF. It does not create new legal duties. It is guidance, in the same family as CSA's other public advisories.
It sits next to the PDPC's Advisory Guidelines on Use of Personal Data in Generative AI, published a week earlier. The PDPC guidelines speak to organisations and the PDPA. The CSA-IMDA advisory speaks to the person typing the prompt. A sensible workplace policy needs both: our summary of the PDPC generative AI guidelines covers the organisation side.
| Practice in the advisory | What it asks | Workplace rule |
|---|---|---|
| 1. Safeguard your information | Control what you share; choose tools carefully | Only approved tools; no personal or confidential data without authorisation |
| 2. Verify content | Cross-check with trusted sources; pause before sharing | A named person checks facts, figures and sources before anything leaves the company |
| 3. Healthy boundaries | Use AI as a tool; keep your own judgement | AI drafts, people decide; no AI-only decisions about customers or staff |
Rule 1: what staff must not put into AI tools
The advisory is blunt: once you share information with a generative AI tool, you lose control over how it is stored, processed or accessed. It lists full name, address and NRIC number, and sensitive information such as financial or medical records, as things to keep out. It adds that workplace information and confidential business data should never be given to AI tools without proper authorisation.
In practice, the risky pastes in a small business are predictable. Give staff a concrete list rather than a vague warning:
- customer names with phone numbers, emails, addresses or NRIC numbers;
- staff records, payslips, medical certificates or performance notes;
- bank statements, invoices with account details, and payment screenshots;
- contracts, tender documents and pricing you have not published;
- passwords, API keys, one-time codes and system screenshots that show them;
- anything a client has shared with you under a confidentiality agreement.
Authorisation is the key word. A company-approved business plan with training switched off and admin controls is a different thing from a personal account on a free tier. Our ChatGPT at work policy guide explains how to decide which tools are approved and what data each may see.
Rule 2: approved tools only, and watch the extensions
The advisory tells users to pick reputable tools with clear privacy policies and terms, and otherwise to assume the provider can access everything and may use conversations for model training. It specifically calls out third-party apps, such as unofficial mobile apps and browser extensions, which may collect and use your data.
This is the gap most offices miss. A staff member installs an AI writing helper in Chrome, and it can now read every web page they open, including the company webmail and accounting system. The advisory's red flags are useful as a staff test: permission requests that do not match what the app does, such as camera or location access, and apps from unknown developers.
Rule 3: verify AI output before it leaves the company
The second practice in the advisory deals with accuracy. It warns that guardrails are not foolproof and that AI tools produce hallucinations: fictional or partly correct information presented convincingly, including fabricated references, quotes and statistics. Its advice is to cross-check with official and trusted sources, consult professionals on health and legal matters, and treat AI output as a starting point.
For a business, wrong output is not just embarrassing. A made-up regulation in a client proposal, an invented price in a quotation or a wrong date in a customer email creates real liability. Set a simple sign-off routine:
Mark AI-assisted drafts
Staff note in the file or email draft that AI helped, so the reviewer knows what to check.
Check every number, date and name
Each figure must trace back to your own records or an official source, such as a gov.sg page, not to the AI's answer.
Open every link and citation
AI tools can cite pages that do not exist or that say something else. If the source does not support the claim, remove the claim.
Get a professional view on legal, tax and medical points
The advisory says this directly for high-impact issues. AI can help you prepare questions, not replace the adviser.
Pause before sending or posting
The advisory's 'pause before sharing' step: does it make sense, and could you defend it to the customer?
Rule 4: people decide, and the account stays secure
The third practice is about healthy boundaries. For individuals it focuses on emotional dependence on AI companions and keeping critical thinking. The workplace version is simpler: AI can draft, summarise and suggest, but a person makes decisions about customers, hiring, refunds and money.
Account security belongs here too. An AI account holds months of prompts that can reveal a lot about your business, and the advisory notes that if a tool is compromised, that history can be misused for fraud or scams. Treat AI logins like email logins: company accounts, MFA switched on, and access removed when staff leave.
Scammers also use generative AI to produce convincing messages, voices and videos. The advisory does not go into deepfakes, but the same verify-first habit applies: a voice note or video call asking for an urgent payment change should be confirmed through a known phone number before anyone acts. Our phishing spotting guide covers the written version of this trick.
One-page staff checklist based on the advisory
Print this, or paste it into your onboarding pack. It covers the three practices in a form staff can follow without reading the advisory.
Safe generative AI use at work
Ask staff to acknowledge it once and again each year. That record also helps show the PDPC that you have reasonable arrangements in place.
Do it yourself or get help?
A small team can adopt these rules in an afternoon: pick the approved tools, switch on business-plan privacy settings, circulate the checklist and get acknowledgements. The harder part is keeping the habit alive as new tools appear.
Our Security Awareness Training (S$390) sets up short monthly lessons in your own account, including Singapore scam topics and safe AI use, with completion tracking. Staff who know why the rules exist follow them better than staff who were just sent a PDF.
Frequently asked questions
No. Advisory AD-2026-008 is guidance for individuals on safe and secure use of generative AI. It does not create new legal obligations. Businesses still have binding duties under the PDPA when staff put personal data into AI tools, and the PDPC's July 2026 advisory guidelines explain how the PDPC reads those duties for generative AI.
No. It says confidential or sensitive business data should never go into generative AI tools without proper authorisation. That leaves room for companies to approve specific tools and plans, set rules on what data may be used, and train staff. A blanket ban is a business choice, not something the advisory requires.
It warns that generative AI accessed through third-party apps, such as unofficial mobile apps or browser extensions, may collect and use your data. It suggests watching for red flags like permission requests that do not match the app's purpose and apps from unknown developers. For businesses, controlling extensions through the admin console is the practical answer.
The advisory recommends cross-checking AI content with official and trusted sources, such as government websites, and consulting professionals for health and legal matters. At work, that means checking every number, date, name and citation against your own records or the original source, opening every link, and having a person sign off before anything goes to a customer.
Usually the owner or the person already handling IT and data protection, often the Data Protection Officer. They approve the tool list, set the account settings, collect staff acknowledgements and review the rules when a new tool or law appears. Keeping it with one named person avoids rules that nobody updates.