Consent models

Understand different consent models.

Privacy laws do not all require the same type of consent. Learn how opt-in, opt-out and region-specific consent models work, and how CookieHub helps you support different requirements from one setup.

Consent modelvisitor journey
Opt-in
  1. 1Visitor arrives
  2. 2Non-essential tracking waits
  3. 3Visitor actively chooses
  4. 4Consent state updates
Opt-out
  1. 1Visitor arrives
  2. 2Notice and preferences are available
  3. 3Visitor can refuse or opt out
  4. 4Preferences update
Regional requirements

The applicable consent model depends on the market.

Privacy regulations take different approaches to consent. Some require prior opt-in before non-essential tracking, while others rely more heavily on notice and the ability to opt out.

Browse privacy regulations
In practice

From regulation to visitor choice.

  1. 01

    Identify the applicable requirements

    Understand which privacy regulations apply to your visitors and website.

  2. 02

    Present the appropriate consent experience

    Use the consent model and controls required for that context.

  3. 03

    Respect and maintain the visitor’s choice

    Apply and update preferences as visitors make or change decisions, and maintain consent records where enabled.

CookieHub

One platform for different consent requirements.

CookieHub can present different consent experiences and apply the matching technical behaviour, based on the requirements you configure for your website.

FAQ

Consent model questions, answered.

A consent model describes when tracking may begin and what choice a visitor is given. The two most common are opt-in and opt-out; some markets focus mainly on notice.

Under an opt-in model, non-essential tracking waits until the visitor makes an affirmative choice. Visitors should be able to change or withdraw that choice later.

Under an opt-out model, certain processing may begin while visitors are informed and given a clear way to refuse or opt out, and to change their preferences.

It depends on factors such as where your visitors are, what data you collect and how you use it, and the specific regulations that apply. For a definitive answer, seek legal advice.

Yes. Visitors from different jurisdictions can be subject to different requirements, so one website may need to present different consent experiences.

CookieHub lets you configure the consent experience and behaviour for the requirements that apply to your website. Choosing the right configuration remains your responsibility, and using CookieHub does not by itself guarantee compliance.

Get started

Support consent requirements across different markets.

CookieHub helps you manage visitor choices and adapt your consent setup to different privacy requirements.