Protecting Customer Data Under UK Privacy Rules
Collect only what you need, store it securely, and explain plainly how personal information will be used and kept.
Why this matters more than you think
If you run a small business or work as a freelancer, you almost certainly hold more personal information than you realise. A client's home address, a customer's phone number, a spreadsheet of newsletter subscribers, a folder of invoices, a diary full of appointment names — all of it counts as personal data under UK law. The rules sit in the UK GDPR and the Data Protection Act 2018, and they apply to sole traders just as much as to large organisations. There is no small-business exemption.
The reassuring news is that the underlying principles are largely common sense. Treat other people's information the way you would want yours treated: collect only what you actually need, keep it safe, and be straightforward about what you are doing with it. Get those three habits right and you are most of the way there.
Know what you hold and why
You cannot protect data you have forgotten about. Before you change anything, spend an hour making a simple list. For each type of personal information you handle, note where it comes from, where it is stored, who can see it, and how long you intend to keep it.
- Customer enquiries and quotes, including old ones you never deleted
- Invoices, receipts and accounting records
- Email inboxes and message threads on your phone
- Mailing lists, booking systems and loyalty schemes
- CVs, references and notes about subcontractors
- Any spreadsheets saved to a personal drive or desktop
The untidy places are usually the risky ones. Somewhere there is probably a folder called "old clients" that has been copied between three laptops. Find it, decide whether you still need it, and delete what you don't.
Collect only what you need
Data minimisation sounds technical but simply means: if you don't need it, don't ask for it. A date of birth is rarely necessary to quote for a job. A home address may not be needed until an invoice is raised. Every extra field you add is another thing to store, secure and eventually delete.
- Review your enquiry forms and remove anything you have never actually used
- Mark optional fields as optional, and don't make consent a condition of doing business
- Only collect sensitive information — health details, for example — if you genuinely need it and have a proper lawful basis
- Check your lawful basis for each purpose: a contract, a legal obligation, consent, or legitimate interests
- If you rely on consent, it must be a clear positive action. A pre-ticked box does not count
That last point catches a lot of people out. Consent has to be freely given, specific and easy to withdraw, and you need to be able to show when and how someone gave it.
Store it securely, in practice
Security does not require an IT department. It requires a handful of habits applied consistently.
- Use a password manager so every account has a long, unique password, and turn on two-factor authentication wherever it is offered
- Turn on encryption for laptops and phones — it is usually a single setting
- Check sharing permissions on cloud folders. A link set to "anyone with this link" is a data leak waiting to happen
- Install updates promptly, including on phones and routers
- Keep regular backups, and make sure the backup is encrypted too
- Avoid emailing spreadsheets of personal data around. Use a shared folder with proper permissions instead
- Have a simple process for when someone leaves or stops working with you: revoke their access the same day
Don't overlook paper. A locked drawer and a shredder still matter, and a box of old records in a garage is not a secure filing system.
Explain it plainly
People are far more comfortable sharing information when they understand what happens to it. A privacy notice does not need to be a legal epic — a clear page on your website, written in plain English, is usually enough. Cover what you collect, why, who you share it with, how long you keep it, and how someone can get a copy, correct it or ask you to delete it. Add a short line at the point of collection so people see it before they hand anything over.
Then actually follow it. Decide a retention period for each category — accounting records, for instance, are typically kept for six years for tax purposes, while an unsuccessful job enquiry might only need a few months — and clear out what has passed its date. If you say you delete marketing data after two years, put a reminder in your calendar and do it.
Keep it ticking over
Data protection is a habit, not a one-off document you write and file away. Diarise a short review every few months: check who still has access to your systems, clear out old files, and confirm your privacy notice still matches what you actually do.
Know what to do if something goes wrong. If personal data is lost, stolen or exposed, you may need to report it to the Information Commissioner's Office within 72 hours of becoming aware, and tell the people affected if there is a real risk to them. Keep a brief log of what happened and what you did — it demonstrates you took it seriously.
Remember too that individuals have rights. They can ask for a copy of their data, ask you to correct it or delete it, or object to how you are using it, and you generally have one month to respond. You do not need to be perfect. You need to be deliberate, and to be able to show that you thought about it.

Post a comment