Is BannerBye actually refusing?
This page reads the exact signals BannerBye hands to every website — and decodes them in front of you. No trust required.
Reading the signals…
Give it a second.
Get BannerBye- Purposes consented
- —
- Vendors consented
- —
- Global Privacy Control
- —
Decoded live from the string below. Zero is the number you want.
What this browser sent
The IAB TCF consent string found on this page:
| Field | Value | Meaning |
|---|
Decode any TC string
Paste a consent string from any site — the euconsent-v2 cookie, or what __tcfapi('getTCData') returns — and see what it actually says. Everything runs in your browser; nothing is sent anywhere.
| Field | Value | Meaning |
|---|
What you're looking at
Most European sites run a consent management platform that speaks the IAB Transparency & Consent Framework. Before that platform decides whether to show you a banner, it looks for an existing answer: a TC string on window.__tcfapi and in the euconsent-v2 cookie. BannerBye puts that answer there first, at document_start, before the site's own scripts run. The answer is no — to all 24 purposes, all special features and every vendor.
A string is only an answer if it decodes. The decoder on this page is written independently of the extension, and every BannerBye build is checked against the IAB Tech Lab reference library before it ships: service-specific scope, policy version 5 and the vendor-disclosure segment the framework has required since 2026.
Global Privacy Control is the second signal: a browser flag and an HTTP header (Sec-GPC: 1) that say "do not sell or share my data". This page can read the flag; the header is only visible to the server, so it isn't shown here.
Not every banner speaks TCF. For the rest, BannerBye has recognised handlers for the big consent platforms and a pattern-based fallback that clicks "reject" for you. Those don't show up on this page — how it works explains every layer.
Something looks off? Open BannerBye and hit Report broken site, or write to hello@bannerbye.com.