Webstudio.ltd

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


Webstudio GDPR

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

danjed

<p>GDPR cookie consent with real script blocking.</p>
<p>Block Google Analytics, Google Tag Manager, Meta Pixel, Hotjar, YouTube embeds, and other third-party services before they reach the browser.</p>
<p>Unlike JavaScript-based consent tools, blocked scripts never reach the browser at all.</p>
<p>Most cookie consent plugins display a banner and rely on JavaScript to stop tracking scripts. In many cases, those scripts can begin loading before the visitor has made a choice.</p>
<p>COOKR takes a different approach.</p>
<p>Scripts are blocked server-side before page delivery. Third-party services cannot execute until consent is explicitly granted. This helps website owners meet GDPR and TTDSG requirements more reliably.</p>
<p>Avoids the client-side race conditions common to JavaScript-only consent tools. No script guessing. No “hope it loads in time.”</p>
<p>Consent enforcement instead of consent theatre.</p>
<p>✓ Server-side script blocking — blocked before the browser receives them<br />
✓ Google Consent Mode v2 support<br />
✓ No external consent cloud<br />
✓ No proxy infrastructure<br />
✓ No visitor data sent to third parties<br />
✓ Works entirely on your WordPress installation</p>
<p>Built for site owners, agencies, and developers who want real GDPR cookie consent enforcement.</p>
<p>COOKR CORE includes:</p>
<ul>
<li>Consent banner & preferences UI</li>
<li>Server-side script interception via PHP output buffer</li>
<li>Auto-Blocker for third-party scripts and iframes</li>
<li>Runtime Inspector</li>
<li>CSP-aware restoration with nonce propagation</li>
<li>Google Consent Mode v2 support</li>
<li>Full JavaScript API (<code>window.cookrConsent</code>)</li>
<li>Self-hosted operation — no external services required</li>
</ul>
<p>COOKR RADR additionally includes:</p>
<ul>
<li>Privacy Radar — runtime detection and classification of third-party services</li>
<li>Enforcement Verification Framework — structured protocol for proving enforcement claims</li>
<li>Compatibility Matrix — tested stack database with VERIFIED/PARTIAL/UNKNOWN/FAILED states</li>
<li>Automatic optimizer exclusions — LiteSpeed, WP Rocket, Autoptimize, FlyingPress</li>
<li>Curated signature database with automatic weekly updates</li>
</ul>
<h4>How It Works</h4>
<p>COOKR intercepts scripts in the PHP output buffer using <code>WP_HTML_Tag_Processor</code> before delivery to the browser. Matching script and iframe tags are neutralised server-side and restored only after the visitor grants consent.</p>
<p>There is no client-side race condition because blocking happens before the browser receives the page.</p>
<h4>Auto-Blocker</h4>
<p>Enable in Settings. Off by default.</p>
<p>When enabled, COOKR rewrites matching script tags and iframe tags server-side — setting <code>type="text/plain"</code> and preserving original attributes in <code>data-cookr-*</code> attributes for restoration after consent.</p>
<p>Test after enabling when using WP Rocket, LiteSpeed Cache, NitroPack, or Cloudflare Rocket Loader.</p>
<h4>Runtime Inspector</h4>
<p>The Runtime Inspector exposes third-party runtime activity directly in the browser — blocked scripts, restored services, iframe activity, detected domains.</p>
<p>Enable in Settings. Append <code>?cookr_debug=1</code> to any frontend URL while logged in as administrator.</p>
<h4>CSP-aware</h4>
<p>COOKR supports strict Content Security Policies without requiring <code>unsafe-inline</code>.</p>
<p>Restored scripts preserve CSP integrity via automatic nonce propagation. COOKR reads the nonce WordPress assigns to enqueued scripts at request time and passes it to restored scripts — no manual configuration required.</p>
<h4>Developer JS API</h4>
<pre><code>cookrConsent.has('analytics')
cookrConsent.require('marketing', callback)
cookrConsent.whenConsented('analytics').then(fn)
cookrConsent.on('consent' | 'change' | 'decline' | 'reset', handler)
cookrConsent.off(event, handler)
cookrConsent.getConsent()
cookrConsent.getExpiry()
cookrConsent.categories()
cookrConsent.reset()
</code></pre>
<h4>Consent Categories</h4>
<ul>
<li><strong>Necessary</strong> — Always active.</li>
<li><strong>Analytics</strong> — GA, GTM, Matomo, Hotjar, Clarity, etc.</li>
<li><strong>Marketing</strong> — Meta Pixel, Google Ads, TikTok, LinkedIn, etc.</li>
<li><strong>External Media</strong> — YouTube, Vimeo, Google Maps, etc.</li>
</ul>
<h4>Does COOKR require an external cloud service?</h4>
<p>No. COOKR runs entirely on your WordPress installation.</p>
<h4>Does visitor consent data leave the server?</h4>
<p>No. Consent data is stored locally on your site.</p>
<h4>Is the Auto-Blocker enabled by default?</h4>
<p>No. Enable and test it after installation, particularly when using caching or JavaScript optimization plugins.</p>
<h4>Which services can be blocked?</h4>
<p>Any third-party script or iframe matching configured domains. Examples: Google Tag Manager, Meta Pixel, YouTube embeds, TikTok Analytics.</p>
<h4>Does COOKR support Google Consent Mode v2?</h4>
<p>Yes. Enable in settings when using GTM or GA4.</p>
<h4>How do I inspect runtime activity?</h4>
<p>Enable the Runtime Inspector in settings and append <code>?cookr_debug=1</code> to any frontend URL while logged in as administrator.</p>
<h4>Does COOKR store personal data?</h4>
<p>The consent log stores a hashed IP (not the raw IP address), consent choices, and a timestamp. The raw IP address is never stored.</p>
<h4>Is COOKR compatible with strict CSP?</h4>
<p>Yes. COOKR automatically reads the nonce WordPress assigns to enqueued scripts and passes it to restored scripts, preserving compatibility with <code>strict-dynamic</code> CSP policies. No manual configuration is required.</p>
<h4>Will COOKR work with caching plugins such as LiteSpeed Cache, WP Rocket, or Cloudflare?</h4>
<p>Yes, but always test after enabling script optimization features such as JavaScript combine, defer, delay, or Rocket Loader. COOKR performs script blocking server-side, but aggressive optimization plugins may alter script delivery and should be verified on your site.</p>
<p>RADR v1.9.8 adds automatic exclusion filters for LiteSpeed Cache, WP Rocket, Autoptimize, and FlyingPress — COOKR registers itself as excluded from JS combination pipelines automatically.</p>
<h4>Does COOKR require HTTPS?</h4>
<p>Yes. COOKR requires HTTPS for consent state to persist correctly across page loads. Modern browsers restrict cookie behaviour on HTTP origins — on HTTP, the consent cookie may not persist, causing the banner to reappear on every page load. HTTPS is also a legal recommendation under GDPR for any site collecting consent.</p>
<h4>What WordPress version is required?</h4>
<p>WordPress 6.2 or higher. COOKR uses <code>WP_HTML_Tag_Processor</code> for safe, attribute-aware script rewriting, introduced in WP 6.2.</p>
<h3>External Services</h3>
<p>This plugin does not connect to any external service by default.</p>
<p>The auto-blocker contains a built-in list of known third-party domains (such as googletagmanager.com, connect.facebook.net, maps.googleapis.com, etc.) that is used purely as a local reference to identify and block scripts before consent. No data is sent to these domains by this plugin — the list is pattern-matching data stored locally in the plugin code.</p>


COOKR – Cookie Consent & Script Blocking

GDPR cookie consent with server-side script blocking. Prevent Google Analytics, GTM, Meta Pixel and third-party embeds from loading before consent.

Webstudio GDPR vs COOKR – Cookie Consent & Script Blocking