Security & Privacy

Cookie Consent Banners: Getting Them Right in Canada, the UAE and the EU

How cookie consent expectations differ across Canada, the UAE and the EU, and how to design a banner that actually controls scripts without hurting the user experience.

Illustration of a website with a cookie consent banner offering accept, reject and settings buttons, framed by three regional flags as abstract shapes

Most business websites now show a cookie banner, yet many of those banners do not actually do anything. Analytics and advertising tags load before the visitor clicks, "Reject" is buried two screens deep, and nobody can say which scripts are on the site. That is a compliance problem and a trust problem. This guide covers cookie consent compliance for businesses operating in Canada, the UAE and the EU: what each region broadly expects, how to design a banner people can actually use, and how to make sure the technology respects the choice. It is general guidance, so confirm your specific obligations with a privacy lawyer.

Cookies and similar technologies (local storage, pixels, device fingerprinting, SDKs) let websites remember sessions, measure usage and track visitors for advertising. Privacy laws care about the information collected and how it is used, not the specific technology. A consent banner exists to:

  1. Tell visitors which non-essential tracking takes place.
  2. Let them choose whether to allow it.
  3. Ensure the website honours that choice.
  4. Keep a record of what was chosen.

If your banner does only the first of these, it is decoration.

European Union

The EU has the most prescriptive regime. The ePrivacy rules require consent before storing or reading non-essential information on a user's device, and the GDPR defines what valid consent means: freely given, specific, informed, unambiguous and given through a clear affirmative action. In practice:

  • No non-essential cookies or tags before consent.
  • No pre-ticked boxes; scrolling or continuing to browse is not consent.
  • Refusing should be as easy as accepting.
  • Consent must be granular by purpose and withdrawable at any time.

These rules can apply to non-EU businesses that target or monitor people in the EU.

Canada

PIPEDA requires meaningful consent, with the form of consent depending on the sensitivity of the information and the reasonable expectations of the individual. The Office of the Privacy Commissioner has indicated that online behavioural advertising requires at least clear notice and an easy opt-out, and that express consent is appropriate in more sensitive or unexpected situations. Provincial laws also matter: BC and Alberta have their own private-sector laws, and Quebec's Law 25 requires that technologies used to identify, locate or profile a person be deactivated by default, with users informed and able to activate them. Our guide to PIPEDA for websites explains the broader framework.

United Arab Emirates

The federal Personal Data Protection Law treats consent as a central lawful basis and sets conditions for it to be specific, clear and withdrawable. The DIFC and ADGM have their own data protection regimes modelled closely on European principles. While the UAE has not published cookie rules as detailed as the EU's, aligning with the consent conditions is the prudent approach. See our UAE PDPL guide for website owners for more context.

Topic EU Canada UAE
Non-essential cookies before choice Not allowed Depends on sensitivity; opt-in safest for tracking (default-off in Quebec) Consent-based approach recommended
Pre-ticked boxes Not valid Not recommended Not recommended
Easy refusal Expected Expected (opt-out at minimum) Expected (withdrawal must be easy)
Granular purposes Expected Good practice Good practice
Record of consent Expected Good practice Good practice

Key takeaway: If your website serves visitors from several regions, designing to the stricter EU-style standard is usually simpler than maintaining region-specific behaviour, and it builds trust everywhere.

Designing a banner people can actually use

A good banner is short, honest and fast.

First layer

  • One or two sentences explaining what you use cookies for, in plain language.
  • Accept all, Reject non-essential and Settings buttons with equal visual weight.
  • A link to your cookie or privacy policy.
  • No blocking of the whole page unless genuinely necessary.

Settings layer

  • Categories such as Necessary (always on), Preferences, Analytics and Marketing.
  • A short description of each category and the main providers involved.
  • Toggles that are off by default for non-essential categories.
  • A Save choices button.

After the choice

  • A persistent link (for example "Cookie settings" in the footer) to change preferences at any time.
  • Re-prompt when you add new purposes or vendors.

Accessibility and language

  • Keyboard navigable, with visible focus and proper labels for screen readers.
  • Sufficient colour contrast; do not grey out the reject button.
  • Translated fully, including right-to-left layouts for Arabic or Persian sites.
  • Lightweight, so it does not hurt your Core Web Vitals.

Making the technology respect the choice

This is where most implementations fail. Follow these steps:

  1. Inventory every script and cookie. Crawl the site, check your tag manager and ask marketing what has been added.
  2. Classify each item as necessary, preferences, analytics or marketing.
  3. Block non-essential scripts by default. Load them only after the relevant category is accepted, either through your consent platform's script blocking or through your tag manager's consent settings.
  4. Configure consent modes for advertising and analytics platforms that support them, so they adjust behaviour based on the user's choice.
  5. Handle embeds. Video players, maps and social widgets often set tracking cookies; use privacy-enhanced modes or click-to-load placeholders.
  6. Test in a clean browser. Before clicking anything, check the network tab and cookie storage. Nothing non-essential should appear.
  7. Log consent. Store a timestamp, consent version and the choices made, without storing more personal data than needed.
  8. Re-test after every marketing or plugin change.

The easiest banner to manage is one with little behind it. Options include:

  • Remove tools nobody looks at.
  • Replace third-party analytics with privacy-friendly or self-hosted analytics such as Dideban Analytics, which keeps data on your own servers. Our comparison of Google Analytics alternatives covers other options.
  • Use server-side measurement for key conversions where appropriate and lawful.
  • Avoid loading advertising pixels on pages where they add no value, such as account areas.

Common mistakes

  • Analytics firing before the banner appears.
  • "Reject" hidden in settings or styled as a faint text link.
  • Banner covers the page on mobile and the close button is off-screen.
  • Categories listed but toggles do nothing.
  • Cookie policy last updated years ago and listing tools no longer used.
  • No way to change a choice later.

Consent setups usually break because nobody owns them. Marketing adds a pixel for a campaign, a developer installs a chat widget, and the banner never hears about either. Agree a simple process:

  1. Marketing requests any new tag or tool and explains its purpose.
  2. The developer or agency classifies it, adds it to the consent configuration and confirms it does not load before consent.
  3. Whoever owns privacy updates the cookie and privacy policy where needed.
  4. Someone checks the live site in a clean browser after the change.

Keep a short register of every tool, its category, its owner and the date it was added. When a tool is no longer used, remove it from the site, the tag manager and the register at the same time. This register also makes answering a regulator, a client questionnaire or a curious customer much easier.

Next steps

Open your website in a private browser window, do not click the banner, and check which cookies and network requests appear. That five-minute test tells you whether your current setup works.

DigiVort can audit your scripts, implement a consent setup that genuinely controls them and reduce your tracking footprint through our security and compliance service and analytics and growth service. If you are planning a new site, start a project and we will design consent in from the beginning.

Frequently asked questions

Do strictly necessary cookies need consent?

Under EU rules, cookies strictly necessary to provide a service the user requested, such as a session or shopping cart cookie, are generally exempt from consent. You should still describe them in your cookie or privacy policy. Canadian and UAE expectations are similar in principle.

Is an 'implied consent' banner enough in Canada?

Implied consent can be acceptable under PIPEDA for less sensitive uses that people would reasonably expect, provided there is clear notice and an easy opt-out. For behavioural advertising and more intrusive tracking, express consent is the safer approach, and Quebec's Law 25 sets stricter expectations for tracking technologies.

Do we need a banner if we only use privacy-friendly analytics?

It depends on the tool, its configuration and the regions you serve. Cookieless, aggregate analytics hosted on your own infrastructure reduces the privacy impact considerably and, in some EU countries, may qualify for exemptions under specific conditions. Take local advice before removing a banner.

How long should we remember a user's choice?

Long enough not to nag users, but not indefinitely. Many sites re-ask after six to twelve months, or sooner when the purposes or vendors change. Whatever you choose, document it and apply it consistently.

Can we make the 'Reject' button smaller or hidden in settings?

In the EU, regulators have repeatedly criticised designs that make refusing harder than accepting. Present accept and reject with equal prominence on the first layer. It is also simply better practice for user trust in every market.