Lynbro Cookie Consent

By lynbro

★ 5.0/5 (3 ratings)100+ active installationsVersion 0.4.21

Free, multilingual cookie consent banner — GDPR/ePrivacy & Google Consent Mode v2 ready, equal Reject button, no pageview limits.

Description

A free, multilingual and fully configurable cookie consent banner for WordPress.
It is GDPR/ePrivacy and Google Consent Mode v2 ready out of the box, with an
equally prominent “Reject all” button (in line with Datatilsynet / EDPB guidance)
and no pageview or domain limits. Everything runs locally — no account, no cloud,
no external requests on the front end.

This plugin helps you with cookie compliance but does not constitute legal advice.

Source code and issue tracker on GitHub:
https://github.com/andrey-tut/lynbro-cookie-consent

Free features:

  • Accessible banner in the footer with equal Accept all / Reject all / Save
    preferences buttons (rejection-equality, no dark patterns).
  • Granular consent categories: Necessary (always on), Preferences, Statistics,
    Marketing — with per-category toggles and descriptions.
  • Script blocking before consent: mark scripts as
    type=”text/plain” data-lynbro-cc=”statistics|marketing” and they only run
    after the matching category is granted. Helper function included.
  • Google Consent Mode v2 — free: all signals default to “denied” before consent
    (ad_storage, analytics_storage, ad_user_data, ad_personalization,
    functionality_storage, personalization_storage, security_storage), updated
    after the visitor chooses.
  • Geo-aware consent model: EU/EEA/UK → opt-in, US → opt-out (CCPA/CPRA), rest of
    world → notice. Region detected from CDN/edge headers (e.g. Cloudflare); safe
    opt-in fallback when unknown. No external geolocation API.
  • Embed/iframe consent placeholders: YouTube, Vimeo, Google Maps, social embeds,
    reCAPTCHA and more are blocked until consent and replaced with a tidy,
    translatable placeholder with an “allow” button (and an optional “always allow
    this service” choice). Zero layout shift — placeholders reserve the iframe size.
  • Automatic blocking of well-known trackers by a built-in catalog (Google
    Analytics/GA4, Google Tag Manager, Meta Pixel, Hotjar, Microsoft Clarity,
    LinkedIn, TikTok and more) in addition to manual script marking — whether the
    tag is enqueued by a plugin or pasted into the page by a theme, a header-code
    plugin or a page builder. Extendable via a filter. Tags hard-coded in a
    theme’s header.php above wp_head() run before any plugin can act; move them
    into a header-code plugin and they are blocked too.
  • Global Privacy Control (GPC): honors the browser opt-out signal and, in
    opt-out mode, automatically applies it with a visible confirmation (California
    CPRA 2026).
  • CCPA / CPRA “Do Not Sell or Share My Personal Information” link in opt-out mode.
  • Cache & performance friendly: the consent core is automatically excluded from
    delay/defer/minify/combine of WP Rocket, LiteSpeed, SiteGround Optimizer,
    Autoptimize and Cloudflare Rocket Loader, with zero layout shift (CLS).
  • Full customization without code: light/dark/auto theme (follows the visitor’s
    system), separate light and dark color sets, position (bottom bar, top bar,
    floating box with corner choice, center modal), live admin preview and a
    WCAG-AA contrast validator.
  • Floating “Cookie settings” button (toggle, corner, label, icon) plus the
    shortcode [lynbro_cookie_settings] to re-open the banner at any time.
  • Local consent log (proof of consent) stored in your own database — with the
    policy version, chosen categories, method, language and region, and an
    anonymised hash instead of a raw IP address. Includes an admin viewer and a
    full CSV export of the entire log.
  • WP Consent API compatible: registers as the consent provider and notifies other
    plugins (functional / preferences / statistics / marketing).
  • Settings import/export (JSON), per-page/post exclusions and policy versioning
    with automatic re-consent when the version changes. No “accept on scroll”.
  • Accessibility: visible focus, ARIA roles, focus trap in the modal, large touch
    targets, RTL ready, reduced-motion support.
  • Private, cookieless statistics — stored only in your own database and fully
    aggregated (no IP address, no visitor identifier, no personal data). See how
    many visitors accept, reject or open preferences, the accept rate per period,
    the average time to decision and the browser-language / device / OS mix. On by
    default; can be turned off in one click.
  • Optional benchmark sharing (off by default): when you opt in, the plugin sends
    only aggregated weekly numbers and your site domain to the Lynbro portal so you
    can see how your accept rate compares to the average. No visitor data is sent.
  • Built-in feedback form: send ideas, requests or bug reports to the developers
    straight from the admin (only when you click Send).
  • Language on demand: request a translation for a locale that isn’t bundled; it
    is stored in your uploads folder (update-safe) and activated automatically.
  • Lightweight vanilla JavaScript (no jQuery), no front-end external requests
    beyond an optional, non-blocking statistics beacon to your own site.
  • Truly multilingual and cache-safe: the initial banner language follows a
    cache-safe cascade (current page language of Polylang/WPML/TranslatePress →
    site language → English). Optional browser auto-detection and an in-banner
    language switcher pick the best language entirely in the visitor’s browser,
    so full-page caches are never affected.
  • Edit banner texts per language in the admin (title, description, buttons,
    category names and descriptions), with the priority your override → bundled
    translation → default. You can even add your own locale and texts.
  • Fully translatable. Ships with 35 bundled languages — including all 24
    official EU languages (Danish, German, French, Spanish, Italian, Dutch,
    Polish, Swedish, Greek and more) — plus any other locale on demand and via
    translate.wordpress.org.
  • Developer-friendly: filters and a JS API
    (window.LynbroCookieConsent.getConsent() / .openSettings() / .onChange()).

Every feature listed here is included for free, with no pageview limits and
nothing locked behind a paywall.

External Services

By default this plugin runs locally, and it also stops WordPress itself from
loading emoji images from WordPress.org (s.w.org) on the front end (setting
“Emoji images from WordPress.org”, on by default). The banner, script blocking, automatic
tracker detection, embed placeholders, Google Consent Mode v2 signalling,
geo-aware consent mode, Global Privacy Control handling, the local consent log
and the local statistics all work on your own server and in the visitor’s
browser, with no account and no third-party API.

The local statistics use a small, non-blocking beacon that is sent only to your
own WordPress site
(the same domain) to count aggregated events. It does not
contact any third party and stores no IP address or personal data.

Three optional features can contact the Lynbro portal at
https://plugins.lynbro.dk. None of them runs automatically without your action,
and none of them sends a visitor IP or any personal data:

  1. Benchmark sharing (telemetry) — off by default. When you turn it on, a
    weekly background job sends aggregated counters for the last 7 days (banner
    shown / accept / reject / manage-open / language-switch totals, the average
    time-to-decision, and the browser-language / device / OS distributions) plus
    your site’s domain to https://plugins.lynbro.dk/v1/telemetry. The portal
    returns an anonymous benchmark so you can compare your accept rate to the
    average. Sent only while the option is enabled.

  2. Feedback — sent only when you submit the feedback form in the admin. It
    posts your message, the chosen category, the plugin version, your site domain
    and (optionally) the email you type, to https://plugins.lynbro.dk/v1/feedback.

  3. Language on demand — sent only when you click “Request this language”. It
    posts the plugin slug, the plugin version and the requested locale code to
    https://plugins.lynbro.dk/v1/i18n/translate, and stores the returned
    translation file in your site’s uploads folder. No visitor data is involved.

Your use of these optional portal features is governed by the Lynbro Privacy
Policy and Terms at https://plugins.lynbro.dk.

Note: any third-party scripts or embeds you add to your own site (for example
Google Analytics, Meta Pixel or a YouTube video) continue to contact their own
providers — but only after the visitor grants the matching consent category. This
plugin’s role is to gate them, not to add them.

WordPress.org plugin directory (the shared Lynbro “Our plugins” screen).
Apart from the above, one request goes to WordPress.org, from every Lynbro plugin
alike: when an administrator who may install plugins opens Lynbro → Our plugins,
the screen asks the WordPress.org Plugin Directory API
(https://api.wordpress.org/plugins/info/1.2/) which Lynbro plugins are listed,
through WordPress core’s own plugins_api() — the same call the Plugins → Add New
screen makes.

  • What is sent: the query (plugins by the author “lynbro”), plus what WordPress
    core adds to every request to WordPress.org: your WordPress version, the admin
    language and, in the User-Agent, your site address. Nothing about your visitors,
    users or content.
  • When: only on that screen, at most once a day (the answer is cached for a day;
    after a failed request, an hour). No other screen and no visitor request triggers it.
  • Installing a suggested plugin uses WordPress core’s own installer, which downloads
    the plugin from downloads.wordpress.org — only when you click “Install now”.
  • WordPress.org Terms of Service ·
    Privacy Policy

Privacy

The plugin stores data only in your WordPress database (your settings and, if
enabled, the local consent log and the local aggregated statistics) and in
first-party cookies on the visitor’s browser (their consent choice and, if used,
the chosen banner language). The consent log never stores a raw IP address — only
a salted, anonymised hash for de-duplication. The statistics are fully aggregated
and contain no IP address or visitor identifier; they are recorded via a
non-blocking beacon to your own site only.

The optional portal features — benchmark sharing (telemetry), the feedback form
and language-on-demand — are opt-in and described in the “External services”
section above. They send aggregated data and your site domain only, never a
visitor IP or personal data, to https://plugins.lynbro.dk. See our Privacy Policy
and Terms there. GDPR/DK compliant.

Installation

Install

From your dashboard (recommended):

  1. Go to Plugins → Add New and search for “Lynbro Cookie Consent”.
  2. Click Install Now, then Activate.

Or upload it manually:

  1. Download the .zip and go to Plugins → Add New → Upload Plugin, choose the
    file and click Install Now, then Activate. (Or extract the folder to
    /wp-content/plugins/lynbro-cookie-consent and activate it from the Plugins screen.)

It works out of the box

On activation the banner goes live immediately with safe, GDPR-ready defaults — an
equally prominent “Reject all”, all non-essential cookies denied until consent, and
Google Consent Mode v2 set to “denied”. You do not have to configure anything to be
compliant. Everything below is optional fine-tuning under Settings → Cookie Consent.

Recommended first steps

  1. Categories — review the consent categories (Necessary, Preferences, Statistics,
    Marketing) and edit their names/descriptions if you like.
  2. Region mode — choose how consent behaves by region (EU/EEA opt-in, US opt-out
    / CCPA, rest-of-world notice), or keep the safe opt-in default.
  3. Block your scripts — for trackers added by hand, mark them as
    (or marketing);
    well-known trackers (GA4, GTM, Meta Pixel, Hotjar, Clarity, …) are auto-blocked.
  4. Google Consent Mode v2 — if you use Google Analytics/Ads/Tag Manager, leave it
    enabled; signals default to “denied” and update to the visitor’s choice automatically.
  5. Design — pick a layout (bottom/top bar, floating box, center modal), colours and
    the floating “Cookie settings” button, with a live device-switchable preview.
  6. Languages — 35 languages ship in the box; enable browser auto-detection and the
    in-banner switcher, or edit texts per language (you can add your own locale too).

Verify

Open your site in a private window — the banner should appear. Choose an option, then
re-open it via the floating button or the [lynbro_cookie_settings] shortcut to change
it. Proof-of-consent records and cookieless statistics appear under
Settings → Cookie Consent → Consent Log / Statistics.

FAQ

Is it really completely free?

Yes. The plugin handles the complete compliance flow — banner, categories,
script blocking, Google Consent Mode v2, geo-aware modes, analytics, the consent
log and translations — with nothing locked behind a paywall and no pageview
limits. There is nothing to buy.

Does it call any external service?

By default the front end makes no third-party requests: the visitor’s choice is
kept in a first-party cookie, and the optional statistics beacon goes only to
your own site (same domain). Three features can contact the Lynbro portal, and
all three are opt-in actions you control: benchmark sharing (off by default),
the feedback form (only when you click Send) and “request a language” (only when
you click Request). Each sends aggregated data only — never a visitor IP or any
personal data. See the “External services” section below for full details.

How do I block my analytics/marketing scripts until consent?

Output them as <script type="text/plain" data-lynbro-cc="statistics">...</script>
(or marketing). They are activated automatically once the visitor grants that
category. A helper function lynbro_cookie_consent_blocked_script() is provided.

Does it support Google Consent Mode v2?

Yes, for free. Signals default to “denied” before consent and are updated to
match the visitor’s choice.

How does the banner choose its language?

It uses a cache-safe cascade: the current page language (when Polylang, WPML or
TranslatePress is active), then your site language, then English. If you enable
“auto-detect visitor language”, the banner additionally picks the best of your
offered languages from the visitor’s browser — and that choice is made in the
browser, so it never breaks full-page caching. You can also enable an in-banner
language switcher. Texts can be overridden per language under Settings → Cookie
Consent → Languages, including adding your own locale.

Does it block embedded videos and maps?

Yes. With “Embed placeholders” enabled, iframes from YouTube, Vimeo, Google Maps,
social networks, reCAPTCHA and similar providers are blocked until the visitor
consents (or clicks “allow” on the placeholder). The detection is local; no
external request is made to identify or block an embed.

Does it honor Global Privacy Control (GPC)?

Yes. In opt-out (US/CCPA) mode, visitors whose browser sends a GPC signal are
automatically opted out of non-essential cookies and shown a visible
confirmation, as required by California from 2026.

Where is the consent log stored?

In a dedicated table in your own WordPress database. No raw IP address is stored;
only a salted, anonymised hash is kept for de-duplication. You can view recent
records and export the complete log as CSV from Settings → Cookie Consent →
Consent Log.

Is it compatible with caching plugins?

Yes. Consent state lives client-side (first-party cookie + JS), so it is never
baked into cached HTML, and the consent core is automatically excluded from
delay/defer/minify/combine of WP Rocket, LiteSpeed, SiteGround Optimizer,
Autoptimize and Cloudflare Rocket Loader.

Screenshots

Changelog

0.4.21

  • Improvement: on phones (480 px and narrower) the banner is compact — the text is shortened to two lines with a “Show more” toggle, “Reject all” and “Accept all” sit side by side with the same size and style, and “Manage preferences” is a quieter text button below. On a 375 px screen the banner now takes well under a third of the height instead of almost half. Desktop is unchanged.
  • Fix: the banner follows the language of the page (<html lang>), not the visitor’s browser: an English browser on a Danish page now sees the Danish banner. The browser language is only used when the page language is not one of the offered languages. A language picked in the switcher is remembered for pages in the same language.

0.4.20

  • Fix: importing a settings file always failed with “Please upload a .json settings file” — WordPress does not list .json as an upload type, so every exported file was refused. The file is now checked by its .json name and its content, as before.
  • Fix: on the Languages tab, the “Read more” link and the “Always on” badge could not be translated — the text was dropped on save in every language, so the banner kept the English words.
  • New: “Remember the choice for (days)” on the Consent Mode tab — how long accepting or rejecting is remembered before the banner asks again (1 to 365 days, 365 by default).

0.4.19

  • The Google Consent Mode defaults really are the first thing in now. 0.4.18 moved them up, but they still came out after tags another plugin or a header snippet prints early, so Google tags could start before the “denied” defaults were set.

0.4.18

  • Important: pasted tracking snippets now wait for consent. Automatic blocking only caught scripts a plugin added with wp_enqueue_script(); the usual Google Analytics (gtag) and Meta Pixel snippets — pasted in the theme, a header/footer code plugin or a page builder — ran before the visitor chose, sent a page view and set the _ga cookie. A small script at the very top of now holds every tag from the tracker catalog (including those a snippet injects, like the Pixel loader and GTM) until its category is granted, and the banner starts them after “Accept”. Rejecting keeps them out. The browser may still fetch the gtag file, but it does not run.
  • The Google Consent Mode defaults are printed at the very top of , before tags other plugins print early.

0.4.17

  • No emoji images from WordPress.org: WordPress swaps emoji for images from s.w.org in browsers without an emoji font, sending the visitor’s IP address to WordPress.org before any consent. A new setting (Blocking tab, on by default) leaves emoji to the visitor’s own font and drops any s.w.org resource hint. Admin, editor, feeds and e-mails are untouched. Filter lynbro_cookie_consent_local_emoji.

0.4.16

  • Never two banners: when Complianz, CookieYes, Cookiebot or Borlabs Cookie is active, this plugin stays silent on the front end — no banner, no script blocking, no Consent Mode defaults, no consent records, not registered with WP Consent API. Its settings screen names the active plugin and offers to bring over its banner texts (every language CookieYes has), categories and policy link; the dashboard and Plugins screen point there. Deactivate the other plugin and our banner takes over.
  • The banner announces its height through the Lynbro bottom-inset contract (rank 30), so the floating chat button and other bottom bars sit above it instead of on top of it — on show, when the preferences open, on resize, and 0 once it is closed.

0.4.15

  • On a multilingual site (Polylang, WPML, TranslatePress, Lynbro Translate) the banner now speaks the page’s language. Before, an English browser or an earlier choice in the banner’s language menu won, so a Ukrainian page could show an English banner. Single-language sites keep the old order: remembered choice, then the browser, then the site language.
  • WPML: the banner used the site’s default language instead of the current page’s.
  • Preferences view at tablet width: with long button labels (Ukrainian, German) the last button ran off the screen; the buttons now wrap.
  • Settings screen: the device switch above the live preview is reachable by screen readers again (only the preview itself is hidden from them), and the grey language codes meet WCAG AA contrast.

0.4.14

  • Readme: External Services now names the one WordPress.org request the shared “Our plugins” screen makes — what is sent, when, and the WordPress.org terms and privacy policy.
  • The plugin names and descriptions on “Our plugins” and in the suggestions are translatable.
  • Links on Lynbro screens use the darker brand green, which meets WCAG AA contrast on the admin background.

0.4.13

  • Shared Lynbro admin 1.1.0: after two weeks of use and a first success (for example settings saved), this plugin’s own screen asks once, politely and without stars, whether it is doing its job. Answers are per user: “Maybe later” or “Don’t ask again”, and only one Lynbro plugin asks in any 30 days.
  • A small “Suggested for this site” block under the plugin’s main screen lists Lynbro plugins that fit what the site already uses (WooCommerce, forms, a Danish setup …), with the reason. It can be hidden; nothing installs on its own and nothing is sent anywhere.
  • Tab labels on Lynbro screens meet WCAG AA contrast.
  • Lynbro admin screens now read the plugin’s bundled translations (languages/) when WordPress has no language pack for it, so a Danish admin sees Danish instead of English.

0.4.12

  • Fix: every consent record was counted twice against the per-visitor limit (WordPress asks the permission check again while building the Allow header), so after 15 decisions a minute from one address – an office, a school, a mobile network – further records were refused instead of after 30.

0.4.11

  • Blocked embeds without width/height attributes (e.g. the Elementor Google Maps widget) get a 300px placeholder instead of a 16:9 box that pushed the page content far below the fold.
  • Placeholder text no longer overlaps when a page builder sets line-height 0 on the embed wrapper.
  • Width/height inside an embed’s URL are no longer mistaken for its size.

0.4.10

  • Banner statistics over the per-visitor limit are dropped quietly (204) instead of a 429 that showed as a console error.

0.4.9

  • Fix: in the box layout the banner had an empty gap above the buttons on wide screens.
  • The keyboard focus ring follows the banner colours instead of a fixed blue.
  • Fix: the “Always on” badge now switches language with the rest of the banner.

0.4.8

  • Fix: the banner could switch to English on a non-English site when the
    translations came from WordPress.org language packs instead of files inside
    the plugin folder. Language packs and downloaded translations are now used
    for the banner text too.

0.4.7

  • Fix: on sites with a page cache, consent records and banner statistics from
    visitors could be silently rejected once the cached page was older than a day
    (the security token embedded in the page had expired). Anonymous visitors no
    longer need that token; the endpoints stay rate-limited and validate every
    field. Logged-in users are checked as before.
  • Fix: pages already cached with an expired token record consent again right
    after the update, without waiting for the cache to clear.

0.4.6

  • Translations: refreshed and quality-reviewed all 35 bundled languages for more
    natural, glossary-consistent wording.
  • Fix: on mobile, the Statistics and Consent Log tables in the admin could push
    the page wider than the screen; each table now scrolls horizontally on its own.

0.4.5

  • Fix: on mobile, opening “Manage preferences” could make the dialog overflow
    horizontally (the categories view wrapped into a second column, forcing
    sideways scrolling to reach the buttons). The dialog now stays a single column
    and scrolls vertically instead.

0.4.4

  • Fix: on mobile the bar layout could stretch to most of the screen height with a
    large empty gap between the text and the buttons. The banner body now sizes to
    its content, the content packs to the top, and the bar never exceeds 85% of the
    viewport. Added slightly smaller mobile font sizes for the title and text.

0.4.3

  • Compliance: tracker-blocking no longer emits literal script tags from PHP — the
    enqueued-script filter now modifies the existing tag in place, and the manual
    helper builds the inert placeholder without a literal script tag.

0.4.2

  • Admin: hide the Save button on tabs without editable settings.

0.4.1

  • Compliance: the consent-log CSV export now exports the complete log (the
    previous row limit was removed); large logs are streamed in batches.
  • Compliance: removed the “Additional CSS” field — use the WordPress Customizer’s
    built-in Additional CSS instead.
  • Compliance: refactored script handling — the Google Consent Mode v2 default
    stub is now enqueued via wp_add_inline_script, and the optional full-page
    output-buffer scan was removed (enqueued-tracker blocking is unchanged).
  • Hardening: the consent-gated script helper now guards inline bodies against a
    breakout.

0.4.0

  • New: private, cookieless, aggregated statistics stored in your own database —
    accept/reject/manage-open counts, accept rate per period (today, yesterday, 7,
    30 and 365 days), average time-to-decision and browser-language / device / OS
    distributions. No IP address and no personal data. Recorded via a non-blocking
    same-site beacon. On by default; one click to disable.
  • New: optional benchmark sharing (off by default) — opt in to send aggregated
    weekly numbers and your site domain to the Lynbro portal and see how your
    accept rate compares to the average.
  • New: in-admin feedback form to send ideas, requests and bug reports (opt-in).
  • New: “request a language” — fetch a translation for a non-bundled locale; it is
    stored in your uploads folder (update-safe) and activated automatically.
  • New: a “Settings” link in the plugins list, a one-time redirect to the settings
    after activation, and a single, gentle, dismiss-forever review reminder after a
    week (no nags, no pressure).
  • Improved: Danish (da_DK) translation updated to cover all new strings.

0.3.0

  • New: cache-safe browser language auto-detection — the banner can show in the
    visitor’s browser language (chosen client-side, so caching is unaffected).
  • New: optional in-banner language switcher with a remembered choice.
  • New: per-language text editor in the admin (title, description, buttons,
    category names/descriptions), with priority override → translation → default,
    plus the ability to add your own locale.
  • New: “About” tab with author info, useful links and a version/updates note.
  • New: quick-start status block confirming the banner is live with the key
    toggles at a glance.
  • Improved: removed the explicit textdomain loader; bundled translations now
    load just-in-time (cleaner Plugin Check, no behaviour change).
  • Improved: Danish (da_DK) translation updated to cover all new strings.

0.2.0

  • New: embed/iframe consent placeholders (YouTube, Vimeo, Google Maps, social
    embeds, reCAPTCHA and more) with “allow” and “always allow this service”.
  • New: Global Privacy Control (GPC) support with a visible opt-out confirmation.
  • New: explicit cache compatibility (auto-exclusion from WP Rocket, LiteSpeed,
    SiteGround Optimizer, Autoptimize, Cloudflare) and zero layout shift.
  • New: light/dark/auto theme with separate dark color set and custom CSS.
  • New: floating “Cookie settings” re-open button (toggle, corner, label, icon).
  • New: WP Consent API compatibility (registers as the consent provider).
  • New: live admin preview with a WCAG-AA contrast validator.
  • New: center-modal layout with a focus trap, and a box-corner choice.
  • New: local consent log (proof of consent) with admin viewer and CSV export.
  • New: automatic blocking of well-known trackers by a built-in catalog.
  • New: settings import/export (JSON), per-page/post exclusions, policy versioning
    with automatic re-consent.
  • New: CCPA/CPRA “Do Not Sell or Share” link in opt-out mode.

0.1.0

  • Initial release: banner, granular categories, script blocking, Google Consent
    Mode v2, geo-aware consent modes, shortcode, accessibility, English + Danish.