A Webflow agency in Suffolk explains what PECR and UK GDPR ask of a small site's cookie banner and contact form, with a table and a 3 field form test.

What PECR and UK GDPR ask of a small site's cookie banner and contact form, in plain English, with a table and a check you can do today.
Say you run a plumbing firm in Stowmarket with two vans. A customer emails to say your cookie banner only has an Accept button. You open your contact form and count 9 fields, when you only ever use 3 of them. That's usually how a cookie banner problem turns up on a small business site. Someone else spots it first.
We build Webflow sites on monthly plans, so bear in mind we'd like your business. We're web people, not lawyers, and this is general guidance rather than legal advice. Check the ICO's guidance or take advice for your own case. If someone already maintains your site, ask them to check both things this month.
Yes, if your site sets cookies that aren't strictly necessary, because PECR asks for consent before they're set. If everything it sets is strictly necessary, you don't need one.
Take a clinic in Sudbury running Google Analytics, with a YouTube video on the contact page and a map in the footer. Each of those can set cookies, and none of them is needed for the site to work, so the clinic needs a banner. The consent only counts if the banner does 4 things:
Most small sites trip the consent rule by accident, through an analytics tag or an embed that the owner added years ago and then forgot about. Find out what yours actually sets before you choose a banner tool, because a banner only works if it holds back the right tags.

Collect only what you need, explain why and for how long in a privacy notice, and link that notice right next to the form. Replying to an enquiry usually rests on legitimate interests, or on steps someone asked for before a contract.
Picture a Newmarket physio whose form asks for a date of birth on every single enquiry. Nobody reads the answer, yet it still has to be kept safe. Stick to a name, a contact detail and the message.
Put a link to your privacy notice beside the submit button, where people will actually see it. The notice should cover who you are, what you collect, why you collect it, how long you keep it and who to contact.
A newsletter tick box should be its own box, and it should start unticked. Someone asking for a quote hasn't asked for your monthly email.
If your site sets no analytics or embed cookies and the form is already short, we're the wrong answer. A one page brochure site like that may need little more than a clear privacy notice. Fix the notice and leave the rest.
If you're on WordPress and a consent plugin already works properly, don't move platform for this alone.
Health information, children's data and regulated financial work bring stricter rules, so check the ICO and take proper advice rather than lean on a blog post, ours included.
Rebuilding anyway? It's easier to build consent in from the start with a new website build than to bolt it onto an old one. Our plans are from £189 a month, priced on the page.
Yes, if your site sets analytics or advertising cookies, or loads embeds that set them. Strictly necessary cookies on their own don't need a banner.
Accept alone isn't enough. Reject should be as easy as accept, with nothing ticked in advance and no refusal hidden behind a settings screen.
Who you are, what you collect, why you collect it, how long you keep it and who to contact. Name anyone else who handles the data, such as your email provider, and say what rights people have over it.
Replying to their enquiry is fine. Marketing emails are a different matter, so the safe route is a separate opt in box, never ticked for them, with a note of when and how each person agreed.

Open your site in a private browser window and don't click Accept. Use the browser's site settings or developer tools to see which cookies are already stored, and note anything that isn't strictly necessary. Then check whether Reject is as easy to find and click as Accept.
Now open the contact form. Is there a privacy link? How many fields are there, and is any box already ticked for the visitor? Cut the fields you never use.
Send us your site address and we'll tell you what it sets before consent, even if you never hire us.
Written by the FutureProofs team in Suffolk. Reviewed by Luke.