What your team should never paste into AI
A small firm's staff should never paste five kinds of things into an AI chat tool: customer personal details, salary and bank records, anything a client shared in confidence, passwords and access codes, and notes about a named employee.
The firm should write those five on one page, talk them through with the team once, and show people how to do the same job without the raw data. That takes about an hour, and it's the cheapest safety step a firm will ever take with AI.
Why this matters the week the logins arrive
The risk starts the day the owner buys logins and tells the team to use them. Someone in accounts pastes the month's salary sheet and asks for a summary for the owner. Someone in sales pastes a customer list with phone numbers to "clean up the format". Nobody meant harm, and both jobs got done faster.
What happens to that text afterwards depends on the plan the firm bought and how its settings are set. Some personal and free plans use chats to train the model unless the user switches it off, while business plans usually don't by default. Most staff don't know which plan they're on, and they shouldn't have to know before they can work safely. A short list does that job for them.
The five things on the list, and what each one protects
- Customer personal details, such as names with phone numbers, addresses or ID numbers. India's data protection law (the DPDP Act) puts the duty on the firm that collected the data, so a leak is the firm's problem and not the tool's.
- Salary, bank and payment records. These are the records people would be most upset to see outside the firm, and a single pasted sheet carries every name on it.
- Anything a client shared in confidence, such as a contract, a price list or a drawing. The firm has often signed a confidentiality clause, and pasting the file breaks it.
- Passwords, one-time codes, access keys and login links. Anything that opens a door stays out of every chat, because a chat history is easy to share by accident.
- Notes about a named employee, such as performance, health or a warning letter. These are the most personal records a small firm holds, and they don't need a name attached for the AI to help with wording.
What staff can do instead
Most of these jobs can still be done safely. Replace names with labels such as Customer A and Employee 2 before pasting, then put the names back by hand. Describe the shape of a sheet instead of pasting it ("a table of 40 customers with name, city and last order date; write a formula that flags anyone with no order in 90 days"). For anything on the list that really needs AI help, the person asks the owner first, and the owner decides whether the firm's business plan is the right place for it.
Make it one page and one conversation
Put the five lines on one page and pin it where people work. Then spend 15 minutes with the team, and ask each person to say one thing they've pasted into an AI tool in the last month, with no blame attached. In most firms that one round shows more than any policy document would, because people say what they actually did.
I write the same kind of list for every AI helper in my own setup, before it does any work. The list of what it must never do takes longer to write than the list of what it does, and it's the one I rely on. A team needs the same thing, only shorter.
Once the list exists, the firm can pick its first safe job for AI with the team, which is what the hands-on workshop I run with small leadership teams covers. You can ask about the workshop here.