Bato Web Agency

<p>Bato Cookie Consent adds a configurable cookie consent interface to WordPress. It provides an admin settings screen for banner content, policy links, consent categories, cookie lifetime, floating preferences button, and Google Consent Mode integration.</p>
<p>The plugin is built for site owners and developers who need a local, customizable consent banner without loading third-party assets by default.</p>
<h4>Features</h4>
<ul>
<li>Consent banner with accept all, reject all, and custom preferences actions.</li>
<li>34 built-in frontend languages with browser/site language detection and RTL support for Hebrew and Arabic.</li>
<li>Necessary, analytics, marketing, and preferences categories.</li>
<li>Editable banner, modal, button, category, and embed placeholder text.</li>
<li>Privacy policy and cookie policy links.</li>
<li>Floating preferences button after a visitor has saved choices.</li>
<li>YouTube and Vimeo embed placeholders that can wait for marketing consent.</li>
<li>Developer filter for adding scripts, embeds, and advanced configuration.</li>
<li>Optional Google Consent Mode updates when <code>gtag</code> is already present on the site.</li>
<li>Translation-ready PHP and JavaScript strings.</li>
</ul>
<h4>Supported Languages</h4>
<p>The frontend consent interface includes built-in content for 34 languages: Arabic, Bulgarian, Catalan, Croatian, Czech, Danish, Dutch, English, English (UK), Estonian, Finnish, French, German, Greek, Hebrew, Hungarian, Italian, Japanese, Latvian, Lithuanian, Macedonian, Norwegian, Polish, Portuguese, Romanian, Russian, Serbian, Slovak, Slovenian, Spanish, Swedish, Turkish, Ukrainian, and Welsh.</p>
<p>The plugin can follow the visitor’s browser language, auto-detect the WordPress site language where possible, or use a fixed language selected in the settings.</p>
<h4>Privacy</h4>
<p>Bato Cookie Consent stores the visitor’s consent choices in the visitor’s browser using a cookie or local storage, depending on the plugin settings. The plugin does not collect personal data, send analytics, or contact external servers by default.</p>
<p>If you configure third-party scripts or embeds, those services may process visitor data according to their own terms and privacy policies. The plugin can help delay those scripts or embeds until the relevant consent category is allowed, but it does not guarantee legal compliance. Site owners are responsible for configuring the banner, policies, and scripts for their jurisdiction.</p>
<h4>Developer Usage</h4>
<p>Developers can extend the frontend configuration with the <code>bato_cookie_consent_config</code> filter:</p>
<pre><code>add_filter('bato_cookie_consent_config', function ($config) {
    $config['scripts'][] = array(
        'id' => 'analytics',
        'category' => 'analytics',
        'src' => 'https://example.com/analytics.js',
        'async' => true,
    );

    return $config;
});
</code></pre>
<p>Source files and build tooling are included with the plugin. To rebuild production assets, run:</p>
<pre><code>npm install
npm run build
</code></pre>
<h3>Third-Party Notices</h3>
<p>Bato Cookie Consent includes or builds with the following third-party packages. These licenses are GPL-compatible according to the GNU project’s GPL-compatible license list. Apache License 2.0 is compatible with GPLv3, so the plugin package is licensed as GPLv3 or later.</p>
<h4>Runtime assets</h4>
<ul>
<li><code>@bato-web-agency/cookie-consent</code> – MIT License</li>
<li><code>@mdi/font</code> – Apache License 2.0</li>
<li><code>vue</code> – MIT License</li>
<li><code>vuetify</code> – MIT License</li>
</ul>
<h4>Build tooling</h4>
<ul>
<li><code>@vitejs/plugin-vue</code> – MIT License</li>
<li><code>vite</code> – MIT License</li>
</ul>
<p>Dependency metadata is recorded in <code>package-lock.json</code>.</p>


Bato Cookie Consent

Adds a customizable multilingual cookie consent banner with 34 supported languages, categories, policy links, embeds, and developer filters.

Ontario

<p>Plain Cookie Consent is a no-frills GDPR + ePrivacy consent banner for WordPress. It ships a single banner, Google Consent Mode v2 defaults, a server-side audit log with pseudonymised subject hashing, a DSAR lookup helper, and constant-gated Meta Pixel / Microsoft Clarity / LinkedIn Insight Tag helpers — all under GPL v2, with no upsells and no external telemetry.</p>
<p>The plugin is designed to support a GDPR/ePrivacy-compliant consent setup. Final compliance depends on the site owner’s configuration and linked privacy policy.</p>
<h4>Core compliance features</h4>
<ul>
<li>Google Consent Mode v2 defaults injected at <code>wp_head</code> priority 1, before any tag manager or gtag snippet.</li>
<li>Early inline consent replay with a revision gate — consent recorded before a policy revision bump is not replayed; the banner re-prompts instead.</li>
<li>Server-side audit log (<code>wp_plain_consent_log</code>) with a privacy-preserving SHA-256 subject hash over a daily-rotating salt, and a 730-day default retention purge (filterable via constant).</li>
<li>Consent revision system with a “Force re-consent for all users now” admin action and strict rollback if the audit insert fails.</li>
<li>Two-step choice pattern: the first layer offers Accept All and Show Options; the preferences screen (one click away) offers equal-weight Accept All, Reject All, and Save Preferences buttons.</li>
<li>Server-mirror consent cookie via a cache-safe <code>GET /mirror-nonce</code> endpoint (<code>Cache-Control: no-store</code>), so full-page caching does not break nonce validation.</li>
<li>Geo targeting: the consent-required region set is the EEA (EU-27 plus Iceland, Liechtenstein, Norway) plus the United Kingdom. Detection uses the Cloudflare <code>CF-IPCountry</code> header when present, with a fail-safe default: if the country cannot be determined, the visitor is treated as in-scope.</li>
<li>CSV/JSON streamed export of the consent log, plus a pre-uninstall evidence warning with one-click export.</li>
<li>DSAR lookup admin tool: recompute a visitor’s subject hash from IP + User-Agent and list matching consent-log entries (GDPR Art. 15 support).</li>
</ul>
<h4>Integrations</h4>
<ul>
<li>Meta Pixel: define <code>PLAIN_COOKIE_CONSENT_FACEBOOK_PIXEL_ID</code> in <code>wp-config.php</code>.</li>
<li>Microsoft Clarity: define <code>PLAIN_COOKIE_CONSENT_CLARITY_PROJECT_ID</code> in <code>wp-config.php</code>.</li>
<li>LinkedIn Insight Tag: define <code>PLAIN_COOKIE_CONSENT_LINKEDIN_PARTNER_ID</code> in <code>wp-config.php</code>.</li>
<li>Public <code>window.plainCookieConsent</code> JavaScript API (<code>getCategories</code>, <code>hasConsent</code>, <code>onChange</code>, <code>onGrant</code>, <code>onRevoke</code>) for site-specific vendors.</li>
<li>Cookie cleanup on revoke with curated defaults for LinkedIn, TikTok, Hotjar, Clarity, Yandex Metrica, and Snapchat (<code>plain_cookie_consent_autoclear_cookies</code> filter).</li>
<li><code>localStorage</code> / <code>sessionStorage</code> cleanup on a real granted-to-revoked transition (<code>plain_cookie_consent_clear_storage_keys</code> filter).</li>
</ul>
<h4>Accessibility</h4>
<ul>
<li>The banner and preferences modal are attested against WCAG 2.1 AA.</li>
<li>axe-core smoke tests (<code>wcag2a</code>, <code>wcag2aa</code>, <code>wcag21aa</code> tags) run on every push and pull request via GitHub Actions.</li>
<li>Site-level accessibility remains the operator’s responsibility.</li>
</ul>
<h4>Languages</h4>
<p>Translation catalogs ship for nine languages: English, German, Russian, Spanish, French, Italian, Dutch, Polish, and Portuguese. Banner language auto-resolution covers all nine shipped languages, including regional variants (for example de-AT or pt-BR), with any other locale falling back to English. Any shipped catalog can also be selected explicitly, and translators can override strings the standard WordPress gettext way.</p>
<h4>Not included</h4>
<ul>
<li>TCF v2.2 (programmatic publishers).</li>
<li>Consent analytics dashboards beyond the read-only Consent Health widget.</li>
<li>Multi-domain consent sync.</li>
<li>Banner A/B testing.</li>
<li>Script auto-blocking beyond Consent Mode and the documented vendor helpers.</li>
</ul>
<h3>External services</h3>
<p>This plugin has no telemetry and never sends data to its own or the author’s servers. Consent records stay in your own WordPress database.</p>
<p>The plugin can optionally load three well-known third-party marketing/analytics tags <strong>on your behalf</strong>. Each one is OFF by default and only ever loads when BOTH of the following are true:</p>
<ol>
<li>You explicitly enable it by defining the matching constant in <code>wp-config.php</code>, and</li>
<li>The visitor grants the relevant consent category in the banner.</li>
</ol>
<p>If you do not define these constants, the plugin makes no third-party requests at all. Once enabled, the tag still loads only after the visitor grants the relevant consent category in the banner.</p>
<h4>Meta (Facebook) Pixel</h4>
<p>Optional advertising measurement. Enabled by defining <code>PLAIN_COOKIE_CONSENT_FACEBOOK_PIXEL_ID</code>. When a visitor grants <strong>advertising</strong> consent, the plugin loads <code>https://connect.facebook.net/en_US/fbevents.js</code> and initialises the Pixel with your Pixel ID. From then on, on each page view, Meta receives standard Pixel data: your Pixel ID, the page URL and referrer, the visitor’s IP address and browser/user-agent, and a PageView event. Nothing is sent before advertising consent.<br />
Provider: Meta Platforms, Inc. Privacy Policy: https://www.facebook.com/privacy/policy/ — Business Tools Terms: https://www.facebook.com/legal/terms/businesstools</p>
<h4>Microsoft Clarity</h4>
<p>Optional session analytics (heatmaps and session insights). Enabled by defining <code>PLAIN_COOKIE_CONSENT_CLARITY_PROJECT_ID</code>. When a visitor grants <strong>analytics</strong> consent, the plugin loads <code>https://www.clarity.ms/tag/<your-project-id></code>. From then on, on each page view, Microsoft receives Clarity analytics data: your project ID, the page URL, the visitor’s IP address and browser/user-agent, and interaction events such as clicks and scrolls. Nothing is sent before analytics consent.<br />
Provider: Microsoft Corporation. Privacy Statement: https://www.microsoft.com/privacy/privacystatement — Clarity Terms of Service: https://clarity.microsoft.com/terms</p>
<h4>LinkedIn Insight Tag</h4>
<p>Optional advertising measurement on LinkedIn. Enabled by defining <code>PLAIN_COOKIE_CONSENT_LINKEDIN_PARTNER_ID</code>. When a visitor grants <strong>advertising</strong> consent, the plugin loads <code>https://snap.licdn.com/li.lms-analytics/insight.min.js</code> with your Partner ID. From then on, on each page view, LinkedIn receives Insight Tag data: your Partner ID, the page URL, and the visitor’s IP address and browser/user-agent. Nothing is sent before advertising consent.<br />
Provider: LinkedIn Corporation. Privacy Policy: https://www.linkedin.com/legal/privacy-policy — LinkedIn Ads Agreement: https://www.linkedin.com/legal/ads-agreement</p>
<h3>Disclaimer</h3>
<p>This plugin is provided “as is”, free of charge, for evaluation and use at<br />
the site operator’s own discretion and risk.</p>
<ul>
<li>The site operator alone chooses which plugins to install and run on their<br />
site, and bears full responsibility for that choice and its consequences.</li>
<li>The plugin is offered for informational and evaluation purposes. The<br />
authors make no guarantees and no promises of any kind — including<br />
correctness, completeness, fitness for a particular purpose, or<br />
uninterrupted operation.</li>
<li>Software may contain errors. Any errors, malfunctions, data loss, or<br />
legal consequences arising from the use of this plugin are the sole<br />
responsibility of the site operator.</li>
<li>Nothing in this plugin or its documentation constitutes legal advice.<br />
The plugin is designed to support a GDPR/ePrivacy-oriented consent setup,<br />
but it does not and cannot guarantee legal compliance of any specific<br />
site — final compliance always depends on the operator’s configuration,<br />
vendors, and policies.</li>
<li>The warranty disclaimer and limitation of liability are governed by<br />
sections 11 and 12 of the GNU GPL v2 license that ships with this plugin.</li>
</ul>


Plain Cookie Consent

Minimal clean-room GDPR/ePrivacy consent banner with Google Consent Mode v2, early inline replay, DSAR helper, and no upsells.

Bato Cookie Consent vs Plain Cookie Consent