Somewhere in the planning of a new website, usually just after the colours are chosen and just before the words are written, the question comes up. Do we need one of those privacy pages? And what about the cookie pop-up that every other site seems to have? Nobody wants to be the business that gets a letter about it, and nobody wants to clutter a clean new site with a banner that covers half the screen on a phone.
The good news is that for most small business websites the answer is fairly settled, and it is less dramatic than the internet makes it sound. Most sites that take enquiries need a privacy policy. Whether they need a cookie banner depends almost entirely on what the site loads, and a site built with care can often need a much smaller one, or none at all.
This guide explains what each one is for, how to tell what your own site needs, what a sensible privacy page says, and where small businesses tend to go wrong. It is general information rather than legal advice. If your business handles sensitive information, such as health details, or you are unsure about something specific, the Information Commissioner's Office (ICO) publishes guidance written for small organisations, and a solicitor can give you an answer for your circumstances.
Table of Contents
The Short Answer
If your website has a contact form, a booking tool, a newsletter sign-up or anything else that asks a visitor for their name, email address or phone number, you should have a privacy policy. It tells people what you collect, why, who else sees it and what rights they have. It does not need to be long, and it does not need to be written in legal language.
A cookie banner is a different matter. It exists to ask permission before a site stores or reads information on a visitor's device for purposes that are not strictly necessary. If your site sets advertising cookies, most analytics cookies, or loads third-party features that set their own, you will usually need to ask. If it sets nothing beyond what is needed for the site to work, you usually do not need to ask, though you should still explain what it does set.
| Your site | Privacy policy | Cookie consent |
| Brochure site, no forms, no analytics, no embeds | Still sensible, short | Usually not needed |
| Contact form, no analytics, no embeds | Yes | Usually not needed |
| Contact form plus Google Analytics | Yes | Usually yes, though the rules on analytics are changing |
| Advertising pixels, retargeting, social tracking | Yes | Yes |
| Embedded videos, maps, chat or review widgets | Yes | Often yes, depending on what they set |
| Online shop or customer accounts | Yes, more detailed | Depends on what is set beyond essentials |
The rest of this guide explains why those answers fall the way they do, so you can apply them to your own site rather than relying on a table.
The Two Sets of Rules
Much of the confusion comes from treating privacy policies and cookie banners as one subject. In the UK they come mainly from two different sets of rules, which ask different questions.
UK GDPR and personal data
The UK General Data Protection Regulation, alongside the Data Protection Act 2018, covers personal data: information that identifies a living person or could be linked to them. A name and email address typed into a contact form is personal data. So is a phone number, a home address for a quote, and the details someone writes in a message about the job.
One of the main principles is transparency. When you collect personal data from someone, you are expected to tell them, at the time, who you are, what you are collecting, why, how long you keep it, who you share it with and what their rights are. On a website, the privacy policy is the usual place to do that.
This applies whatever the size of the business. A sole trader taking enquiries through a form is collecting personal data in the same sense as a large company, even if the volume and the risk are tiny by comparison.
PECR and cookies
The Privacy and Electronic Communications Regulations, usually shortened to PECR, cover storing or reading information on someone's device. Cookies are the best known example, but the same rules apply to similar technologies, such as tracking pixels and local storage.
The core rule is that you need clear consent before setting anything that is not strictly necessary to provide the service the visitor asked for. You also need to tell people what you are setting and why. That is where the cookie banner comes from: it is the most common way of asking for consent before the non-essential items load.
PECR applies whether or not the cookie itself contains personal data. A site can therefore have very little personal data and still need cookie consent, or collect personal data through a form and need no cookie consent at all.
Worth keeping straight: the privacy policy is about what you tell people. The cookie banner is about what you ask them. A site can need one without the other.
The rules are not standing still. The Data (Use and Access) Act 2025 changes some of this, including relaxing consent for certain low-risk uses such as some analytics, with parts coming into force in stages. The detail matters, so check the ICO's current guidance before relying on any exemption rather than assuming one applies.
Do You Need a Privacy Policy?
For almost every business website that takes enquiries, yes. The more useful questions are what it needs to cover and how to write one that is accurate for your site rather than borrowed from someone else's.
What counts as collecting personal data
Owners sometimes assume that because they do not run a shop or ask people to create accounts, they do not collect anything. It is worth listing what the site actually does:
- Contact and quote forms. Names, email addresses, phone numbers, postcodes and the message itself.
- Booking or appointment tools. Often run by another company, which then holds the details too.
- Newsletter sign-ups. Email addresses, usually stored with a mailing service.
- Chat widgets. Conversations and sometimes contact details, stored by the chat provider.
- Analytics. Depending on the tool and its settings, identifiers and information about visits.
- Hosting and server logs. Many servers record IP addresses for security and troubleshooting.
- Job application forms. CVs and personal histories, which deserve particular care.
Even a site with nothing but a phone number and an email link still has a hosting provider, and often a form somewhere that nobody remembers adding. A short privacy policy is a sensible default for any business site.
What a privacy policy should say
The ICO's guidance on the right to be informed sets out what people should be told. For a typical small business website, that comes down to a handful of plain sections:
| Section | What it answers | An example of the kind of wording |
| Who you are | Who is responsible for the data | The business name, and company number if it is a limited company, plus a contact email |
| What you collect | Which details, from which forms | Name, email, phone number and message from the contact form |
| Why you collect it | The purpose, and the lawful basis | To reply to your enquiry and give you a quote |
| Who else sees it | The services that process it for you | The form provider, the email provider, the hosting company |
| How long you keep it | A retention approach | For as long as the enquiry or resulting work requires, then reviewed |
| Their rights | What people can ask for | Access, correction, deletion, objection, and how to ask |
| Cookies | What the site sets | A short list, or a link to a separate cookie section |
| Complaints | Where to go if unhappy | The ICO, at ico.org.uk |
| Changes | How updates are handled | The date the page was last updated |
The lawful basis is the part people find most daunting. For replying to an enquiry someone has sent you, many small businesses rely on legitimate interests, or on taking steps at the person's request before entering into a contract. For a newsletter, consent is usual. The ICO has an interactive tool for working out which basis fits, and it is worth ten minutes of your time rather than copying whatever another site says.
Two other things often belong alongside the policy. Most organisations that process personal data need to pay a data protection fee to the ICO unless they are exempt, and the ICO's website has a short self-assessment to check. And if a form collects something more sensitive, such as health information for a treatment booking, the bar is higher and specific advice is worth getting.
Writing it in plain English
A privacy policy is meant to be understood by the people it is about. The ICO's own guidance encourages concise, plain language. Long blocks of legal phrasing copied from a template do not make a policy more compliant. They make it less likely that anyone reads it, and more likely that it describes things your site does not do.
A few habits help:
- Use headings that match the questions: what we collect, why, who sees it, how long, your rights.
- Name the forms rather than talking about "data you may provide through various channels".
- Name the services that handle the data, or at least the kind of service, so people know where their details go.
- Say what you do not do, if it is true: you do not sell data, you do not add people to lists they did not ask to join.
- Put a date at the top and change it when the content changes.
A generated template is a reasonable starting point, but read every line against your actual site. Templates commonly mention online payments, account creation, international transfers and advertising partners that a small trade site has never had. Each of those lines is a statement you are making about your business.
Do You Need a Cookie Banner?
This is where most of the anxiety sits, and where most of the unnecessary clutter comes from. The answer depends on what your site actually sets, which is something you can find out.
Which cookies need consent
PECR's exemption covers items that are strictly necessary to provide the service the visitor has asked for. The ICO's guidance treats this narrowly. Necessary for the business is not the same as necessary for the visitor.
| Type | Typical example | Consent usually needed? |
| Shopping basket or login session | Remembering what someone added, or that they signed in | No, strictly necessary |
| Security and load balancing | Protecting a form from abuse, routing traffic | Usually no |
| Remembering a consent choice | Storing that someone declined cookies | No |
| Analytics | Google Analytics and similar tools | Generally yes so far, though new law introduces limited exemptions; check current guidance |
| Advertising and retargeting | Meta pixel, Google Ads remarketing tags | Yes |
| Embedded third-party content | YouTube videos, Google Maps, social feeds | Often yes, if they set their own cookies |
| Chat and review widgets | Live chat bubbles, review carousels | Depends on the provider and what it sets |
The pattern is that the features that need consent are mostly the ones added on top of the site: tracking, advertising and embeds from other companies. A site that is just its own pages and a form often sets very little that needs asking about.
Finding out what your site sets
You do not need to guess. A rough check takes a few minutes:
- Open your site in a private or incognito window so nothing from earlier visits is stored.
- Open the browser's developer tools. In Chrome, right-click, choose Inspect, then the Application tab, and look under Cookies and Local storage.
- Load the homepage without clicking anything and note what appears. Anything non-essential appearing before a visitor has agreed is the first thing to look at.
- Visit a page with a video, map or form and check again. Embeds often add cookies from other domains.
- Note the names and the domains. Searching a cookie name usually tells you which service set it.
Free online scanners can do a similar job, but they only see what loads when they visit. Checking yourself, on the pages customers actually use, is more reliable. If you are not comfortable doing this, whoever looks after the site should be able to give you a list.
This check often turns up surprises: an analytics tag from an old account, an advertising pixel from a campaign that ended, a social feed nobody reads. Removing those reduces what you need to ask about, and as why is my website slow explains, they tend to slow the site down as well.
What a proper banner does
If your site does need consent, the banner has to do the job properly. A banner that says "by using this site you accept cookies" while everything loads regardless does not meet the standard. The ICO has been clear on several points:
- Non-essential items should not load until the visitor agrees. The banner is pointless if the tracking has already run.
- Rejecting should be as easy as accepting. A large Accept button with Reject hidden behind a settings menu is the pattern the ICO has written to organisations about.
- No pre-ticked boxes. Consent has to be an active choice.
- Explain what each category does, in words a visitor understands.
- Let people change their mind, usually through a link in the footer.
On a phone, the banner should not cover the phone number or the contact button so completely that someone has to fight it to get in touch. A small bar with two clear buttons is usually enough. A full-screen overlay is rarely necessary on a small business site and does no favours for the enquiries the site exists to bring in. Mobile responsive web design covers the other things that get in the way on small screens.
A fair test of any banner: could a visitor who wants nothing tracked say so in one tap, and would the site then actually stop loading those things?
The Sites That Need the Least
The simplest way to deal with cookie consent is to need less of it. Every feature that sets non-essential cookies brings a consent question with it. A few choices make a real difference:
- Ask whether you use the analytics. If nobody has opened the analytics account in a year, removing it removes a consent question. If you do use it, look at privacy-focused tools and settings, and check current guidance on what consent they need.
- Use Search Console for search data. Google Search Console reports how often your pages appeared and were clicked in Google, and it does not set cookies on your visitors. How to check your website ranking covers it.
- Load videos and maps on click. A still image that becomes the video when tapped means the third-party cookies only arrive if someone chooses to watch.
- Link to profiles rather than embedding feeds. A link to your Instagram sets nothing. An embedded feed often does.
- Remove old pixels once an advertising campaign has ended.
None of this means a site must avoid every tool. If you run paid adverts and need to measure them, you will need tracking, and with it a proper consent banner. The point is to decide feature by feature, knowing what each one brings.
As one example of how plain this can be, the Operosus privacy policy says its own site does not currently use advertising or tracking cookies, and that consent would be asked for where the law requires it if analytics were enabled in future. That is the sort of statement any small site can make, if it is true for that site.
Common Mistakes
Most problems with privacy policies and cookie banners on small sites are not deliberate. They come from copying, forgetting and adding features without anyone updating the paperwork.
| Mistake | Why it happens | Why it matters |
| A policy copied from another business | Quick, and it looks official | It names the wrong company and describes things your site does not do |
| A template left unedited | Feels safer to include everything | Statements about payments, accounts or advertisers that are untrue for your site |
| A banner that does nothing | Installed for appearance | Tracking loads before consent, which is the thing the rules are about |
| Reject hidden, Accept prominent | Designed to maximise acceptance | The ICO has specifically raised this pattern |
| A banner on a site that sets nothing | Added because everyone else has one | Clutter on a phone for no reason, and a claim that confuses visitors |
| Policy never updated | Written at launch and forgotten | New forms, widgets and tools go undescribed |
| No link from the form | The policy sits only in the footer | People are meant to be told at the point they hand over details |
| Data kept indefinitely | Inboxes and form tools keep everything by default | Holding more than you need for longer than you need it |
The last of those is easy to overlook. Contact form tools often store every submission forever, separately from your inbox. It is worth knowing where enquiries are kept and having a rough habit of clearing out old ones you no longer need. Handling website enquiries covers where enquiries go once they arrive.
A short line under each form, such as "We use these details to reply to your enquiry. See our privacy policy." with a link, does a lot of the transparency work at the moment it matters.
A Small Site Worked Through
Here is an imagined roofer with a five-page site. The business and the details are illustrative, not drawn from a client, but the pattern is common.
What the site does. It has a homepage, three service pages and a contact page with a quote form asking for name, phone, email, postcode and a description of the job. The homepage has an embedded YouTube video of a recent job. Every page has Google Analytics, installed by a previous designer. The footer has a link to a privacy policy.
The privacy policy. On reading it, the owner finds it was generated years ago. It mentions an online shop the business never had, payment processing, and "our partners" for advertising. It does not mention the quote form at all, or the company that provides it. It has no date.
The cookie check. In a private window, the homepage sets Google Analytics cookies straight away and several YouTube cookies from the video, all before anyone clicks anything. A cookie banner exists but only has an OK button, and dismissing it changes nothing.
The decisions. The owner checks the analytics account and finds nobody has logged in for well over a year, so it is removed. Search Console is set up instead for search figures. The video is changed to load only when someone taps a still image, with a short note that it plays from YouTube. With those two changes, the homepage sets nothing non-essential on arrival, and the banner is removed.
The new policy. It is rewritten in plain English. It names the business, says the quote form collects name, phone, email, postcode and job details to reply and quote, names the form provider and email provider, gives a retention approach, lists people's rights with a contact email, mentions the ICO, explains that the video sets YouTube cookies only if someone plays it, and carries the date. A one-line note and link go under the quote form. The owner also checks whether the business needs to pay the ICO data protection fee.
What did not happen. An offer for a subscription consent platform with a full-screen banner is set aside, because the site no longer sets anything that needs consent on arrival.
The result is a shorter policy that is true, no banner covering the quote button on a phone, and a site that is slightly faster than before. If the owner later starts running adverts with tracking, a proper banner with equal Accept and Reject buttons goes back on, and the policy is updated to match.
Questions to Ask Before a Build
If you are planning a new site, this is the cheapest moment to get these things right, because nothing has been added yet. A few questions worth putting to whoever builds it:
- What will the site set on a visitor's device when it first loads, before anyone clicks anything?
- Which third-party services will it load, such as fonts, maps, videos, chat, reviews or analytics, and do any of them set cookies?
- Where will form submissions be stored, and who can see them?
- If consent is needed, will non-essential items actually wait until a visitor agrees, and will rejecting be as easy as accepting?
- Who writes the privacy policy, and who checks it describes this site rather than a template?
- How do I update the policy when I add a newsletter, a booking tool or adverts?
Clear answers to these tell you a fair amount about how carefully the rest of the site will be built. Vague answers, or a suggestion to just add a plugin, are worth questioning. If you are moving from an existing site, the same questions apply to whatever is coming across; moving your website to a new designer covers the wider handover.
The content of the privacy policy is ultimately yours. The builder can tell you what the site does, but only you know how long you keep enquiries, who in the business sees them and whether you pass details to anyone else, such as a subcontractor.
Keeping It Accurate
A privacy policy and cookie set-up that were right at launch drift out of date as the site changes. Most problems arise from additions nobody connected to the paperwork. A few habits keep it in line:
- Whenever you add a form, widget, tool or tracking tag, ask whether the policy and the banner need to change.
- Repeat the private-window cookie check once or twice a year, and after any significant change.
- Remove tools nobody uses, along with their mention in the policy.
- Update the date at the top of the policy whenever the content changes.
- Clear out old enquiries you no longer need from form tools and inboxes.
- Glance at the ICO's guidance now and again, particularly while the newer rules on cookies come into force.
What should happen to your website every month sets out a wider routine that these checks fit into, and who owns your website is worth reading if you are not sure who has access to the accounts where form data ends up.
The short version: if your site collects details through a form, write a short, plain privacy policy that describes what it actually does. Check what the site sets in a private window. If it sets nothing beyond what is strictly necessary, you usually do not need a consent banner. If it does, either remove what you do not need or use a banner that genuinely waits for consent and makes rejecting as easy as accepting.
For most small business websites, none of this is complicated. It is a page of honest description and a few minutes checking what the site loads. Done properly, it means the site tells customers the truth about their details, asks permission only where it has to, and does not put a pop-up between someone and your phone number without a reason.