cookie-noticeconsent

Cookie notice, cookie banner, cookie policy: what's the difference?

Three phrases that get used as if they mean the same thing. They don't, and the one you're missing is usually the one that matters.

23 August 2026 · Diffuse · 4 min read

If you have gone looking for a way to handle cookies on your website, you have probably seen these three phrases used as if they are interchangeable.

They are not. And the difference is worth five minutes, because the piece people usually skip is the piece that actually does the work.

The banner is the box on the screen

That is it. The banner is the thing visitors see: the bar along the bottom or the little window that appears asking about cookies.

It is the most visible part and, on its own, the least useful.

A banner that pops up, collects a click, and changes nothing behind the scenes is decoration. This happens more often than you would think. Someone adds a banner because the site needed one, and it never gets connected to the things it is supposed to be controlling.

Think of it like a light switch that is screwed to the wall but not wired to anything. It looks right. It clicks. The light does not change.

The policy is the page that explains

The cookie policy is a page on your site, usually linked in the footer, that lists what your website stores, what each thing is for, and how long it stays.

It is not the same as your privacy statement, though plenty of sites combine them. That is fine, as long as the cookie detail is genuinely in there and someone can find it.

The usual problem with cookie policies is not that they are missing. It is that they were written once, three years ago, and the site has picked up a chat widget and two embedded videos since.

The notice is the whole thing working together

This is the one people mean when they say they need "a cookie notice", even if they are picturing the banner.

A cookie notice is the banner, plus the choice it collects, plus remembering that choice, plus, most importantly, actually acting on it.

For it to be doing its job:

  1. Nothing optional runs until someone says yes
  2. Saying no is as easy as saying yes
  3. The choice is remembered for next time
  4. The choice is applied straight away on the next visit, before anything loads
  5. Visitors can change their mind later without hunting for it

Points 1 and 4 are the ones that get skipped, because you cannot see them by looking at the page.

How to tell which piece you are missing

Open your own site in a private window and refuse everything. Then:

  • Cookies appear anyway? You have a banner, not a notice. It is not wired up.
  • Nothing explains what the cookies do? You are missing the policy.
  • The banner asks again every single visit? The choice is not being remembered.
  • No way to change your mind? That needs to be there, and it needs to be about as easy as agreeing was.

Why this matters when you are buying

Because it decides what you are actually getting.

A banner is the easy part, an afternoon's work. Holding back the optional stuff, remembering what people chose, and applying it properly next time is the hard part, and it is the part that counts.

Plenty of tools sell you a banner and let you assume you bought a notice.

When you are comparing options, do not look at the screenshot of the banner. Ask one question: what actually happens when someone says no?

Our Cookie Notice tool covers all five points above, including the ones you cannot see from the page.


This is general guidance, not legal advice. If your site handles anything sensitive, it is worth asking someone qualified where you are.