Access codes with an address
Key-safe, alarm, gate and garage codes. “Key safe 1472, side gate” next to a postcode is a burglary in one message. Keep these in your job system, not in a chat window.
For the trades
Half the trades I talk to are already doing this: a job description into ChatGPT, out comes a tidy quote or a polite chasing email. Good — it saves an evening a week. But the customer’s name, their address and the key-safe code went in with it, and that is where a useful habit becomes a data leak. Here’s the line, in plain English.
Using ChatGPT or any AI tool to draft quotes and customer emails is fine. The risk is what you paste in: a customer’s name with their address, phone numbers, key-safe or alarm codes, photos of the inside of their home, or anything about their health. Keep those out, use a business account with training switched off, add one line to your privacy notice, and you’re compliant.
Published
The job, without the person. An AI tool writes a better quote when it knows what the work is, not who it’s for. All of this is fine in any tool, on any plan:
Notice there’s no name in there. You add “Dear Mrs Pascoe” and the address yourself, after the tool has done the writing. That one habit removes most of the risk on its own.
Not on a free plan, not on a paid plan, not on a business plan. These don’t belong in a general AI tool at all, because the tool doesn’t need them to do the job and the downside if they leak is serious.
Key-safe, alarm, gate and garage codes. “Key safe 1472, side gate” next to a postcode is a burglary in one message. Keep these in your job system, not in a chat window.
Each on its own is personal data. All three together is a complete record of a real person. The tool doesn’t need any of them to write the quote.
“Elderly, lives alone, hard of hearing, leave the door on the latch.” Health details are special-category data under UK GDPR — the highest bar there is — and that sentence is also a safety risk to the customer.
A boiler is fine. A kitchen with post on the worktop, a child’s school jumper on the chair and the street through the window is not. Crop to the work. No faces, ever.
On a landlord job you hold data about two people, and the tenant never agreed to anything. Their name and number stay out.
Yours or theirs. If an invoice template needs your bank details, add them after the tool has written it.
When you type into one of these tools, the text leaves your phone and goes to the company’s servers — usually in the United States — to be processed. What happens next depends on the plan you’re on. On a consumer plan the company may keep your conversations and, unless you’ve turned it off, use them to improve its models. On a business plan it doesn’t train on them, and keeps them only as long as it says in its terms.
That’s the whole data-protection question in two sentences. UK GDPR doesn’t ban AI tools. It asks whether you had a lawful reason to process the customer’s data, whether you told them you were doing it, and whether you handed it to someone who might do something with it you never agreed to. A customer’s address in a model’s training data is the third one.
The ICO — the regulator — doesn’t go looking for one-man bands who used the wrong plan. It acts on complaints and breaches. The realistic risk for a small firm isn’t a fine; it’s a customer finding out that their access code went into a free chatbot, telling the village, and leaving a review that says so.
Every one of these tools comes in two kinds of account, and the names are confusing on purpose.
| Kind of account | Examples | Your data |
|---|---|---|
| Consumer | ChatGPT Free, Plus, Pro · Claude Free, Pro, Max · Gemini personal · Copilot personal | May be used to improve the model unless you find the setting and turn it off. Conversations kept. |
| Business | ChatGPT Business or Enterprise · Claude Team or Enterprise · Gemini in Workspace · Microsoft 365 Copilot | Not used for training by default. Covered by a business agreement you can point to in your privacy notice. |
A business plan for one or two people costs about the same as a round of bacon rolls each month. If anyone at the firm puts customer details into an AI tool, that is the plan they should be on. If you want to stay on a consumer plan, go into the settings today and turn off “improve the model” — and then keep all the personal data out anyway, because the retention still applies.
Find out what the office is actually using. Ask, don’t accuse. Most people have never thought about it.
Put it on a business plan, or at minimum turn off model training on the consumer one.
Agree the rule: the job goes in, the person doesn’t. Name, address, phone, codes, health, photos of people — added afterwards, by hand.
Add one line to your privacy notice. “We use AI tools to help draft quotes and correspondence; customer details are processed under a business agreement and are not used to train AI models.”
Write it down. The one-page staff AI policy is free and takes ten minutes to fill in. It’s what you point to if anyone ever asks.
Copy this, change the details, paste it into whichever tool you use. Nothing in it identifies the customer.
Write a quote for a roofing job. I am a roofer in Cornwall. Job: strip and re-slate the front elevation of a 1930s semi, approx 45m², reclaimed Delabole slate to match the rear, new breathable membrane, replace one lead valley, re-bed ridge tiles. Price: £[your figure] plus VAT, materials and scaffold included, skip excluded. Lead time: 5–6 weeks from deposit. Terms: 25% deposit, balance on completion, 10-year workmanship guarantee. Tone: friendly, professional, short. Leave a gap for the customer's name and address, which I'll add myself.
The tool writes the quote. You add the name and the address. The customer gets a professional document, and nothing about them ever left your phone.
This is plain-English guidance for small businesses, not formal legal advice. Where something genuinely needs a solicitor or a data-protection specialist, I'll tell you straight.
Free template. What staff may and may not put into AI tools, which tools are approved, who checks the output. Prevents most incidents before they happen.
The single most common way small firms leak data. When it is fine, when it breaches UK GDPR, and how to make it safe.
Written by someone who spent forty years on the tools. What genuinely helps a working trade, and what is sales patter.
Not sure which accounts your staff are actually on, or what the one-page rule for the office should say? Ask. Written for a trade, not a corporation, and I'll tell you what you can sort yourself.
Talk to Mick