Skip to content
Limited-time offer: Free external security assessment with your Buyer's Guide. Get the Guide
Business Technologies NI
Interactive learning

Is it safe to paste this into AI?

A five-minute story for business owners: choose your company's approach to AI and see what happens next.

Is it safe to paste company information into ChatGPT?

Not on a personal or free account. Public AI tools can keep what you paste, have people review it and be ordered by a court to preserve it—even when they promise not to train on it. Public or anonymised information is fine in any AI; client and confidential business information belongs only in an AI your business has approved and secured; passwords and keys never go in. The safe approach is a written AI policy, an approved, secure AI tool, tidy file permissions and a trained team.

Interactive story · 5 minutes

You run Mossvale Surveying

A 20-person firm of building surveyors in Lisburn (fictional). Choose how the business handles AI, see what happens next, and try other paths as often as you like. No sign-up, and nothing you choose is stored.

Read the whole story on one page

Round 1

AI has arrived at Mossvale

You own Mossvale Surveying, a 20-person firm of building surveyors in Lisburn. On Monday morning your office manager mentions that half the team already use AI to draft emails and reports.

Then a client's procurement form lands on your desk. Question 14: "Describe your organisation's approach to AI and how you protect our data."

What do you do?

If you choose: Leave it—the team will figure it out

Three months later…

The team has figured it out—on their own. Sarah in accounts pastes the client fee schedule into a free chatbot to tidy it up. Mark pastes a survey report, client's home address and all, into another to rewrite the summary. Both use personal accounts.

None of it was malicious. But those conversations now sit with providers Mossvale has no contract with. Free AI apps can keep chats, let human reviewers read some of them, and be ordered by a court to preserve them—in 2025 a US court did exactly that for ChatGPT conversations, deleted ones included.

Doing nothing isn't neutral: staff use whatever is free, and client data goes with it.

If you choose: Ban AI tools

The ban goes out on Tuesday…

The work doesn't get any lighter, so the AI simply moves. Reports get drafted on personal phones over lunch and emailed back in. Nobody mentions it, because officially it isn't happening.

Now you can't see any of it. This is shadow AI, and it's costly: IBM found that breaches at organisations with high levels of shadow AI cost an average of US$670,000 more. Even Samsung's ban, after engineers pasted source code into ChatGPT, was a pause while it put proper controls in place—not the answer itself.

A ban without a safe alternative hides the problem instead of solving it.

If you choose: Let everyone use the free tools they like

Productivity is up. Then the client calls back…

Reports are going out faster, using five different AI apps across twenty personal accounts. It feels like progress, until the client chases Question 14: which AI tools hold our data, and where?

You can't answer. If staff have put clients' personal details into those tools, UK GDPR still applies: Mossvale needs a lawful basis, and data sent to providers outside the UK brings the international-transfer rules into play. Right now you can't even say which providers have it.

If you can't say where client data went, you can't answer clients, insurers or the regulator.

If you choose: Have everyone switch off "use my data to improve the model" in their AI settings

Everyone ticks the box…

The team switch off "Improve the model for everyone", and you answer Question 14: "Our data is not used to train AI." It feels done.

But that setting only covers training. The provider can still keep conversations for a period—OpenAI's business platform, for example, keeps abuse-monitoring logs for up to 30 days. On consumer apps people may read them: Google says some Gemini chats are reviewed by people, and reviewed chats are kept for up to three years. And in 2025 a US court ordered OpenAI to preserve ChatGPT conversations, deleted and temporary chats included.

Meanwhile the chats still sit in staff members' personal accounts. Anyone who gets into one of those accounts, or is sent a shared chat link, can read what was pasted.

"We don't train on your data" isn't data protection. Ask what's kept, for how long, who can read it and where it's held.

If you choose: Buy everyone a popular AI subscription and leave it at that

Day two of the new AI assistant…

You buy a business AI that works across your Microsoft 365 files. On day two, a junior surveyor asks it to "summarise this year's pay review"—and it does.

The AI did nothing wrong. Years ago the HR folder was shared with "everyone", and assistants like Microsoft 365 Copilot can show a user anything that user can already open. Untidy permissions that nobody noticed are now one question away.

A good tool on untidy permissions makes over-shared files easy to find.

If you choose: Send a quick "be careful with AI" email

Everyone replies "Will do"…

Nobody knows what "careful" means. Is a client's name all right? A draft contract? A week later, someone pastes the office router's admin password into a chatbot to ask how to set up guest Wi-Fi.

They thought they were being careful: it was only the Wi-Fi. But a password pasted into an AI tool can't be taken back, so it has to be changed—and the contract pasted the day before is already out of your hands.

Vague advice changes nothing. Staff need to know which tool to use and what never goes in.

What good looks like

Every one of those paths had the same gap: nobody decided where company data is allowed to go. The fix is four plain steps, done together.

  1. A clear AI policy. One page that says which AI tools are approved, what staff can put into them, and what never goes in: client personal data in unapproved tools, passwords and keys, unreleased financials.
  2. An approved, secure AI. Business accounts the company controls, not personal ones—AI inside your own Microsoft 365, a private cloud AI for your business only, or AI on your own hardware for the most sensitive work. Get the terms in writing: what's kept and for how long, whether anyone can review it, where it's held and how legal holds are handled. A training opt-out covers none of these.
  3. Tidy permissions. Before any AI searches your files, remove company-wide sharing links, fix who can open which sites and folders, and label sensitive files.
  4. A trained team. Short and practical: real examples, take names and figures out before asking, and what to do if something slips—like changing a password that was pasted.

Round 2

Six months on: the big contract

Mossvale is shortlisted for a housing association's stock-condition surveys—your biggest contract yet. The reports will include tenants' names and addresses.

The team wants AI to speed up the write-ups, and the housing association's contract asks you to explain, in writing, how AI will handle tenants' data.

How do you handle it?

If you choose: Tell the team to take tenants' names out first, then use whichever AI they prefer

Report 37 of 200…

Taking names out is a good habit, and it works most of the time. Then report 37 goes in with a tenant's address in a photo caption, into a free tool on someone's personal account.

You still can't tell the housing association where their tenants' data is held, because it depends on whoever was typing that day.

Anonymising helps, but it's a habit, not a control. Client work needs a tool you control.

If you choose: Upgrade everyone to the premium plan of the AI app they already use

Twenty paid plans later…

The answers are better, but the accounts are still personal, the terms are the consumer ones, and there's no policy on what goes in.

When someone leaves, their chat history—tenant details and all—leaves with them. Paying for an AI app doesn't make it your business's AI.

A bigger subscription isn't a safer one. What matters is who controls the account and its terms.

The right path: Agree in writing which AI handles client data, set it up on business accounts with access limited to the project team, and walk the team through it

Contract signed.

Your answer to the housing association fits in a paragraph: which AI is used, where tenants' data is held, who can see it, how long it's kept, and what staff may and may not put in. Their data protection officer has no follow-up questions.

The team uses the AI openly because they know the rules. Reports go out faster, the project folder is locked to the people working on it, and nobody is drafting on their phone at lunch.

Policy, an approved and secure AI, tidy permissions and a trained team: that's what lets you say yes to AI and to the client.

If you choose: Keep AI away from this client's work altogether

Week three of the contract…

Two hundred reports, a tight deadline and a team that knows AI could halve the work. By week three, some of them are quietly using it anyway, on their own devices.

It's the ban again, at the worst possible moment: shadow AI on your most sensitive client's data.

Saying no isn't a plan when the pressure is real. Give the team a safe way to say yes.

Three things to take away

  1. Doing nothing, banning AI and leaving staff to choose all end the same way: company data in AI tools you don't control.
  2. "We don't train on your data" isn't enough. Ask what's kept, for how long, who can read it and where it's held.
  3. Safe AI is four things together: a written policy, an approved and secure AI, tidy permissions and a trained team.
Your next step to TechState™

Ready to run your business on its technology?

Book your Business Technology Review. In one focused conversation, we'll understand your business, assess your platform and show you the path to operating in TechState™.