Regulation compliance

UK GDPR for a plumbing business: the essentials

Lawful basis, privacy notices, retention, access requests and data breaches explained for plumbing and heating firms, with a one-page action plan.

Ava research teamPublished 7 min read

On this page
  1. Why a one-van firm is a data controller
  2. What personal data a plumbing firm holds
  3. Your lawful basis, purpose by purpose
  4. Tell people what you do with their data
  5. Keep it safe: where small firms get caught
  6. Access requests and other rights
  7. When something goes wrong
  8. Example: the phone left on the van roof
  9. A one-page action plan
  10. Frequently asked questions
  11. References

Key takeaways

  • Every plumbing firm that keeps customer names, addresses, photos or call notes is a data controller under the UK GDPR, whatever its size.
  • Most of your processing rests on contract and legal obligation. Marketing is where firms usually go wrong.
  • Phishing is the attack most likely to reach you: 35% of UK micro businesses identified phishing attacks in 2025[1].
  • Reportable breaches must go to the regulator within 72 hours of you becoming aware of them[2], so plan your response before you need it.

Why a one-van firm is a data controller

The UK GDPR and the Data Protection Act 2018 apply to anyone who decides why and how personal data is used. A sole trader who keeps a phone full of customer contacts, photos of the inside of people's homes and notes about key safes is doing exactly that. Size does not change the rules, though it does change how much paperwork is proportionate.

The good news is that most of what a plumber does with data is ordinary and expected. Customers want you to have their address and phone number. The risk sits in a few places: data kept forever, marketing sent without the right permission, security left to chance, and nobody knowing what to do when a phone or laptop goes missing.

What personal data a plumbing firm holds

  • Enquiries: names, phone numbers, emails, addresses and the fault described, from calls, web forms, texts and social media messages.
  • Job records: job sheets, photos and videos taken inside homes, access notes, key safe codes, alarm codes and pet warnings.
  • Call recordings and transcripts, if you record calls or use an answering service.
  • Safety and compliance records: gas safety records, commissioning records and building regulations notifications, which name the occupier or landlord.
  • Landlord and tenant details passed to you by letting agents.
  • Vulnerability notes, such as an elderly customer with no heating or a resident who needs extra time to reach the door.
  • Payment and invoice records, including bank details for refunds.
  • Staff records: contracts, payroll, driving licences, training certificates and sickness notes.
  • Dash cam and vehicle tracker data that can identify drivers and members of the public.

Health details, even a simple note that a customer uses a wheelchair or is unwell, are special category data. Record only what the engineer needs to do the job safely and keep it out of general notes that everyone can see.

Your lawful basis, purpose by purpose

Typical lawful bases for a plumbing firm's processing. Record your choices in a short document.
What you use data forUsual lawful basisWatch out for
Quoting, booking and doing the jobContractCollect only what the job needs
Gas safety and compliance recordsLegal obligationKeep as long as the regulations require, then delete
Tax and accounting recordsLegal obligationHMRC retention periods apply
Service reminders to existing customersLegitimate interestsElectronic marketing rules may also apply
Newsletters and offersConsent, or soft opt-in for existing customersPECR, not just GDPR, governs emails and texts
Call recordingLegitimate interestsTell callers and set a retention period
Vulnerability notesLegitimate interests plus a special category conditionKeep minimal and access-controlled
Staff payroll and recordsContract and legal obligationRestrict access to whoever runs payroll

Write these choices down. A one-page record of what you hold, why, on what basis, where it is stored and how long you keep it is the backbone of compliance for a small firm. It also makes your privacy notice and your answer to any complaint much easier to write.

Tell people what you do with their data

When you collect data from someone, Article 13 requires you to give them certain information: who you are and how to contact you, your purposes and lawful basis, any legitimate interests you rely on, who receives the data, any transfers abroad, how long you keep it, their rights, their right to complain to the regulator, and whether they have to give you the data[3].

For most firms that means a clear privacy notice on the website, a link in emailed quotes and booking confirmations, and a short line in your voicemail or call greeting where calls are recorded. Our guide to writing a privacy notice for a plumbing website covers the sections in detail, and the call recording rules for trades explain what to tell callers.

If an AI Employee such as Ava answers your phones, the call recordings and transcripts it produces are personal data like any other. Name the service in your notice as a processor and give those records a retention period.

Keep it safe: where small firms get caught

Cyber attacks on small firms are routine. 43% of UK businesses reported a cyber security breach or attack in the 12 months before the 2025 survey[4]. Phishing was the most common type, experienced by 85% of the businesses that had a breach or attack[5]. Among micro businesses, 35% identified phishing attacks, down from 40% the year before[1].

UK micro businesses identifying phishing attacksBusinesses with 0 to 9 employees, Cyber security breaches survey
UK micro businesses identifying phishing attacksColumn chart. 2024: 40%; 2025: 35%.0%10%20%30%40%2024: 40%40%20242025: 35%35%2025UK micro businesses identifying phishing attacksColumn chart. 2024: 40%; 2025: 35%.0%10%20%30%40%2024: 40%40%20242025: 35%35%2025

Source: Department for Science, Innovation and Technology (GOV.UK), 2025[1]

Show the data
ItemValue
202440%
202535%

Awareness of practical help is low: only 9% of micro businesses knew about the government's Cyber Essentials scheme[6]. Its basic controls are a sensible checklist even if you never certify.

  • Turn on two-step verification for email, job management, accounting and banking.
  • Use a password manager and a different password for every system.
  • Set phones and tablets to lock automatically and to wipe remotely if lost.
  • Keep devices and apps updated, and remove ex-staff from every system on their last day.
  • Check bank detail changes by phone using a number you already hold, never one in the email.
  • Back up job records somewhere that ransomware on one laptop cannot reach.

Access requests and other rights

Customers, tenants and staff can ask for a copy of the personal data you hold about them. Disputes are the usual trigger: a customer unhappy with a bill asks for every note, photo and call recording about their job. Until February 2026 Article 12(3) required a response within one month of receipt, extendable by two further months for complex or numerous requests[7]. The Data (Use and Access) Act 2025 has since moved the time limit rules into a new article, so check the regulator's current guidance when a request arrives.

  1. Log the date the request arrived and confirm the person's identity if you are unsure who they are.
  2. Search every place data could be: job software, email, phones, photos, call recordings and paper files.
  3. Remove other people's personal data unless you have a reason to include it.
  4. Send the copy securely with a short covering note explaining what is included.
  5. Do not delete anything once a request has arrived. That can be an offence.

When something goes wrong

A personal data breach is any security incident that leads to personal data being lost, destroyed, changed, disclosed or accessed without authority. For a plumber, that might be a stolen work phone, a laptop left on a train, an email sent to the wrong landlord, or a hacked email account.

If a breach is likely to result in a risk to people's rights and freedoms, you must notify the regulator without undue delay and, where feasible, within 72 hours of becoming aware of it[2]. If notification is late, you must give reasons. Breaches that are unlikely to cause any risk do not need reporting, but you should still record them and what you did.

  1. Contain it

    Wipe the lost phone remotely, change passwords, recall the email if possible, and ask the wrong recipient to delete it.

  2. Assess the risk

    Whose data, how much, how sensitive, and could anyone be harmed, for example through key safe codes or alarm codes?

  3. Decide on reporting

    If there is a likely risk, report to the regulator within the deadline. If there is a high risk, tell the affected people too.

  4. Fix the cause

    Change the process or setting that allowed it and note what you changed.

Example: the phone left on the van roof

Example. An engineer puts his work phone on the van roof while loading and drives off. The phone holds the job app, a week of photos inside customers' homes and a notes file with three key safe codes. He realises an hour later.

The owner wipes the phone remotely from the device management console, changes the job app password, and asks the three customers to change their key safe codes, explaining why. Because the phone was locked with a PIN and wiped quickly, and codes have been changed, he decides the remaining risk is low, records the incident and his reasoning, and does not report it. The firm moves key safe codes out of the notes app into the job system's restricted field.

A one-page action plan

  1. List the data you hold, why, on what basis, where and for how long.
  2. Publish a clear privacy notice and link to it from quotes and confirmations.
  3. Check whether you need to pay the data protection fee.
  4. Separate service messages from marketing and follow the rules on marketing texts and emails.
  5. Switch on two-step verification and remote wipe for every device.
  6. Set retention periods and diary a yearly clear-out of old enquiries.
  7. Write down what you will do if a phone, laptop or van is stolen, and read how to stop tool theft from vans, because the data goes with the van.

Frequently asked questions

Does GDPR apply to sole trader plumbers?

Yes. If you decide how customers' personal data is used, you are a controller under the UK GDPR, whether you are a sole trader or a limited company.

Do I need consent to keep customer details?

Usually not. Doing the job relies on contract, and safety and tax records rely on legal obligation. Consent, or the soft opt-in, matters mainly for marketing emails and texts.

Is a stolen work phone a data breach?

It can be. If the phone holds customer data and is not protected, or codes and photos could be misused, assess the risk, contain it, and report to the regulator within 72 hours if the breach is likely to put people at risk.

Can a customer ask for their call recordings?

Yes. Call recordings are personal data and fall within an access request. Keep recordings only as long as you need them and know where to find them.

References

  1. Department for Science, Innovation and Technology (GOV.UK) (2025). Cyber security breaches survey 2025 (opens in a new tab) ↑

  2. legislation.gov.uk (The National Archives) (2026). UK GDPR, Article 33: notification of a personal data breach (opens in a new tab) ↑

  3. legislation.gov.uk (The National Archives) (2026). UK GDPR, Article 13: information to be provided where personal data are collected from the data subject (opens in a new tab) ↑

  4. Department for Science, Innovation and Technology (GOV.UK) (2025). Cyber security breaches survey 2025 (opens in a new tab) ↑

  5. Department for Science, Innovation and Technology (GOV.UK) (2025). Cyber security breaches survey 2025 (opens in a new tab) ↑

  6. Department for Science, Innovation and Technology (GOV.UK) (2025). Cyber security breaches survey 2025 (opens in a new tab) ↑

  7. legislation.gov.uk (The National Archives) (2026). UK GDPR, Article 12 (version as at 4 February 2026) (opens in a new tab) ↑

Book a demo

See Ava handle your calls.

Book a short demo. We’ll walk through your calls and workflow, and agree what Ava should take care of.

Book a demo