Using AI Chatbots at Work Without Leaking Company Data

Most people who use AI chatbots at work do it to save time: summarising a long document, drafting an email, fixing a spreadsheet formula, explaining an error message. Those are good uses. The risk lies in what gets pasted into the chatbot and where that data goes next.

The cautionary tale

In 2023, Samsung engineers pasted confidential source code and internal meeting notes into ChatGPT while asking for help. Nobody hacked anything. They sent sensitive data to an external service under consumer terms, and Samsung responded by restricting staff use of generative AI tools on company devices. In most organisations, the biggest AI data risk is ordinary employees trying to get their work done.

OWASP’s Top 10 for LLM Applications ranks sensitive information disclosure second, right after prompt injection.

Where your data can go

Some consumer AI services may use your conversations to train their models unless you opt out. Business and enterprise plans from the major providers generally exclude customer data from training by default, but check the terms of the plan you actually use. Conversations may also be stored for a period and, in some cases, reviewed for abuse or safety monitoring.

Data can also leave through side doors. A “share” link, a browser extension or a third-party plugin can expose a conversation far beyond the person who started it. And if someone takes over a staff member’s AI account, they get its entire chat history.

Five rules for anyone using AI at work

  1. Use the company-approved tool, signed in with your work account, and keep personal free accounts out of work.
  2. Never paste secrets: passwords, API keys, private keys, connection strings, or anything from a .env file. If you do paste one, treat it as compromised and rotate it.
  3. Strip personal data before you paste. Replace customer names, ID numbers, addresses and health or financial details with placeholders; the model rarely needs them to help you.
  4. Keep contracts, unreleased financials, M&A material and source code in tools your organisation has approved for that classification of data.
  5. Check the output before you use it. AI can be confidently wrong, and you remain responsible for what you send to a customer or commit to production.

A one-page AI policy for small businesses

Banning AI rarely works. People use it on their phones anyway, and then you have no visibility at all. A short, clear policy works better, and it only needs four parts.

Name the one or two AI services staff may use, on business plans with training on customer data switched off and with single sign-on and MFA enforced. Set data rules as a simple traffic light: public information is fine (green), internal information goes only into approved tools (amber), and secrets and regulated personal data never go in (red). Treat AI output as a draft, with a named person reviewing anything that goes to a customer or into a system. And ask staff to report a mistaken paste immediately, without blame, so secrets can be rotated.

With a few simple guardrails, AI chatbots are among the best productivity tools a small team can have, and the company’s data stays with the company.

Sources