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.

privacyhubofficial

<p>PrivacyHub Cookie Consent connects your WordPress site to the PrivacyHub consent platform.</p>
<p>It helps site owners deploy and manage consent banners, block non-essential scripts until consent is granted, and send Google Consent Mode v2 signals.</p>
<p>Supported banner and framework modes include:</p>
<ul>
<li>Simple banner</li>
<li>Enhanced banner</li>
<li>IAB TCF for GDPR and ePrivacy use cases</li>
<li>US GPP banner for US state privacy use cases</li>
</ul>
<p>PrivacyHub can be configured for websites operating in or targeting regions such as:</p>
<ul>
<li>European Union and EEA</li>
<li>United Kingdom</li>
<li>Switzerland</li>
<li>United States</li>
<li>Canada</li>
<li>Brazil</li>
<li>South Africa</li>
<li>Australia</li>
<li>Singapore</li>
<li>Middle East deployments using PrivacyHub regional configurations</li>
</ul>
<p>Key features:</p>
<ul>
<li>Loads your configured PrivacyHub banner using your Website ID</li>
<li>Block-first handling for common analytics, marketing, and preferences scripts</li>
<li>Google Consent Mode v2 default and update signaling</li>
<li>Optional GA4 and GTM runtime loading after consent</li>
<li>Admin settings page for Website ID, script blocking, and Google Consent Mode configuration</li>
</ul>
<h4>External services</h4>
<p>This plugin connects to external services to load the consent runtime and, when configured by the site owner, send Google Consent Mode v2 signals and load Google tags after consent.</p>
<p>It may contact:</p>
<ul>
<li><code>https://api.privacyhub.ai/functions/v1/cookie-consent-script</code></li>
<li><code>https://api.privacyhub.ai/functions/v1/ph</code> (optional thin loader, when enabled by integrators)</li>
<li><code>https://www.googletagmanager.com/gtag/js</code> (when a GA4 Measurement ID is configured and analytics consent is granted)</li>
<li><code>https://www.googletagmanager.com/gtm.js</code> (when a GTM Container ID is configured and eligible consent is granted)</li>
</ul>
<p>What the services are used for:</p>
<ul>
<li>Retrieve and render the configured PrivacyHub consent banner for the current Website ID</li>
<li>Apply configured consent behavior for the active site and region setup</li>
<li>Process consent-related frontend runtime behavior configured in PrivacyHub</li>
<li>Initialize Google Consent Mode v2 defaults and updates</li>
<li>Load GA4 or GTM only after the relevant consent state allows it</li>
</ul>
<p>When they are called:</p>
<ul>
<li>On frontend page loads when the plugin is enabled and a Website ID is configured</li>
<li>After consent is granted, if GA4 and/or GTM IDs are configured by the site owner</li>
</ul>
<p>What is sent:</p>
<ul>
<li>The configured Website ID in the PrivacyHub script request query string</li>
<li>Standard browser request metadata automatically sent by the site visitor’s browser to the destination host</li>
<li>Google tag requests generated by the site owner’s configured GA4 or GTM implementation after consent</li>
</ul>
<p>Service providers:</p>
<ul>
<li>PrivacyHub</li>
<li>Google</li>
</ul>
<p>Service links:</p>
<ul>
<li>PrivacyHub website: https://www.privacyhub.ai/</li>
<li>Register: https://www.privacyhub.ai/register</li>
<li>Login: https://www.privacyhub.ai/login</li>
<li>Privacy policy: https://www.privacyhub.ai/privacy-policy</li>
<li>Help center: https://www.privacyhub.ai/help-center/enable-google-consent-mode</li>
<li>Google business privacy information: https://business.safety.google/privacy/</li>
</ul>
<h4>Asset licensing</h4>
<p>The bundled plugin assets in the <code>assets/</code> directory are original PrivacyHub branding assets distributed with this plugin release for use within the plugin admin interface.</p>


PrivacyHub Cookie Consent

Cookie consent banners, script blocking, and Google Consent Mode v2 for GDPR, UK/Swiss privacy, US state privacy, and more.

COOKR – Cookie Consent & Script Blocking vs PrivacyHub Cookie Consent