Cookie Banners and Privacy Notices: The Basics for Small Business Websites
Almost every small business website now runs something that stores data in a visitor's browser: an analytics tag, an ad pixel, a chat widget, an embedded video or a booking tool. Whether you need a cookie banner, and what it has to do, depends on where your visitors are and what those tools actually do, not on whether other sites have one.
This guide explains the basics in plain English: the rules behind cookie banners in the EU and UK, the opt-out model used in California, what regulators say a valid banner looks like, and where Google Consent Mode fits. It is general information, not legal advice. If you handle sensitive data, sell to customers across several countries or are unsure whether a law applies to you, talk to a privacy lawyer.
Key facts
- 7 — Consent types Google Consent Mode can pass, from ad_storage to security_storage
- $26.6M — CCPA annual revenue threshold since 1 January 2025 (one of three tests)
- 15 — Business days California allows to act on a Do Not Sell or Share request
- 0 — Non-essential cookies the ICO says should run on the landing page before consent
Why Cookie Banners Exist
In the EU, the rule comes from Article 5(3) of the ePrivacy Directive. In the UK, the equivalent is the Privacy and Electronic Communications Regulations (PECR). Both say you may only store information on a visitor's device, or read information already stored there, if you tell them clearly what you are doing and get their consent, unless an exception applies.
Two details catch people out:
- It is not only cookies. The UK Information Commissioner's Office (ICO) says the rules also cover similar technologies, including tracking pixels, scripts and software development kits (SDKs). Local storage and fingerprinting-style techniques fall under the same idea.
- Third-party tools count as yours. If you add a pixel or embed that sets cookies, you are responsible for telling visitors about it and, where needed, getting consent before it runs.
Consent here uses the GDPR definition: a freely given, specific, informed and unambiguous indication of the visitor's wishes, given by a clear affirmative action. That definition is what drives most of the design rules below.
What Needs Consent and What Doesn't
The main exception is for storage that is strictly necessary to provide a service the visitor has asked for. The ICO stresses that this means essential, not merely useful, and that it is judged from the visitor's point of view rather than the site owner's. Examples it gives include a cookie that remembers what is in a shopping basket and cookies needed for security on a login.
Typical tools on a small business site sort roughly like this:
- Usually exempt: session cookies for a cart or checkout, login and security cookies, load-balancing cookies, and a cookie that stores the visitor's consent choice itself.
- Usually need consent: advertising and retargeting pixels (Meta, Google Ads, LinkedIn and similar), cross-site tracking, and embeds that set third-party tracking cookies.
- It depends: analytics. Under EU guidance, analytics cookies have generally needed consent. In the UK, the ICO's current guidance on storage and access technologies lists an exception for statistical purposes, with conditions: the only purpose is measuring how your service is used so you can improve it, you explain it clearly, you give a simple, free way to object, and any analytics provider acts only on your behalf. It does not cover profiling, tracking individuals or advertising.
Even exempt cookies should still be explained in your privacy or cookie notice. The exception removes the need for consent, not the need to tell people.
What a Valid Consent Banner Looks Like
The European Data Protection Board's guidelines on consent and the ICO's cookie guidance agree on most of the practical points. A banner that collects valid consent:
- Blocks non-essential tags until the visitor chooses. The ICO says non-essential cookies should not be set on the landing page before consent. A banner that appears while the ad pixel has already fired does not do its job.
- Offers a real choice. Visitors who refuse must still be able to use the site. The EDPB says making access conditional on accepting cookies (a "cookie wall") means consent is not freely given.
- Requires an action. Scrolling, swiping or simply continuing to browse is not consent, according to both the EDPB and the ICO. Pre-ticked boxes and sliders that start in the "on" position are not valid either.
- Is specific. Let visitors choose by purpose, such as analytics or advertising, rather than one all-or-nothing switch hidden behind a settings link.
- Can be changed later. Withdrawing consent should be as easy as giving it. A small "Cookie settings" link in the footer that reopens the choices is the common way to do this.
Many consent management platforms (CMPs) can do all of this, but none of them are compliant out of the box. The categories, the default state and which scripts are blocked are settings you have to get right.
The US Picture: Opt-Out Instead of Opt-In
US privacy laws mostly work the other way round. California's Consumer Privacy Act (CCPA), as amended by the CPRA, does not require a consent banner before analytics or ad cookies. It gives California residents rights, including to know what you collect, to delete it, to correct it and to opt out of the "sale" or "sharing" of their personal information. Sharing has a specific meaning here: passing data for cross-context behavioural advertising, which is what many ad pixels do.
The CCPA only applies to for-profit businesses that do business in California and meet at least one of three tests. According to the California Attorney General and the California Privacy Protection Agency, those are:
- annual gross revenue above $26,625,000 (adjusted from $25 million on 1 January 2025);
- buying, selling or sharing the personal information of 100,000 or more California consumers or households; or
- getting 50% or more of annual revenue from selling personal information.
A business that is covered and sells or shares data must provide a clear "Do Not Sell or Share My Personal Information" link, must not make people create an account to use it, and must act on requests within 15 business days. It must also treat a browser's Global Privacy Control (GPC) signal as a valid opt-out. Browsers that support it send a Sec-GPC: 1 request header, and sites can read it in JavaScript:
if (navigator.globalPrivacyControl) {
// Treat this visitor as opted out of sale and sharing
}Other US states have passed their own privacy laws with different thresholds and rights, so check which apply if you have customers in several states.
Where Google Consent Mode Fits
Google Consent Mode is often confused with a banner, but Google's documentation is clear that it is not one. You are still responsible for getting consent, with a banner, a CMP or your own solution. Consent Mode is the layer that passes the visitor's choice to Google tags so they change how they behave.
It works with seven consent types: ad_storage, ad_user_data, ad_personalization, analytics_storage, functionality_storage, personalization_storage and security_storage. Each is set to granted or denied.
There are two ways to implement it:
- Basic: Google tags do not load until the visitor interacts with the banner. If they refuse, nothing is sent to Google, not even the consent state.
- Advanced: Google tags load straight away with consent defaulted to denied, and send cookieless pings until the visitor accepts. Google uses those pings for more detailed conversion modelling.
Basic is the simpler and more cautious choice. If you consider advanced, make sure your privacy notice explains it and that the approach fits the rules where your visitors are.
Writing the Privacy Notice and Testing Your Setup
Your banner is only half the job; the notice behind it has to say what is going on. The ICO says visitors should be told which cookies you set, what they do, which third parties receive the information and how long the cookies last. Grouping cookies by purpose usually reads better than one long table.
A practical routine for a small site:
- Inventory everything. List every tag, pixel, embed and plugin, including ones added through Google Tag Manager or a page builder.
- Remove what you don't use. Every tool you delete is one less thing to disclose and one less script slowing the page.
- Sort by purpose into strictly necessary, analytics, functionality and advertising, then configure the banner to block each non-essential group until consent.
- Test in a private window. Open your browser's developer tools, check the storage panel (Application in Chrome, Storage in Firefox) before you click anything, and confirm only essential cookies are present. Then refuse, reload and check again.
- Recheck after changes. New plugins, a new ad campaign or a theme update can add tags without anyone noticing, so add this to your regular maintenance list.
If you're in scope for California's law, add the opt-out link and GPC handling to the same checklist, and keep the privacy policy's "last updated" date honest.
Sources
- ICO: What are the rules on cookies and similar technologies?
- ICO: Storage and access technologies, what are the exceptions?
- EDPB: Guidelines 05/2020 on consent under Regulation 2016/679
- California Attorney General: California Consumer Privacy Act (CCPA)
- California Privacy Protection Agency: Updated monetary thresholds in the CCPA
- Google for Developers: Consent mode overview
- MDN: Sec-GPC header
Related reading
Frequently asked questions
Does a small US business website need a cookie banner?
Not always. US laws such as California's CCPA use an opt-out model and only apply to businesses that meet certain thresholds. If you have EU or UK visitors and use non-essential cookies such as ad pixels, their rules can require consent first. Check where your visitors are and what your tools do, and ask a privacy lawyer if unsure.
Are Google Analytics cookies strictly necessary?
No. Analytics is not treated as strictly necessary. In the EU it has generally needed consent. In the UK, the ICO's current guidance lists an exception for purely statistical analytics with conditions, including clear information and a simple way to object.
Is Google Consent Mode the same as a cookie banner?
No. Google says consent mode does not collect consent. You still need a banner or consent platform; consent mode passes the visitor's choice to Google tags so they adjust what they store and send.
Want a cookie setup you can actually explain?
Tell me what tools your site runs and I'll send you a free, no-obligation quote for a clean, tested consent setup.
Get a free quote