Your contact form is handling personal data. Is it doing it safely?
· 5 min read
Almost every business website has one: a simple form asking for a name, an email address, a phone number and a message. It feels harmless. Someone wants a quote, they fill it in, you get an email.
But that form is collecting personal data. Under UK GDPR, your business is responsible for what happens to it from the moment someone presses “Send”. On older websites, nobody has thought about that for years.
(This is part three of a series. Part one has the overview.)
What UK GDPR expects, in plain English
You don’t need to read the regulation to get the gist. For a contact form, it comes down to four things.
- Tell people what you’re doing. Before or when they submit the form, people should be able to find out who you are, why you want their details, what you’ll do with them, how long you’ll keep them and who else sees them. That’s what a privacy notice is for.
- Only collect what you need. If you only ever reply by email, do you need their home address and date of birth?
- Keep it secure. You’re expected to protect personal data with security that’s appropriate to the risk. For a website, that means the basics: encryption, up-to-date software, and not leaving data lying around.
- Don’t keep it forever. Keep enquiries for as long as you have a reason to, then delete them.
None of this is new. What’s changed is how many old websites quietly fail on all four.
The usual problems on older sites
Every message ever sent, still on the website
Many contact form plugins save a copy of every submission in the website’s own database, as well as emailing it to you. Nobody turns this off, and nobody clears it out. We regularly see small business sites holding five or more years of enquiries: names, phone numbers, email addresses and whatever people typed in the message box.
That’s a problem twice over. You’re keeping personal data far longer than you need it. And it’s sitting on the part of your setup that attackers target most, often behind software that hasn’t been updated. If someone breaks into the site, they don’t just deface it. They take the lot.
Messages going to the wrong place
Forms are usually set up once, at launch, to email a particular person. People leave. Inboxes get forwarded to personal accounts, or just keep receiving mail nobody reads. We’ve seen forms still delivering enquiries to someone who left the business years earlier.
No padlock
Some older sites still send form submissions without encryption, so anything typed into the form can be read on the way. Browsers now flag these sites as “Not secure”, which also does nothing for your enquiry numbers.
A privacy notice from a template
The privacy notice was downloaded at launch, filled in with the business name, and never looked at again. It doesn’t mention the contact form, the mailing list, or the services the site now uses. A privacy notice that doesn’t describe what you actually do doesn’t meet the requirement.
Plugins nobody looks after
Form plugins are among the most common ways into older websites. A plugin that hasn’t been updated, or has been abandoned by its developer, can expose every submission it has ever stored.
If something does go wrong
If personal data is lost, stolen or exposed, that’s a personal data breach. If it’s likely to put people at risk, you have to report it to the ICO within 72 hours of finding out. If the risk to people is high, you may need to tell them too.
For a small business, the bigger cost is rarely a fine. It’s the time, the stress, the awkward emails to customers, and the questions about why years of enquiries were sitting on an out-of-date website in the first place.
New since June 2026: a way to complain
The Data (Use and Access) Act added a new duty that applies to almost every business. Since 19 June 2026, you must have a process for handling data protection complaints. In short, you need to:
- Give people a way to complain to you directly about how you’ve handled their data. It can be email, a form or a phone number. There’s no single required method.
- Acknowledge a complaint within 30 days.
- Look into it and respond without undue delay, telling them the outcome.
- Keep a record of complaints and what you did about them.
For most small businesses, this means adding a short section to your privacy notice that says how to raise a concern, and making sure someone actually picks it up. It’s not a big job, but it’s one most older websites won’t have done.
Don’t forget the ICO fee
If your business uses personal data, and almost every business does, you probably need to pay the ICO’s data protection fee. For most small companies it’s £52 or £78 a year. It’s easy to miss when a business is set up, and not paying can lead to a fine. The ICO has a short self-assessment to check whether you need to.
What good looks like
A well set-up contact form is pretty unremarkable. It:
- asks only for what you need to reply
- sits on a secure, encrypted page
- delivers enquiries securely to an inbox you actually monitor
- doesn’t store copies on the website itself
- links to a privacy notice that describes what you really do, including how to complain
- is protected from spam bots without tracking your visitors
That’s how we build forms, and it’s how the forms on our own site work.
Four things to check
- Send yourself a test enquiry. Check who receives it. Is that still the right person?
- Ask whoever manages your site whether form submissions are stored on the website, and if so, how many there are and how far back they go.
- Read your privacy notice. Does it mention the contact form, how long you keep enquiries, and how someone can complain?
- Check your ICO fee is paid and up to date.
If you’d like us to check your forms and privacy notice, get in touch. It’s part of our website security check.
Not legal advice. The ICO’s guidance for small organisations is the place to check the detail.