Shadow AI is when employees use AI tools their company has not approved, like pasting customer data into a personal chatbot account or installing an AI browser extension. It happens in almost every organisation because the tools are useful and easy to access. Banning them rarely works; the better approach is to offer approved tools, set clear rules and make it easy for staff to ask.
Why is shadow AI a risk?
- Data leaks: confidential or personal data may be stored or used for training by a provider you have no contract with
- Compliance: privacy laws and client contracts may forbid sharing certain data with third parties
- Security: unvetted extensions, plugins and agents can be malicious, as in the fake Claude Code extension case
- Wrong answers: unchecked AI output can end up in reports, code or client emails
- No audit trail: if something goes wrong, nobody knows what was shared
Why does banning AI tools not work?
Because people use them to get work done faster, and they can use personal phones and accounts. A ban pushes use further out of sight. It also signals that the company is not helping staff learn a skill the job market increasingly expects, as covered in AI literacy as a job skill.
How do I manage shadow AI in 6 steps?
- 1. Find out what people use. Run an anonymous survey and check network and expense data, without punishing honesty
- 2. Offer an approved option. A business AI plan with data protections removes the main reason for shadow use
- 3. Write a short acceptable use policy saying which data can and cannot go into AI tools; see our acceptable use policy guide
- 4. Create a fast approval path for new tools, measured in days, not months
- 5. Train people on safe prompts, privacy and checking output
- 6. Review regularly, since tools and risks change every few months
What data should never go into an unapproved AI tool?
Customer and employee personal data, passwords and API keys, unreleased financial results, source code under client contracts, health or legal records, and anything marked confidential. When in doubt, ask or remove identifying details first.
What about AI agents and browser extensions?
These are a bigger risk than chatbots because they can act, not just answer. An agent with access to email or files can be tricked by hidden instructions on a web page. Require approval for any tool that connects to company systems, and see our agent autonomy risk guide.
Who should own the AI policy?
Usually a small group from IT or security, legal and a business team, so rules are safe but practical. For the wider rollout, read AI governance frameworks and common enterprise AI rollout mistakes.




