Let users see what "Accept" and "Decline" actually do.

Pilot setup

Zero-risk test on one page or template. You keep 100% of all banner ad revenue during the pilot. We measure consent-rate lift and banner economics against your existing banner via a 50/50 A/B split.

How it works

1. First-layer replacement — Our overlay replaces your CMP's first layer; consent is stored via your CMP.
2. Pre-choice and post-choice flows — Pre-choice: no ads are shown. Decline triggers NP path; Accept triggers P path (with purge).
3. Resurfacing — Your CMP controls re-prompt policy. We report the observed encounter rate.

Frequently asked questions

What regulatory validation do you have?

We received non-binding Innovation Advice from the UK Information Commissioner's Office (ICO) in February 2026 (case ref 00000118), confirming the approach can be permissible when no storage/access occurs before consent, the presentation is not framed as reward/penalty, and content shown is explanatory rather than persuasive. Our design is aligned to GDPR, ePrivacy, and TCF 2.2 requirements.

Does this replace our CMP?

No. DecidePrivacy overlays the first layer only and writes consent via your existing CMP. Your CMP remains the system of record for consent storage and vendor management.

Do you show ads before consent?

No. Nothing is shown before a user makes their choice. Pre-choice: no ads are displayed. Only after the user accepts or declines do we trigger the appropriate ad path.

Which CMPs do you support?

We integrate with TCF 2.2-compliant CMPs. Detailed integration specifications are shared during the pilot onboarding process.

What do you need from us?

Page URL, CMP provider, traffic estimate, and ad stack context. We'll work with your team to configure the integration during onboarding.

How is impact measured?

Via A/B testing on eligible consent encounters. We report overall metrics plus a Safari split to account for browser-specific behaviors.

Is this 'consent or pay'?

No. Users choose between personalized ads, non-personalized ads, or granular options — all free. There is no paywall.

What happens after the pilot?

If KPIs are met, we discuss commercial terms. If not, there's no obligation. Pilot revenue is retained by the publisher regardless of outcome.

How long does integration take?

Typically 1–2 weeks for technical integration, followed by a 3–6 week pilot period to reach statistical significance.

About DecidePrivacy

DecidePrivacy is a consent-layer technology that makes cookie choices visible and understandable by showing what changes after a user decides—without showing personalized advertising before consent.

We help publishers protect revenue while offering a clearer, more respectful consent experience.

What we build

DecidePrivacy turns the first-layer cookie banner into an outcome-shown consent layer:

• Before a choice: the banner is inert (no personalized advertising, no ad-tech activity triggered).
• If the user rejects: the banner can render a real non-personalized (NP) creative.
• If the user accepts: the banner can render a real personalized (P) creative.

Principles

• No pre-choice personalization
• No pre-choice ad-tech activity
• Plain-language UX
• Compliance-first design, not coercion

Founded by Alex Novikau, a leading privacy professional with a background in humanitarian protection. Patent pending.

Privacy Notice

DecidePrivacy is a project operated by a private individual in Denmark. For privacy questions, use the contact form on the website.

We process: contact form submissions (name, email, company, message), demo access logs (invitation tokens, IP addresses, user agents), and standard web analytics via Cookiebot-managed cookies.

Legal bases: consent (contact form), legitimate interest (demo access security), and contract performance. Data is stored in the EU via Supabase. You may exercise GDPR rights (access, rectification, erasure, restriction, portability, objection) by contacting us.

Demo and Website Terms of Use

By accessing the DecidePrivacy website or using the gated demo, you agree to these terms. The website and demo are provided for evaluation and informational purposes only.

You may not: share invitation tokens or bypass access controls; reverse-engineer the consent banner technology; use the demo for competitive analysis without written permission; or scrape, crawl, or bulk-download site content.

All content, designs, software, and the underlying consent banner methodology are the intellectual property of DecidePrivacy. Patent pending. These terms are governed by the laws of Denmark.

Resources

Insights on consent UX, publisher economics, and privacy-first advertising.

• Non-personalised advertising: what it earns, what it costs, and why it is growing — When a user rejects cookies, the ads change — and the revenue drops 5x to 8x. Most publishers have no strategy for their fastest-growing inventory segment.
• The EU Digital Omnibus proposal: what it means for cookie banners — The European Commission's November 2025 proposal would fold cookie consent into GDPR, exempt analytics cookies, and mandate browser-level consent signals. Here is what publishers need to prepare for.
• Encounter rate: the consent metric that changes everything publishers think they know — The encounter rate — the share of sessions where the banner actually appears — is the multiplier between consent lift and revenue impact. Most publishers do not measure it.
• Safari, ITP, and the consent metric most publishers get wrong — Safari's Intelligent Tracking Prevention resets consent storage every 7 days. The result: Safari users see the consent banner 3–5x more often than Chrome users, dragging down aggregate accept rates and hiding the real economics.
• What the latest CNIL cookie fines tell publishers about consent design risk — In September 2025, CNIL fined Google €150M and SHEIN €150M for cookie consent failures. What these cases reveal about where enforcement is heading — and what publishers should check now.
• The consent rate problem: what it actually costs European publishers — Most European publishers running an honest consent banner see accept rates between 30–50%. This article breaks down what that gap actually costs in revenue terms.
• TCF 2.2 first-layer requirements: what publishers actually need to show — The first layer is the only part of the consent experience that nearly every user sees. This article walks through what TCF 2.2 actually requires.
• How to measure consent banner performance: a publisher guide — Most publishers track consent with a single metric. This guide covers the three baseline metrics, experiment sizing, and common measurement errors.
• Outcome transparency: showing users what their consent choice means — Consent banners tell users what data processing they agree to — but not what happens as a result. This article examines making consequences visible.
• What actually happens when you click Accept All on a cookie banner — The technical chain from consent click to rendered ad — consent strings, real-time auctions, identifier sync, and why the user understanding gap matters.
• What research tells us about consent decisions, ad relevance, and outcome transparency — Research across behavioural economics, advertising science, and consumer surveys shows that consent behaviour is shaped by trust, interface design, and the perceived value of what users are consenting to.