Stopping staff putting company data into AI tools on their own initiative
You can't stop it with a ban. You stop it by giving people a sanctioned tool that's better than the one they're sneaking, a short list of what never goes in, and no shame in asking.

Why people do it
Because it helps them, the company hasn't given them anything as good, and nobody has said clearly what the risk actually is. A rep pasting a customer's email into a consumer assistant to draft a reply isn't being reckless. They're doing their job faster with the tool in front of them. In our experience most "shadow" use is exactly this – ordinary work, in a tool the company can't see, by people who'd happily use the sanctioned one if it existed and was any good.
The order
- Provide. A company-owned assistant for everyone, with training switched off, retention set, and the licence in the company's name. If the sanctioned tool is worse than the free one, it fails right here. The settings are in protecting IP and company data.
- Rules. One page, mostly a list of what never goes in, shown to everyone on the staff and every new starter. The list is below.
- Ask. A named person, and a way to ask that takes less time than guessing. If asking is slow, people guess.
- Block. Only now, and only on company devices: block the consumer versions of the tools you've provided. On personal devices you can't block anything, so the rule and the training are what you've got.
Businesses that start at step 4 get a quieter problem, not a smaller one.
What never goes in
Be specific, or it isn't a rule. In most B2B businesses the list is:
- Personal data about a customer or someone on the staff: names with addresses, phone numbers, dates of birth, anything medical or financial about a person.
- Payroll and the management accounts.
- Anything received under a non-disclosure agreement.
- Source designs, formulations, code and pricing logic.
- Passwords, keys, and anything else that unlocks a system.
Everything else, in the company workspace, is allowed. People find a short list of what's out, with everything else allowed, easier to follow than a long cautious one, because it answers the question they've actually got.
Making the shadow use visible
Ask. Once a quarter, every team gets asked what tools they use and for what, with an amnesty said out loud: nobody's in trouble for what they tell you. The list that comes back is the best picture you'll have of where the tools are useful, and most of it will be ordinary. Then move each use into the sanctioned tool. Where the sanctioned tool can't do it, that's a request to the AI lead, not a reason for the person to carry on quietly.
When someone gets it wrong
They will. Somebody will paste the wrong thing somewhere. The response that means the next person tells you too is to thank them for telling you, work out what was exposed and to whom, tell the people who need to know, and close the gap that made it easy. The response that drives it underground is punishing the report.