Laws

Reject All Button Rules: What Regulators Expect

Why EU and UK regulators expect a Reject all button on your cookie banner's first layer, what equal prominence means, the fines behind it and how to design it.

By the allowedit team · · 7 min read

The short answer

  • In the EU and the UK, refusing cookies must be as easy as accepting them. Regulators read that as a Reject all option on the first layer of the banner.
  • Equal prominence means reject is as easy to see, read and click as accept. It doesn't have to be the same colour, but a faint text link next to a bold button fails.
  • The rule has been enforced with real fines, including €210 million against Google and Facebook in France in 2022.
  • A Reject all button usually lowers consent rates a little, and keeps your banner defensible.

If your banner asks for consent in the EU or the UK, it needs a way to refuse that's as easy as accepting, on the first screen people see. In practice that means a Reject all button next to Accept all, just as visible and just as easy to click. Regulators have enforced this with large fines, and it's one of the most checked parts of any cookie banner.

This guide covers where the rule comes from, what "equal prominence" means, and how to design a banner that meets it without looking like a legal notice.

Where does the rule come from?

Not from a single sentence of law. It follows from three requirements in the GDPR:

  • Consent must be freely given (Article 4(11)). If refusing is harder than accepting, the choice is pushed one way.
  • Withdrawing consent must be as easy as giving it (Article 7(3)). If accepting takes one click, refusing shouldn't take four.
  • Consent must be unambiguous, which rules out treating silence or closing as acceptance.

Regulators turned those principles into a practical expectation. In January 2023, the European Data Protection Board's Cookie Banner Taskforce reported that a large majority of national regulators consider a banner with no reject (or equivalent) option on the first layer, where accept is offered, to be a breach.

Which fines made this clear?

France's regulator, the CNIL, has been the most active.

WhenWhoFineWhy
December 2020Google, Amazon€100m and €35mCookies set on arrival without consent, among other issues
January 2022Google (€150m), Facebook (€60m)€210m combinedRefusing cookies took several clicks, accepting took one
2022 to 2024Several large sites, including Microsoft (Bing)Tens of millions of eurosMissing or harder refusal, cookies set before consent

The January 2022 decisions are the clearest statement of the rule: the CNIL said that making refusal more complicated than acceptance discourages people from refusing and pushes them to accept, so consent isn't freely given.

In the UK, the ICO has written to many of the country's most visited sites, telling them to give people a fair choice between accepting and rejecting, and warning that it would act against those that didn't.

What does "equal prominence" mean?

Reject must be as easy to see, read and click as accept. The Taskforce report lists the patterns regulators have objected to:

  • Reject hidden in a second layer. Accept on the banner, reject only inside "Settings".
  • Reject as a text link. A bold Accept button next to a small "continue without accepting" link.
  • Low contrast. Light grey text on a white background for reject, a strong colour for accept.
  • Misleading wording. "Necessary only" that still loads analytics, or labels that hide what the button does.

Equal prominence doesn't mean every pixel must match. But the closer the two buttons look, the less there is to argue about.

Good

Accept all and Reject all as two buttons of the same size and style, with Customise beside them. All three on the first layer.

Risky

Accept all as a filled button, Reject all as an outline button of the same size with readable contrast. Most regulators would accept this, but some reviewers prefer identical styles.

Bad

Accept all as a big coloured button, with "Manage options" as a small link that leads to a panel of switches and a Save button.

Usually, yes, a little. When refusing is as easy as accepting, more people refuse. How much depends on your audience and your banner.

That's the point of the rule. A consent rate inflated by making refusal hard isn't real consent, and the data behind it is the data a regulator would question. A lower rate built on fair choices is one you can defend.

Two things help keep the rate healthy:

  1. Say why, briefly. "We use analytics to see which pages help people, and ads to reach new customers" reads better than a paragraph of legal terms.
  2. Use Google Consent Mode. In advanced mode, Google models conversions from people who declined, so your reports don't drop as sharply. See Consent Mode v2, explained.

How should the buttons be labelled?

Plain, parallel words work best:

  • Accept all / Reject all / Customise
  • Allow all / Deny all / Choose

Avoid labels that blur the meaning, like "OK" for accept (unclear on a consent banner), "I understand" (sounds like a notice), or "Continue" (doesn't say what happens).

What happens after someone rejects?

Clicking the button is only half of it. After Reject all:

  1. No analytics, marketing or preference cookies should be set.
  2. Scripts in those categories should not load, or should stop on the next page view.
  3. Google tags should receive a Consent Mode update that keeps everything denied.
  4. The choice should be remembered, so the banner doesn't reappear on every page.
  5. The visitor should be able to change their mind later, through a floating settings button or a footer link.

The CNIL recommends remembering a refusal for about six months before asking again. Asking on every visit after a refusal is itself a form of pressure.

You can check the first three points with the free cookie checker, which loads your page, records what's set before any choice, and flags trackers that ignore it.

What about the US?

US state privacy laws use an opt-out model, not opt-in. Tracking can run by default, but visitors must be able to opt out of the sale or sharing of their data, usually through a "Do not sell or share my personal information" link, and their browser's Global Privacy Control signal must be honoured. A Reject all button isn't required, though showing one does no harm. Our post on CCPA and Global Privacy Control covers it.

How allowedit handles it

allowedit's cookie banner shows Reject all on the first layer by default, and by default it uses the same filled style as Accept, so the two match. If you choose the outline style for Reject and Customise instead, they stay the same size and sit on the same row, so check the contrast in the live preview before you publish.

The region rules apply opt-in with Reject all to visitors in the EU and EEA, the UK, Switzerland and Quebec. Visitors in the 19 US states with privacy laws see an opt-out with "Do not sell or share my personal information". Everyone else gets a notice or nothing, your choice.

Every choice, including rejections, goes in the consent log with a random consent id, the time, the choices, the banner version and the region, so you can show what each visitor saw and chose. No IP addresses are stored.

The short version

Put Reject all next to Accept all, make them look alike, and make sure Reject actually stops the trackers. It's a small design change that removes the most common reason cookie banners get flagged. The rest of the checklist is in cookie banner requirements under GDPR.

This article summarises regulator guidance and decisions. It isn't legal advice.

Frequently asked questions

Is a Reject all button legally required?

The GDPR doesn't use the words, but it requires that refusing is as easy as accepting and that consent is freely given. Most EU regulators, and the UK's ICO, say a banner with Accept on the first layer and no equivalent way to refuse there doesn't meet that standard.

Can I use a close button (X) instead of Reject all?

Some regulators accept closing the banner as a refusal, if it's clear that closing means no and nothing optional runs afterwards. A labelled Reject all button is clearer and is the safer choice everywhere.

Do I need Reject all for US visitors?

Not in the same way. US state laws use an opt-out model: tracking can run, but visitors must be able to opt out of the sale or sharing of their data, through a clear link. Many sites still show Reject for US visitors because it's simple.

Does Reject all have to be the same colour as Accept all?

Not exactly the same, but it must be just as visible. Regulators have objected to grey-on-white reject links next to bright accept buttons. Using the same style for both is the simplest way to be safe.