Ad-blockers & Safari ITP

We'd rather tell you plainly what does and doesn't work than let you find out from a support ticket. This page covers the two known edge cases in normal operation.

Ad blockers

Some ad blockers and privacy extensions block requests to third-party consent/tag-management scripts, which can include f.js. If that happens on a given visit:

• The inline Consent Mode stub (see install.md) has already run and set every category to denied — that part doesn't depend on f.js at all.
• f.js never loads, so the banner never renders, window.consentfolio is never defined, and no dashboard-configured script URL or data-cf-consent-marked script is ever activated for that visitor.

The result: that visitor never sees a cookie banner and is never counted as having consented to anything beyond strictly necessary. It's a lost opportunity to collect analytics or ad consent from them — but it is fail-closed, not a compliance gap. Nothing non-essential ever runs without a recorded grant.

The same logic applies if a blocker lets f.js load but blocks the config or consent-receipt requests specifically: no config means the banner can't render correctly, and denied defaults simply stay in place.

Safari Intelligent Tracking Prevention (ITP)

Consentfolio stores a visitor's choice in localStorage first, with a JS-set cookie as a fallback, and an in-memory fallback if neither is available (so a visit never crashes even with storage disabled).

Safari's ITP caps the lifetime of cookies that are set by JavaScript (rather than by a server Set-Cookie header) at roughly 7 days. For visitors whose consent record ends up relying on that cookie, this means the record can expire well before the normal 12-month consent validity window, and the visitor may be re-prompted sooner than they would be in other browsers.

This is a known, accepted trade-off of the current storage approach rather than a bug — we're documenting it rather than hiding it. If you have a meaningful Safari audience and this matters to your reporting, expect a modest rate of "early" re-prompts from returning Safari visitors that you won't see from Chrome or Firefox visitors.