Bato Cookie Consent

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.

The plugin is built for site owners and developers who need a local, customizable consent banner without loading third-party assets by default.

Features

• Consent banner with accept all, reject all, and custom preferences actions.
• 34 built-in frontend languages with browser/site language detection and RTL support for Hebrew and Arabic.
• Necessary, analytics, marketing, and preferences categories.
• Editable banner, modal, button, category, and embed placeholder text.
• Privacy policy and cookie policy links.
• Floating preferences button after a visitor has saved choices.
• YouTube and Vimeo embed placeholders that can wait for marketing consent.
• Developer filter for adding scripts, embeds, and advanced configuration.
• Optional Google Consent Mode updates when gtag is already present on the site.
• Translation-ready PHP and JavaScript strings.

Supported Languages

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.

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.

Privacy

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.

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.

Developer Usage

Developers can extend the frontend configuration with the bato_cookie_consent_config filter:

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;
});

Source files and build tooling are included with the plugin. To rebuild production assets, run:

npm install
npm run build

Third-Party Notices

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.

Runtime assets

• @bato-web-agency/cookie-consent – MIT License
• @mdi/font – Apache License 2.0
• vue – MIT License
• vuetify – MIT License

Build tooling

• @vitejs/plugin-vue – MIT License
• vite – MIT License

Dependency metadata is recorded in package-lock.json.