Shayan Ghiaseddin

<p><strong>Accept My Cookies</strong> is a lightweight and customizable WordPress plugin that helps you comply with GDPR and other privacy regulations. It displays a user-friendly consent modal, allowing visitors to accept or reject tracking cookies. The plugin supports <strong>Google Consent Mode</strong> for seamless integration with Google Analytics, Ads, and Tag Manager.</p>
<h4>Key Features</h4>
<ul>
<li><strong>GDPR Compliance</strong>: Helps you comply with GDPR and other privacy regulations.</li>
<li><strong>Customizable Consent Banner</strong>: Fully customizable text, colors, and positioning.</li>
<li><strong>Google Consent Mode</strong>: Supports Google Consent Mode for Google Analytics, Ads, and Tag Manager.</li>
<li><strong>Storage Options</strong>: Choose between cookies or local storage for consent preferences.</li>
<li><strong>Customizable Toggles</strong>: Allow users to customize their consent preferences for specific tracking parameters.</li>
<li><strong>Lightweight</strong>: Minimal impact on site performance.</li>
<li><strong>Cache and CDN Compatible</strong>: Having the option to store user choice in browser’s local storage, no need to worry about interference with caching systems or CDN.</li>
</ul>
<h4>Google Consent Mode</h4>
<p>The plugin supports <strong>Google Consent Mode</strong>, allowing you to manage user consent for Google services. When enabled, the plugin will:<br />
– Set default consent to <code>denied</code> for all tracking parameters.<br />
– Update consent status to <code>granted</code> based on user preferences.<br />
– Integrate seamlessly with Google Analytics, Ads, and Tag Manager.</p>
<h4>Customization</h4>
<p>You can customize the following aspects of the consent banner:<br />
– <strong>Position</strong>: Choose from bottom, top, left, right, or center.<br />
– <strong>Size</strong>: Set the banner size to tiny, normal, or wide.<br />
– <strong>Colors</strong>: Customize the banner’s background, text, and button colors.<br />
– <strong>Delay</strong>: Set a delay (in seconds) before the banner appears.</p>
<h3>External services</h3>
<p>This plugin provide options to you to connects to Google Tag Manager in order to enable Google Consent Mode, which is used to manage user consent for Google services such as Google Analytics, Google Ads, and Google Tag Manager.</p>
<h4>What data is sent and when?</h4>
<ul>
<li><strong>Data Sent</strong>: The plugin sends the user’s consent preferences (e.g., analytics_storage, ad_storage, ad_user_data, ad_personalization) to Google Tag Manager (https://www.googletagmanager.com/gtag/js?id=########).</li>
<li><strong>When</strong>: This data is sent when the user interacts with the consent banner (e.g., accepting or rejecting cookies).</li>
</ul>
<p>Links to Service Policies:<br />
<a href="https://marketingplatform.google.com/about/tag-manager/use-policy/" rel="nofollow ugc">Google Tag Manager Terms of Service</a><br />
<a href="https://policies.google.com/privacy" rel="nofollow ugc">Google Privacy Policy</a></p>
<h4>Why is this necessary?</h4>
<p>Google Consent Mode is required to ensure that no tracking occurs without user consent, helping you comply with GDPR and other privacy regulations. The plugin does not send any personally identifiable information (PII) to Google.</p>
<h3>Configuration</h3>
<p>After activating the plugin, follow these steps to configure it:</p>
<ol>
<li>Go to <strong>Settings > Accept My Cookies</strong> in your WordPress admin dashboard.</li>
<li>Configure the following settings:
<ul>
<li><strong>Consent Text</strong>: Customize the text displayed in the consent banner.</li>
<li><strong>Learn More URL</strong>: Set the URL for the “Learn More” link.</li>
<li><strong>Google Consent Mode</strong>: Enable Google Consent Mode and provide your Google Analytics ID.</li>
<li><strong>Storage Method</strong>: Choose between cookies or local storage.</li>
<li><strong>Banner Appearance</strong>: Customize the banner’s position, size, colors, and delay.</li>
</ul>
</li>
<li>Save your changes.</li>
</ol>
<h3>1.4.3</h3>
<ul>
<li>Close button added to consent banner</li>
<li>Bug fix</li>
</ul>
<h3>1.4.0</h3>
<ul>
<li>Extract information from .log file</li>
<li>And show as line chart in Logging tab</li>
</ul>
<h4>1.3.1</h4>
<ul>
<li>Bug fix with showing Clarity toggle</li>
<li>Bug fix with adding opacity to hex colors</li>
</ul>
<h4>1.3.0</h4>
<ul>
<li>Microsoft Clarity has added as an option to consent banner</li>
</ul>
<h4>1.2.1</h4>
<ul>
<li>Passed the test with WordPress 6.8</li>
</ul>
<h4>1.2.0</h4>
<ul>
<li>Reduced exposed options as js object to only those needed</li>
<li>Restructured the classes dependency </li>
</ul>
<h4>1.1.0</h4>
<ul>
<li>Logging bug fixed to log all parameters with consent options</li>
<li>Cookies must be check by JavaScript too, to make work on caching systems on</li>
<li>Minor change in Persian translation </li>
</ul>
<h4>1.0.3</h4>
<ul>
<li>Minor bug fix in initial language detection</li>
</ul>
<h4>1.0.0</h4>
<ul>
<li>Release to WordPress Plugin Repository</li>
</ul>
<h4>0.6.4</h4>
<ul>
<li>Bug fix in stylings</li>
<li>Bug fix in default custom html value</li>
<li>Adding and editing Persian translation</li>
</ul>
<h4>0.6.3</h4>
<ul>
<li>Minor bug fix in stylings</li>
</ul>
<h4>0.6.2</h4>
<p>Fixing wordpress plugin reviewer issues:<br />
– Tested Up To Value is Out of Date, Invalid, or Missing<br />
– Use wp_enqueue commands<br />
– Undocumented use of a 3rd Party / external service<br />
– Using load_plugin_textdomain() for loading the plugin translations is not needed for WordPress.org directory since WordPress 4.6.<br />
– Variables and options must be escaped when echo’d<br />
– Allowing Direct File Access to plugin files</p>
<h4>0.6.1</h4>
<ul>
<li>Getting the custom HTML</li>
<li>Rendering custom HTML in the </li>
</ul>
<h4>0.5.1</h4>
<ul>
<li>Credit tab added to settings</li>
</ul>
<h4>0.5.0</h4>
<ul>
<li>Logging functionality has added</li>
</ul>
<h4>0.4.5</h4>
<ul>
<li>Adding status to submit button in settings page</li>
<li>Fixing input validator</li>
</ul>
<h4>0.4.3</h4>
<ul>
<li>Adding title for consent banner</li>
<li>Fixing text-domain load</li>
<li>Adding Persian language glossary</li>
</ul>
<h4>0.3.9</h4>
<ul>
<li>Submiting the plugin to WordPress plugin’s repo</li>
</ul>
<h3>License</h3>
<p><strong>Accept My Cookies</strong> is licensed under the <a href="https://www.gnu.org/licenses/gpl-3.0.html" rel="nofollow ugc">GPLv3</a> or later.</p>
<h3>Credits</h3>
<ul>
<li>Developed by <a href="https://sghiaseddin.com" rel="nofollow ugc">Shayan Ghiaseddin</a>.</li>
<li>Inspired by the need for Google Consent Mode on Google Digital Marketing platforms.</li>
</ul>


Accept My Cookies

Accept My Cookies displays a user-friendly consent banner, allowing visitors to accept or reject tracking cookies and it supports Google Consent Mode.

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.

Accept My Cookies vs COOKR – Cookie Consent & Script Blocking