Webstudio.ltd

Webstudio GDPR is a complete GDPR and ePrivacy compliance solution for WordPress websites. Designed for Slovak, Czech and international markets.
Key features:
<ul>
<li>Granular consent — visitors can individually accept or decline categories: necessary, analytics, marketing and functional cookies</li>
<li>Script Manager — automatically blocks and conditionally loads scripts (Google Analytics 4, Facebook Pixel, Google Tag Manager, etc.) based on granted consent</li>
<li>Quick templates — add GA4, Facebook Pixel, GTM or Google Ads with a single click</li>
<li>Setup wizard — guided onboarding on first activation: site type, data processing, company details — done in under 2 minutes</li>
<li>Privacy policy page generator — creates or updates a page with a complete legal privacy policy template adapted to your site type (e-shop, SaaS, blog, firm)</li>
<li>Consent audit log — every consent is recorded in the database (session ID, IP, user-agent, policy version); exportable to CSV</li>
<li>4 banner positions — bottom-left, bottom-right, center with overlay, full-width bottom bar</li>
<li>Appearance customisation — button colors, border-radius, text colors — all configurable from the admin dashboard</li>
<li>Automatic re-consent — when company details change, the policy version is bumped and visitors are asked for consent again</li>
<li>Public JavaScript API — <code>wsgdprApi.openSettings()</code>, <code>wsgdprApi.getConsent()</code>, <code>wsgdprApi.hasConsent('analytics')</code></li>
<li>Re-open button — floating shield icon in the corner of the screen</li>
<li>Multilingual — Slovak (primary), Czech, English</li>
</ul>
The banner is lightweight (vanilla JS, no dependencies), WCAG-friendly and loads asynchronously.
<h3>External services</h3>
This plugin does not connect to any external service on its own. However, it provides a Script Manager that allows site administrators to load third-party scripts based on visitor consent. These scripts are added manually by the administrator and may include:
<h4>Google Analytics 4 / Google Tag Manager</h4>
If the administrator adds a GA4 or GTM script via the Script Manager, the browser will connect to Google’s servers (<code>www.googletagmanager.com</code>, <code>www.google-analytics.com</code>). This happens only after the visitor grants consent for the selected cookie category. Data sent is determined by the script configured by the administrator. 
* Terms of service: https://marketingplatform.google.com/about/analytics/terms/us/ 
* Privacy policy: https://policies.google.com/privacy
<h4>Facebook / Meta Pixel</h4>
If the administrator adds a Facebook Pixel script, the browser will connect to Meta’s servers (<code>connect.facebook.net</code>). This happens only after the visitor grants consent for the selected cookie category. 
* Terms of service: https://www.facebook.com/legal/terms 
* Privacy policy: https://www.facebook.com/privacy/policy/
<h4>Google Ads</h4>
If the administrator adds a Google Ads Conversion Tracking script, the browser will connect to Google’s servers. This happens only after the visitor grants consent for the selected cookie category. 
* Terms of service: https://policies.google.com/terms 
* Privacy policy: https://policies.google.com/privacy
The plugin itself does not send any data to external servers. All consent data is stored locally in the WordPress database.

Webstudio GDPR

Easy-to-configure cookie consent banner compliant with GDPR and ePrivacy. Granular consent, script blocking, privacy policy generator and audit log.

Billy Wilcosky

Oven integrates the <a href="https://github.com/orestbida/cookieconsent" rel="nofollow ugc">CookieConsent</a> JavaScript library (v3.1.0) into WordPress to provide a compliant, accessible cookie consent experience.
<h4>Features</h4>
<ul>
<li>Cookie consent banner – Shows a consent modal to visitors on first visit with Accept all, Essential only, and Manage preferences.</li>
<li>Automatic cookie detection – Enable “Cookie detection mode” in settings, then browse your site while logged in as an administrator. Cookies set during your visit are detected and added to the list.</li>
<li>Essential vs non-essential – WordPress core cookies (login, session, comments, settings) are classified as essential; third-party and analytics cookies as non-essential. Visitors see both categories in the preferences modal.</li>
<li>Revision and re-consent – When a new cookie is detected and added, the revision number is incremented. All visitors (including those who had previously accepted) must consent again.</li>
<li>Logged-in vs guest – For guests, consent is stored in a cookie so they are not prompted on every visit (until the revision changes). For logged-in users, consent is stored in the database (user meta) tied to their account.</li>
<li>Consent logging – For logged-in users, each consent choice is recorded in their profile. Admins and editors can view when a user accepted and which cookies they accepted (Users → edit user → Cookie consent).</li>
<li>Cookie descriptions – You can edit a short description for each cookie so visitors know what it does. Descriptions are shown in the preferences modal.</li>
<li>Privacy policy link – Optional privacy policy URL in settings is shown in the consent modal (recommended for GDPR).</li>
<li>Accessibility – Uses the CookieConsent library’s built-in ARIA attributes and keyboard support.</li>
</ul>
<h4>Settings</h4>
<ul>
<li>Settings → Oven – Enable cookie consent, enable cookie detection mode, set an optional privacy policy URL (recommended for GDPR), and view or edit the list of detected cookies and their descriptions.</li>
</ul>
<h4>GDPR and compliance</h4>
Oven is designed to support compliance with the GDPR and similar laws:
<ul>
<li>Consent before non-essential cookies – Non-essential cookies and scripts that set them are blocked until the user accepts. Essential cookies (e.g. login, session) are allowed without consent.</li>
<li>Clear information – Visitors see a list of cookies with names and descriptions (editable in settings). You can link to your privacy policy from the consent modal.</li>
<li>Granular choice – Users can accept all, essential only, or manage preferences and toggle individual non-essential cookies.</li>
<li>Withdraw consent – Users can reopen the preferences modal and change or withdraw consent at any time. Rejected non-essential cookies are cleared on each visit.</li>
<li>Re-consent when policy changes – When you add or reclassify cookies, the revision number increases and all visitors are asked to consent again.</li>
<li>Consent logging (logged-in users) – For registered users, consent choices and timestamps are stored in their profile. Admins and editors can view consent history under Users → [user] → Cookie consent. Guest consent is not logged (stored only in a cookie).</li>
<li>Transparency – Cookie detection mode helps you build an accurate cookie list; you can add cookies manually and describe what each one does.</li>
</ul>
<h4>Requirements</h4>
<ul>
<li>PHP 7.4 or higher</li>
<li>WordPress 5.9 or higher</li>
</ul>
<h3>Credits</h3>
<ul>
<li>CookieConsent (v3.1.0) by Orest Bida – https://github.com/orestbida/cookieconsent – MIT License.</li>
</ul>

Oven Cookie Consent

Cookie consent for WordPress: detect cookies, classify essential vs non-essential, and re-prompt visitors when your cookie list changes.

Webstudio GDPR vs Oven Cookie Consent