Limits and compatibility

Knowing the limits of a tool is part of using it well. This page lists them honestly.

#Not included

• IAB TCF. The banner does not implement the Transparency and Consent Framework used by some advertising networks.
• Google-certified CMP. It is not a Google CMP partner. It does support Consent Mode v2.
• Global Privacy Control. The banner does not automatically treat the Global Privacy Control signal as a refusal.
• Server-side tools other than through the Cloudflare Zaraz connection.
• Region rules. The banner asks everyone. It does not show different banners by country.

#Cannot be intercepted

Dynamic imports, WebSocket connections, document.write scripts, images set in style sheets and trackers placed before the banner script. See Blocking before consent.

#Browser limits

• Browsers cap cookie lifetimes. Safari limits cookies written by scripts, which can shorten how long the banner's own choice cookie lasts, so Safari visitors may be asked again earlier than the period you set.
• A visitor who blocks all cookies in their browser cannot save a choice and may see the banner on each page.
• Visitors using content blockers may not load the banner at all, in which case no trackers load either.

#Your responsibility

The banner helps you obtain and record consent. What your site loads, and what your declaration says, remains your responsibility. Use the site check regularly, because sites change.

#FAQ

#Why not TCF?

TCF is built for advertising networks with many partners. Privacyboard focuses on small businesses, and many do not need it. If a partner requires it, check their requirements first.

#Does it work with single-page apps?

The banner loads once and applies to the page as a whole, so navigation inside the app does not ask again.