Responsible AI Use ยท Lesson 2 of 3
Confidential code and AI tools
Study notesAbout 3 minutes. A full lesson with quick checks is on its way.
In short
Only put company code or personal data into AI tools your organisation has approved. Pasting it into an unapproved service can be a data leak.
In your work
Stuck on a bug in a charity client's donor database, you're tempted to paste the module, with some real donor records, into a free chatbot. Instead you use the approved assistant and swap the records for made-up ones.
What the UK rules say
- Putting personal data into an AI service is processing under UK GDPR, and the ICO's guidance on AI and data protection applies.
- Client code and data are usually covered by confidentiality terms, and the BCS Code of Conduct says not to disclose confidential information without permission.
What to do
- Check which AI tools are approved, and for which kinds of data.
- Remove personal data, secrets and client names before asking for help.
- Ask before sharing a client's code, even with an approved tool.
Watch out for
- Assuming a paid plan or 'private mode' means a tool is approved.
- Pasting logs or stack traces that contain tokens or customer details.
In your organisation
Which AI tools are approved at your organisation, and for which kinds of data?
Your employer's own policies come first.
Sources
- ICO, Guidance on AI and data protection (opens in a new tab), checked 6 October 2026.
- BCS, BCS Code of Conduct (opens in a new tab), checked 6 October 2026.
UK law and guidance, explained for learning. Not legal advice.
