visionsolutions

CookieBoxs is a cookie consent plugin for WordPress that helps site owners manage visitor consent preferences and configure consent-aware integrations.
Free features include:
<ul>
<li>Google Consent Mode v2 support</li>
<li>Automatic script blocker and cookie cleaner</li>
<li>25+ built-in integrations</li>
<li>Content blockers for embedded media and maps</li>
<li>40 interface languages</li>
<li>Region presets</li>
<li>Consent logging in WordPress</li>
<li>Floating settings badge</li>
<li>Self-hosted plugin files</li>
</ul>
Optional PRO features include two-phase Cookie Scanner (server + browser-based detection), geo-targeting, additional templates, cookie declaration, consent analytics, tamper-proof consent records with CSV export and printable certificates, A/B testing of banner variants, granular per-service consent, a live banner design editor, branding options, and custom CSS.
Documentation: <a href="https://cookieboxs.com" rel="nofollow ugc">cookieboxs.com</a>
<h3>Source Code</h3>
All JavaScript and CSS files included in this plugin are human-readable and not minified or compiled. No build tools (npm, webpack, composer) are required to work with this plugin’s source code. All plugin-authored JavaScript and CSS is written directly and included as-is.
Third-party libraries and embed snippets:
<ul>
<li>
<code>assets/js/chart.min.js</code> — Chart.js library (MIT License). Source code and unminified version available at: https://github.com/chartjs/Chart.js
</li>
<li>
<code>assets/js/cookieboxs-consent-mode.js</code> — Contains standard third-party integration embed snippets (e.g., Google Tag Manager, Meta Pixel, TikTok Pixel, Microsoft Clarity, Hotjar, LiveChat, Intercom, etc.). These are the official JavaScript snippets provided by each service for website embedding, written in their standard compact form. Each snippet includes a source URL comment pointing to the official documentation. A full list of source URLs is also available in the file header comments. The surrounding plugin logic (consent state management, Google Consent Mode v2 setup, custom script injection) is authored by this plugin and is fully human-readable.
</li>
</ul>
Official documentation URLs for all embedded third-party snippets:
<ul>
<li>Google Tag Manager: https://developers.google.com/tag-platform/tag-manager/web</li>
<li>Meta Pixel: https://developers.facebook.com/docs/meta-pixel/get-started</li>
<li>TikTok Pixel: https://ads.tiktok.com/help/article/get-started-pixel</li>
<li>Microsoft Clarity: https://learn.microsoft.com/en-us/clarity/setup-and-installation/clarity-setup</li>
<li>Hotjar: https://help.hotjar.com/hc/en-us/articles/115011639927</li>
<li>Heap Analytics: https://developers.heap.io/docs/web</li>
<li>Mixpanel: https://docs.mixpanel.com/docs/tracking-methods/sdks/javascript</li>
<li>PostHog: https://posthog.com/docs/libraries/js</li>
<li>LinkedIn Insight Tag: https://learn.microsoft.com/en-us/linkedin/marketing/integrations/ads-reporting/insight-tag</li>
<li>Pinterest Tag: https://help.pinterest.com/en/business/article/install-the-pinterest-tag</li>
<li>Snapchat Pixel: https://businesshelp.snapchat.com/s/article/snap-pixel-about</li>
<li>Twitter/X Pixel: https://business.x.com/en/help/campaign-measurement-and-analytics/conversion-tracking-for-websites</li>
<li>Microsoft Advertising UET: https://help.ads.microsoft.com/apex/index/3/en/56682</li>
<li>LiveChat: https://developers.livechat.com/docs/getting-started/installing-livechat</li>
<li>Crisp: https://docs.crisp.chat/guides/chatbox-sdks/web-sdk/</li>
<li>Tawk.to: https://help.tawk.to/article/adding-a-tawk-to-widget-to-your-website</li>
<li>Intercom: https://developers.intercom.com/installing-intercom/web/installation</li>
<li>Yandex Metrica: https://yandex.com/support/metrica/code/counter-initialize.html</li>
<li>Matomo: https://developer.matomo.org/guides/tracking-javascript-guide</li>
</ul>
<h3>Privacy Policy</h3>
CookieBoxs does not send visitor consent records to the plugin author’s servers.
Consent records are stored in the WordPress database. Optional third-party integrations that you configure, such as analytics, advertising, chat, or embedded media services, connect directly from the visitor’s browser to those third-party providers after the relevant consent conditions are met.
Admin-only connections used for plugin news, optional deactivation feedback, or optional license validation are described below.
<h3>External Services</h3>
This plugin uses external services only for user-configured integrations. Third-party integrations are optional, disabled by default, and only activated when the site administrator enables and configures them. The plugin does not offload any of its own assets (JavaScript, CSS, images) to external servers — all plugin files are included locally.
<h4>Plugin services</h4>
<ul>
<li>
VisionSolutions API – plugin news and updates: used in the admin area only; sends plugin version, WordPress version, and site language when an administrator opens the settings page. Provider: VisionSolutions, https://visionsolutions.pl 
Terms of use: https://visionsolutions.pl/regulamin/ 
Privacy policy: https://visionsolutions.pl/polityka-prywatnosci/
</li>
<li>
VisionSolutions API – deactivation feedback (optional): sends selected reason, optional comment, site URL, WordPress version, and PHP version only if an administrator submits feedback during deactivation. Provider: VisionSolutions 
Terms of use: https://visionsolutions.pl/regulamin/ 
Privacy policy: https://visionsolutions.pl/polityka-prywatnosci/
</li>
<li>
VisionSolutions API – PRO license validation (optional): sends license key, site domain, and plugin version on activation and periodic validation. Provider: VisionSolutions 
Terms of use: https://visionsolutions.pl/regulamin/ 
Privacy policy: https://visionsolutions.pl/polityka-prywatnosci/
</li>
<li>
ipapi.co geolocation API (optional, PRO): used only when geo-targeting is enabled and fallback geolocation is needed; sends visitor IP address. Provider: ipapi 
Terms of use: https://ipapi.co/terms/ 
Privacy policy: https://ipapi.co/privacy/
</li>
<li>
Cookie Scanner (admin-initiated, PRO): two-phase scan. Phase 1 (server): sends requests from your server to your own website pages to detect cookies and tracking scripts from HTML. Phase 2 (browser): loads the scanned page in a hidden iframe within the administrator’s browser to detect cookies set by JavaScript (e.g. pixels loaded via Google Tag Manager). All scanning happens locally — no external provider is contacted.
</li>
</ul>
<h4>Optional integrations (services)</h4>
These are third-party services that the site administrator can optionally enable. When enabled, the plugin loads the official embed snippet provided by each service, which connects the visitor’s browser directly to that service provider. These are service integrations, not offloaded plugin assets. Each integration is disabled by default and only activates when the administrator provides their account ID.
<ul>
<li>
Google Tag Manager – tag management service; may load on page view and use Consent Mode signals. Loaded from: www.googletagmanager.com. Provider: Google LLC. 
Terms of use: https://marketingplatform.google.com/about/analytics/terms/us/ 
Privacy policy: https://policies.google.com/privacy
</li>
<li>
Google Analytics 4 – analytics service; loaded from www.googletagmanager.com/gtag/js via wp_enqueue_script. Provider: Google LLC. 
Terms of use: https://marketingplatform.google.com/about/analytics/terms/us/ 
Privacy policy: https://policies.google.com/privacy
</li>
<li>
Google Ads – conversion tracking and remarketing service; loaded from www.googletagmanager.com/gtag/js via wp_enqueue_script. Provider: Google LLC. 
Terms of use: https://ads.google.com/intl/en/home/terms/ 
Privacy policy: https://policies.google.com/privacy
</li>
<li>
Meta Pixel – advertising measurement service; loaded from connect.facebook.net. Provider: Meta Platforms, Inc. 
Terms of use: https://www.facebook.com/legal/terms 
Privacy policy: https://www.facebook.com/privacy/policy/
</li>
<li>
TikTok Pixel – advertising measurement service; loaded from analytics.tiktok.com. Provider: TikTok Inc. / ByteDance Ltd. 
Terms of use: https://ads.tiktok.com/i18n/official/policy/business-products-terms 
Privacy policy: https://www.tiktok.com/legal/privacy-policy
</li>
<li>
Microsoft Clarity – session analytics and heatmaps service; loaded from www.clarity.ms. Provider: Microsoft Corporation. 
Terms of use: https://clarity.microsoft.com/terms 
Privacy policy: https://privacy.microsoft.com/en-us/privacystatement
</li>
<li>
Hotjar – heatmaps, recordings, and feedback service; loaded from static.hotjar.com. Provider: Hotjar Ltd. 
Terms of use: https://www.hotjar.com/legal/policies/terms-of-service/ 
Privacy policy: https://www.hotjar.com/legal/policies/privacy/
</li>
<li>
Matomo – analytics service; loaded from the site administrator’s configured Matomo instance URL. Provider: InnoCraft Ltd. or the site owner’s Matomo host. 
Terms of use: https://matomo.org/matomo-cloud-terms-of-service/ 
Privacy policy: https://matomo.org/matomo-cloud-privacy-policy/
</li>
<li>
Yandex Metrica – analytics service; loaded from mc.yandex.ru. Provider: Yandex LLC. 
Terms of use: https://yandex.com/legal/metrica_termsofuse/ 
Privacy policy: https://yandex.com/legal/confidential/
</li>
<li>
Heap Analytics – analytics service; loaded from cdn.heapanalytics.com. Provider: Heap Inc. 
Terms of use: https://heap.io/legal/heap-terms-of-service 
Privacy policy: https://heap.io/legal/privacy
</li>
<li>
Mixpanel – analytics service; loaded from cdn.mxpnl.com. Provider: Mixpanel, Inc. 
Terms of use: https://mixpanel.com/legal/terms-of-use/ 
Privacy policy: https://mixpanel.com/legal/privacy-policy/
</li>
<li>
PostHog – analytics and feature flags service; loaded from the site administrator’s configured PostHog host. Provider: PostHog, Inc. 
Terms of use: https://posthog.com/terms 
Privacy policy: https://posthog.com/privacy
</li>
<li>
LinkedIn Insight Tag – advertising measurement service; loaded from snap.licdn.com. Provider: LinkedIn Corporation. 
Terms of use: https://www.linkedin.com/legal/l/li-marketing-terms 
Privacy policy: https://www.linkedin.com/legal/privacy-policy
</li>
<li>
Pinterest Tag – advertising measurement service; loaded from s.pinimg.com. Provider: Pinterest, Inc. 
Terms of use: https://policy.pinterest.com/en/terms-of-service 
Privacy policy: https://policy.pinterest.com/en/privacy-policy
</li>
<li>
Snapchat Pixel – advertising measurement service; loaded from sc-static.net. Provider: Snap Inc. 
Terms of use: https://snap.com/en-US/terms 
Privacy policy: https://snap.com/en-US/privacy/privacy-policy
</li>
<li>
Twitter/X Pixel – advertising measurement service; loaded from static.ads-twitter.com. Provider: X Corp. 
Terms of use: https://twitter.com/en/tos 
Privacy policy: https://twitter.com/en/privacy
</li>
<li>
Microsoft Advertising UET – conversion tracking service; loaded from bat.bing.com. Provider: Microsoft Corporation. 
Terms of use: https://about.ads.microsoft.com/en-us/policies/legal 
Privacy policy: https://privacy.microsoft.com/en-us/privacystatement
</li>
<li>
Intercom – customer messaging service; loaded from widget.intercom.io and api-iam.intercom.io. Provider: Intercom, Inc. 
Terms of use: https://www.intercom.com/legal/terms-and-policies 
Privacy policy: https://www.intercom.com/legal/privacy
</li>
<li>
LiveChat – support chat service; loaded from cdn.livechatinc.com. Provider: LiveChat, Inc. 
Terms of use: https://www.livechat.com/legal/terms-of-service/ 
Privacy policy: https://www.livechat.com/legal/privacy-policy/
</li>
<li>
Crisp – customer messaging and chat service; loaded from client.crisp.chat. Provider: Crisp IM SAS. 
Terms of use: https://crisp.chat/en/terms/ 
Privacy policy: https://crisp.chat/en/privacy/
</li>
<li>
Tawk.to – support chat service; loaded from embed.tawk.to. Provider: Tawk.to Ltd. 
Terms of use: https://www.tawk.to/legal/terms-of-service/ 
Privacy policy: https://www.tawk.to/legal/privacy-policy/
</li>
</ul>
<h4>Script blocker safe domains</h4>
The automatic script blocker does not block scripts from essential service domains (payment gateways, CAPTCHAs, translation). These domains are whitelisted so the script blocker does not interfere with site-critical functionality provided by other plugins or themes. The CookieBoxs plugin itself does not load any files from these domains — they are only whitelisted to prevent breakage:
<ul>
<li>
Stripe – payment processing service; loaded by other plugins from js.stripe.com and checkout.stripe.com. Provider: Stripe, Inc. 
Terms of use: https://stripe.com/legal/ssa 
Privacy policy: https://stripe.com/privacy
</li>
<li>
PayPal – payment processing service; loaded by other plugins from www.paypal.com and www.paypalobjects.com. Provider: PayPal Holdings, Inc. 
Terms of use: https://www.paypal.com/us/legalhub/useragreement-full 
Privacy policy: https://www.paypal.com/us/legalhub/privacy-full
</li>
<li>
Google reCAPTCHA – spam protection service; loaded by other plugins from recaptcha.net. Provider: Google LLC. 
Terms of use: https://policies.google.com/terms 
Privacy policy: https://policies.google.com/privacy
</li>
<li>
hCaptcha – spam protection service; loaded by other plugins from js.hcaptcha.com. Provider: Intuition Machines, Inc. 
Terms of use: https://www.hcaptcha.com/terms 
Privacy policy: https://www.hcaptcha.com/privacy
</li>
<li>
Cloudflare Turnstile – bot protection service; loaded by other plugins from challenges.cloudflare.com. Provider: Cloudflare, Inc. 
Terms of use: https://www.cloudflare.com/terms/ 
Privacy policy: https://www.cloudflare.com/privacypolicy/
</li>
<li>
Google Translate – translation service widget; loaded by other plugins from translate.google.com and translate.googleapis.com. Provider: Google LLC. 
Terms of use: https://policies.google.com/terms 
Privacy policy: https://policies.google.com/privacy
</li>
</ul>
<h4>Content blockers</h4>
Content blockers are an optional feature that replaces embedded third-party media (YouTube, Vimeo, Google Maps) with a placeholder until the visitor grants consent. When consent is given, the embed loads normally from the service provider.
<ul>
<li>
YouTube – video embeds can be blocked until consent; loaded from www.youtube.com and www.youtube-nocookie.com. Provider: Google LLC. 
Terms of use: https://www.youtube.com/t/terms 
Privacy policy: https://policies.google.com/privacy
</li>
<li>
Vimeo – video embeds can be blocked until consent; loaded from player.vimeo.com and vimeo.com. Provider: Vimeo, Inc. 
Terms of use: https://vimeo.com/terms 
Privacy policy: https://vimeo.com/privacy
</li>
<li>
Google Maps – map embeds can be blocked until consent; loaded from www.google.com/maps and maps.googleapis.com. Provider: Google LLC. 
Terms of use: https://cloud.google.com/maps-platform/terms 
Privacy policy: https://policies.google.com/privacy
</li>
</ul>

CookieBoxs – GDPR/CCPA Cookie Consent & Google Consent Mode v2

Cookie consent plugin for managing visitor consent with Google Consent Mode v2, script blocking, content blockers, and optional integrations.

danjed

GDPR cookie consent with real script blocking.
Block Google Analytics, Google Tag Manager, Meta Pixel, Hotjar, YouTube embeds, and other third-party services before they reach the browser.
Unlike JavaScript-based consent tools, blocked scripts never reach the browser at all.
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.
COOKR takes a different approach.
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.
Avoids the client-side race conditions common to JavaScript-only consent tools. No script guessing. No “hope it loads in time.”
Consent enforcement instead of consent theatre.
✓ Server-side script blocking — blocked before the browser receives them 
✓ Google Consent Mode v2 support 
✓ No external consent cloud 
✓ No proxy infrastructure 
✓ No visitor data sent to third parties 
✓ Works entirely on your WordPress installation
Built for site owners, agencies, and developers who want real GDPR cookie consent enforcement.
COOKR CORE includes:
<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>
COOKR RADR additionally includes:
<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>
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.
There is no client-side race condition because blocking happens before the browser receives the page.
<h4>Auto-Blocker</h4>
Enable in Settings. Off by default.
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.
Test after enabling when using WP Rocket, LiteSpeed Cache, NitroPack, or Cloudflare Rocket Loader.
<h4>Runtime Inspector</h4>
The Runtime Inspector exposes third-party runtime activity directly in the browser — blocked scripts, restored services, iframe activity, detected domains.
Enable in Settings. Append <code>?cookr_debug=1</code> to any frontend URL while logged in as administrator.
<h4>CSP-aware</h4>
COOKR supports strict Content Security Policies without requiring <code>unsafe-inline</code>.
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.
<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>Necessary — Always active.</li>
<li>Analytics — GA, GTM, Matomo, Hotjar, Clarity, etc.</li>
<li>Marketing — Meta Pixel, Google Ads, TikTok, LinkedIn, etc.</li>
<li>External Media — YouTube, Vimeo, Google Maps, etc.</li>
</ul>
<h4>Does COOKR require an external cloud service?</h4>
No. COOKR runs entirely on your WordPress installation.
<h4>Does visitor consent data leave the server?</h4>
No. Consent data is stored locally on your site.
<h4>Is the Auto-Blocker enabled by default?</h4>
No. Enable and test it after installation, particularly when using caching or JavaScript optimization plugins.
<h4>Which services can be blocked?</h4>
Any third-party script or iframe matching configured domains. Examples: Google Tag Manager, Meta Pixel, YouTube embeds, TikTok Analytics.
<h4>Does COOKR support Google Consent Mode v2?</h4>
Yes. Enable in settings when using GTM or GA4.
<h4>How do I inspect runtime activity?</h4>
Enable the Runtime Inspector in settings and append <code>?cookr_debug=1</code> to any frontend URL while logged in as administrator.
<h4>Does COOKR store personal data?</h4>
The consent log stores a hashed IP (not the raw IP address), consent choices, and a timestamp. The raw IP address is never stored.
<h4>Is COOKR compatible with strict CSP?</h4>
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.
<h4>Will COOKR work with caching plugins such as LiteSpeed Cache, WP Rocket, or Cloudflare?</h4>
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.
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.
<h4>Does COOKR require HTTPS?</h4>
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.
<h4>What WordPress version is required?</h4>
WordPress 6.2 or higher. COOKR uses <code>WP_HTML_Tag_Processor</code> for safe, attribute-aware script rewriting, introduced in WP 6.2.
<h3>External Services</h3>
This plugin does not connect to any external service by default.
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.

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.

CookieBoxs – GDPR/CCPA Cookie Consent & Google Consent Mode v2 vs COOKR – Cookie Consent & Script Blocking