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.

Felix A. Schultz

<p><a href="https://www.intastellarsolutions.com/solutions/cookie-consents" rel="nofollow ugc">Intastellar Consents</a> allows you to display a compliant cookie consent banner on your WordPress website and block non-essential scripts until consent is given.</p>
<p>Intastellar Consents supports out of the box the following compliance laws:<br />
– GDPR<br />
– ePrivacy Directive<br />
– CCPA / CPRA<br />
– LGPD in Brazil<br />
– POPIA in South Africa</p>
<p>The plugin integrates seamlessly by loading the Intastellar Consents script and handling consent logic centrally, ensuring consistent behavior across pages.</p>
<h3>Google Consent Mode</h3>
<p>Intastellar Consents supports Google Consent Mode, allowing Google Analytics and Google Ads<br />
to adapt their behavior based on user consent while preventing tracking cookies before consent.</p>
<p>Consent signals are updated dynamically when users change their preferences.</p>
<h3>Key Features</h3>
<ul>
<li>GDPR & ePrivacy compliant consent banner</li>
<li>Google Consent Mode support (advanced setups included)</li>
<li>CCPA / CPRA support with “Do Not Sell My Personal Information” option</li>
<li>Blocks marketing and analytics scripts until consent is granted</li>
<li>Lightweight, minimal performance impact</li>
<li>Customizable look and feel to match your brand</li>
<li>Multi-language support based on site language</li>
<li>Easy plugin install or single-script integration</li>
<li>Hosted securely in the EU</li>
<li>Compatible with Google Analytics, Meta Pixel, Microsoft UET/Clarity, HubSpot, and others</li>
<li>Support for LGPD in Brazil and POPIA in South Africa</li>
</ul>
<h3>Supported WordPress Languages</h3>
<p>The full plugin admin (Settings, Branding, Intro, Privacy, Help, and the “Ask for review” prompt) is translated into the following languages. Set your site or admin language in <strong>Settings <span aria-hidden="true" class="wp-exclude-emoji">→</span> General</strong> (or your user profile language for the admin) to use them.</p>
<ul>
<li>English (default)</li>
<li>Danish (Dansk)</li>
<li>German (Deutsch)</li>
<li>French (Français)</li>
<li>Spanish (Español)</li>
<li>Italian (Italiano)</li>
<li>Dutch (Nederlands)</li>
<li>Polish (Polski)</li>
<li>Portuguese – Portugal (Português)</li>
<li>Japanese (日本語)</li>
</ul>
<h3>Translations</h3>
<ul>
<li><strong>Plugin admin:</strong> The list above is built into the plugin; no extra setup is needed. Just set your WordPress or user language and the admin will appear in that language.</li>
<li><strong>This page (WordPress.org):</strong> To have the plugin description and this readme shown in more languages on the WordPress.org plugin page, translators can contribute at <strong>translate.wordpress.org</strong> <span aria-hidden="true" class="wp-exclude-emoji">→</span> project <strong>wp-plugins/intastellar-gdpr-cookie-banner</strong>. Approved translations there are used for the plugin’s landing page and for automatic language-pack updates.</li>
</ul>
<h3>Who Is This Plugin For?</h3>
<ul>
<li>Small business websites</li>
<li>Freelancers and agencies building WordPress sites</li>
<li>Developers who want a clean consent solution</li>
<li>Website owners who don’t want enterprise-level CMP complexity</li>
<li>Anyone tired of bloated cookie plugins</li>
<li>Agencies managing multiple client sites that need a consistent consent solution</li>
<li>WordPress developers looking for a lightweight and easy-to-use consent solution</li>
</ul>
<h3>How It Works</h3>
<p>Intastellar Consents loads a secure script that:<br />
1. Detects visitors’ region and initializes consent defaults (GDPR, CCPA, etc.)<br />
2. Prevents non-essential scripts from firing until consent is given<br />
3. Applies Google Consent Mode signals based on user consent<br />
4. Ensures personalized banner presentation via multi-language detection<br />
5. Fires permitted scripts only after valid consent<br />
This approach helps you balance privacy compliance with data insights, especially for analytics and ads platforms.</p>
<h3>GDPR & Privacy Compliance</h3>
<p>Intastellar Consents is built with GDPR principles in mind:</p>
<ul>
<li>Consent before non-essential cookies</li>
<li>Clear and explicit user choice</li>
<li>No pre-checked consent</li>
<li>No user profiling by the plugin itself</li>
<li>Consent handling aligned with GDPR and ePrivacy Directive</li>
</ul>
<p>Intastellar Consents does not claim to provide full legal compliance on its own.</p>
<h3>Privacy & Data Handling</h3>
<p>The plugin itself does not store personal data on the WordPress site.<br />
Consent logic is handled via Intastellar Consents’ infrastructure.</p>
<p><strong>Note:</strong> Website owners remain responsible for ensuring their overall site configuration, cookie usage, and privacy policy are GDPR-compliant.</p>
<h3>External Resources</h3>
<p>The plugin loads the following external resources which are required for the consent banner to function:<br />
JavaScript from:<br />
https://consents.cdn.intastellarsolutions.com<br />
CSS styling from:<br />
https://downloads.intastellarsolutions.com<br />
The banner and consent management logic run from these hosted resources.<br />
Without these external files, the plugin will not display or function properly.<br />
No personal data or WordPress user information is sent to these domains simply by loading the script.</p>
<p>No tracking, analytics, or marketing cookies are set by these resources before user consent is given.</p>
<p>Why are external resources required?<br />
The consent system is centrally maintained so updates to compliance rules, UI, and consent logic can be rolled out without requiring site owners to manually update the plugin.</p>
<p>You can find the service on our website: <a href="https://www.intastellarsolutions.com/solutions/cookie-consents" rel="nofollow ugc">https://www.intastellarsolutions.com/solutions/cookie-consents</a><br />
Find the privacy policy here: <a href="https://www.intastellarsolutions.com/about/legal/privacy" rel="nofollow ugc">https://www.intastellarsolutions.com/about/legal/privacy</a><br />
Find the terms of service here: <a href="https://www.intastellarsolutions.com/about/legal/terms" rel="nofollow ugc">https://www.intastellarsolutions.com/about/legal/terms</a></p>


Intastellar Consents – GDPR Cookie Banner & Google Consent Mode

Short Description

Free GDPR, CCPA, LGPD, POPIA cookie banner for WordPress. Automatically block tracking scripts and support Google Consent Mode.

COOKR – Cookie Consent & Script Blocking vs Intastellar Consents – GDPR Cookie Banner & Google Consent Mode