Borlabs Cookie vs Real Cookie Banner

Borlabs Cookie

Consent runs at group and single-service level, a freely positionable icon lets visitors reopen and change their choices, and the banner is stated WCAG 2.1 AA with over 150 styling options, eight professional languages plus automatic translation, and an EU versus non-EU rule. I found no public information on A/B testing of banner variants or on accept and reject being pinned to equal prominence as a default, which is the testing my ad revenue lives on.

Real Cookie Banner

Customisation runs deep — 20+ design templates with 200+ options, 19 languages, per-vendor consent through the TCF layer, per-country banner rules via a locally stored MaxMind database, and WCAG 2.2 Level AA with keyboard navigation and an accessibility score in the customiser. But we found no public information on reject carrying the same weight as accept on the first layer, on how visitors change their choice later, or on A/B testing — only aggregated consent statistics are documented, which is the gap that hurts my banner testing most.

Borlabs Cookie

Content blockers come vendor-maintained for over 370 packages alongside a script and style blocker, an audit scan checks the site sets no cookies or external content without consent, and the Google Tag Manager path is documented in depth — template, per-service opt-in events, local container hosting and its stated limits. I found no public information on server-side tagging support.

Real Cookie Banner

Templates block data processing before consent, 130+ content-blocker templates cover named services with lazy loading for embeds, a Google Tag Manager integration option is documented alongside a JavaScript and developer API, and the knowledge base walks through testing that nothing is set before consent. We found no public information on server-side tagging support or an automated monitor reporting early-loading scripts on the live site.

Borlabs Cookie

The scanner covers cookies, external resources and consent-requiring functions, reaches HTTP-Auth areas and custom URLs, and the vendor is transparent that it scans a defined subset — home page, one older and one newer page per post type, archives, legal notice and contact form. I found no public information on scheduled rescans, alerts on new trackers, or a cookie declaration that updates itself from the scan.

Real Cookie Banner

This is a service scanner, not a cookie scanner — it crawls the sitemap, detects iframes, script tags, installed plugins and HTTP-header services, and suggests manually researched templates from a library of 160+, with the limits of what it finds stated unusually openly. It explicitly does not scan specific cookies, we found no public information on scheduled rescans or alerts on changed trackers, and the cookie policy document is generated from the banner configuration rather than from scan results.

Borlabs Cookie

Consent logs document consents including their changes over time, every byte sits on the customer's own server, consent is asked again when services change or after a configurable lifetime, and consent is shared across domains and multisite instances. I found no public information on retention for the log, an export format, a banner version per record, or a consent ID the visitor can look up — exactly what I would need to answer an authority.

Real Cookie Banner

Each consent is stored in my own WordPress database with a server-generated pseudonymous UUID, the services and groups consented to, and a revision hash tying the record to the exact banner settings shown, with any configuration change forcing re-consent; the list is viewable and exportable in the backend, and consents forwarded from other sites are marked. We found no public information on a consent ID the visitor could look up, withdrawal recorded as its own event, or a stated retention period for the consent log itself.

Borlabs Cookie

IAB TCF 2.4 is stated as certified with the Global Vendor List downloaded and the TC string attached to defined links, Consent Mode v2 works in basic and advanced mode with all consent types and default-denied documented, and Microsoft UET consent mode is listed as included — the core of my ad stack. The pages I read give no registered CMP ID number, no naming as a Google-certified CMP, and no public information on GPP or Global Privacy Control for US states or on iOS and Android SDKs, so consent shared between my site and an app is not evidenced.

Real Cookie Banner

TCF 2.2 is implemented with weekly Global Vendor List updates and vendor management, and Google Consent Mode v2 transmits automatically via the Google Tag including additional consent types to Google Tag Manager — the core of what my Ads conversions need. The captured pages give different statements on Google certification (one calls the product a CMP certified by Google for AdSense, others state it is not part of the Partner Program), and we found no public information on a registered IAB CMP ID, on Consent Mode advanced mode by name, on Microsoft UET, GPP or GPC for US states, or on app SDKs — the product runs on WordPress.

Borlabs Cookie

The contracting entity is Borlabs GmbH in Hamburg with registry court, register number and German VAT ID published, the plugin keeps all data on the customer's own server and transmits no visitor data to the vendor, and subprocessors are named with their countries together with a data processing agreement available for support access. I found no public information on security certifications or on the ownership behind the company, and the Amazon SES mention in the website privacy policy is not separated from product-related email.

Real Cookie Banner

The whole consent chain sits on my own server — the plugin runs in my WordPress, the banner is served from my webspace with nothing loaded from the vendor's servers for visitors, the vendor states it has no access to settings or documented consents, and the contracting entity is a German GmbH with full register details at the Deggendorf court. Against that, no data processing agreement is offered for operation (the vendor's documented legal position, with one available for support access), subprocessors for the license and update services are not listed, activation telemetry includes consent counts, and we found no public information on security certifications or ownership.

Borlabs Cookie

Plans scale publicly by website count with euro prices — from €49, then 179 € per year for 10 sites up to 499 € per year for 99 — with unlimited pageviews and subpages, TCF and Consent Mode included in the plans, VAT treatment stated as prices excluding VAT, cancel anytime and a 30-day money-back guarantee. The captured pages do not itemise the tiers between the entry price and the 10-website plan, so the annual cost for a single small property is only partly computable.

Real Cookie Banner

All five tiers are published with gross annual prices scaling by number of websites (59 € to 299 €), every tier includes all features, updates and premium support, staging environments are included in equal number, VAT treatment and cancellation terms are stated, and a free sandbox and a free version exist. Expert setup by the vendor's cookie experts and the enterprise tier above 25 websites are the pieces we found no public prices for, and a single extra domain beyond a tier is not priced individually.