Darwin Digital

<p><strong>Darwin Cookie Consent</strong> shows visitors a clear cookie banner, lets them choose what to accept, and sends those choices to your analytics and marketing tools through Google Consent Mode v2. No tracking runs until consent is given.</p>
<p>The plugin includes admin controls for legal links, appearance, integrations, localized frontend messaging, and privacy-safe reporting.</p>
<h4>Key Features</h4>
<ul>
<li>GDPR cookie consent banner and settings modal</li>
<li>Google Consent Mode v2 support</li>
<li>Editable localized content for English, French, German, and Spanish</li>
<li>Automatic content selection by WordPress site locale</li>
<li>WordPress editor support for the banner message and modal intro</li>
<li>Configurable legal page links for privacy, terms, and cookie policy</li>
<li>Integration controls for Google Tag Manager, GA4, Matomo, Facebook Pixel, LinkedIn Insight Tag, and Pardot</li>
<li>Separate Ad Personalization consent handling</li>
<li>Required Strictly Necessary Cookies row always enabled in the popup</li>
<li>Aggregate admin metrics for recent banner views and accepts</li>
<li>Resettable metrics counters with no personal data stored in the metrics table</li>
</ul>
<h4>Consent Categories</h4>
<ul>
<li><strong>Strictly Necessary Cookies</strong>: always required and always enabled</li>
<li><strong>Analytics</strong>: used for analytics tools such as Google Analytics and Matomo</li>
<li><strong>Marketing</strong>: used for marketing-related tracking integrations</li>
<li><strong>Ad Personalization</strong>: handled separately from general marketing consent</li>
</ul>
<h4>Privacy and Data Handling</h4>
<ul>
<li>Localized content is stored in WordPress options</li>
<li>Consent metrics store aggregate daily counts only — no personal identifiers are stored in the metrics table</li>
<li>The consent log table stores a SHA-256 hash of the visitor IP address and the browser user agent alongside the encoded consent payload; no plain-text IP addresses are stored</li>
<li>Consent Mode signals are updated based on saved user choices</li>
<li>No data is transmitted to the plugin author or any third-party service by this plugin itself</li>
</ul>
<h3>External Services</h3>
<p>This plugin can load scripts from third-party services when those integrations are configured in the plugin settings. No external requests are made unless the corresponding integration is enabled by the site administrator.</p>
<h4>Google Tag Manager</h4>
<p>When a GTM container ID is provided, this plugin loads the Google Tag Manager script from <code>googletagmanager.com</code>. Google Consent Mode defaults are applied before GTM loads so that no tracking occurs without user consent.</p>
<ul>
<li>Data sent: page URL and GTM container ID as part of the script request.</li>
<li>When: on every frontend page load, only if a GTM container ID is configured.</li>
<li>Service provider: Google LLC — <a href="https://marketingplatform.google.com/about/analytics/terms/us/" rel="nofollow ugc">Terms of Service</a> | <a href="https://policies.google.com/privacy" rel="nofollow ugc">Privacy Policy</a></li>
</ul>
<h4>Google Analytics (GA4)</h4>
<p>When a GA4 measurement ID is provided and GTM is not in use, this plugin loads the gtag.js script from <code>googletagmanager.com</code>. The script only fires after measurement consent is granted.</p>
<ul>
<li>Data sent: page URL and measurement ID as part of the script request.</li>
<li>When: on every frontend page load after measurement consent is granted, only if a GA4 ID is configured.</li>
<li>Service provider: Google LLC — <a href="https://marketingplatform.google.com/about/analytics/terms/us/" rel="nofollow ugc">Terms of Service</a> | <a href="https://policies.google.com/privacy" rel="nofollow ugc">Privacy Policy</a></li>
</ul>
<h4>Google Fonts</h4>
<p>When the default plugin font is selected, this plugin loads the Roboto typeface from Google Fonts. The stylesheet is fetched from <code>fonts.googleapis.com</code> and the font files are served from <code>fonts.gstatic.com</code>. A preconnect resource hint is also added for both domains.</p>
<ul>
<li>Data sent: browser and referrer information as part of the font request (standard browser HTTP headers).</li>
<li>When: on every frontend page load when the default font option is active.</li>
<li>Service provider: Google LLC — <a href="https://fonts.google.com/about" rel="nofollow ugc">Terms of Service</a> | <a href="https://policies.google.com/privacy" rel="nofollow ugc">Privacy Policy</a></li>
</ul>
<h4>Facebook Pixel</h4>
<p>When a Facebook Pixel ID is provided, this plugin loads the Facebook Pixel script from <code>connect.facebook.net</code>. The script only fires after marketing consent is granted.</p>
<ul>
<li>Data sent: page URL and pixel ID as part of the script request.</li>
<li>When: on every frontend page load after marketing consent is granted, only if a Pixel ID is configured.</li>
<li>Service provider: Meta Platforms, Inc. — <a href="https://www.facebook.com/legal/terms" rel="nofollow ugc">Terms of Service</a> | <a href="https://www.facebook.com/privacy/policy/" rel="nofollow ugc">Privacy Policy</a></li>
</ul>
<h4>LinkedIn Insight Tag</h4>
<p>When a LinkedIn Partner ID is provided, this plugin loads the LinkedIn Insight Tag from <code>snap.licdn.com</code>. The script only fires after marketing consent is granted.</p>
<ul>
<li>Data sent: page URL and partner ID as part of the script request.</li>
<li>When: on every frontend page load after marketing consent is granted, only if a Partner ID is configured.</li>
<li>Service provider: LinkedIn Corporation — <a href="https://www.linkedin.com/legal/user-agreement" rel="nofollow ugc">Terms of Service</a> | <a href="https://www.linkedin.com/legal/privacy-policy" rel="nofollow ugc">Privacy Policy</a></li>
</ul>
<h4>Salesforce Pardot</h4>
<p>When Pardot account and campaign IDs are provided, this plugin loads the Pardot tracking script from <code>pi.pardot.com</code>. The script only fires after marketing consent is granted.</p>
<ul>
<li>Data sent: page URL and account/campaign IDs as part of the script request.</li>
<li>When: on every frontend page load after marketing consent is granted, only if Pardot IDs are configured.</li>
<li>Service provider: Salesforce, Inc. — <a href="https://www.salesforce.com/company/legal/" rel="nofollow ugc">Terms of Service</a> | <a href="https://www.salesforce.com/company/legal/privacy/" rel="nofollow ugc">Privacy Policy</a></li>
</ul>
<h4>Matomo</h4>
<p>When a Matomo URL and site ID are provided, this plugin loads the Matomo tracking script from the configured Matomo instance. The script only fires after measurement consent is granted.</p>
<ul>
<li>Data sent: page URL and site ID to the configured Matomo instance.</li>
<li>When: on every frontend page load after measurement consent is granted, only if Matomo is configured.</li>
<li>Service provider: InnoCraft Ltd — <a href="https://matomo.org/website-terms/" rel="nofollow ugc">Terms of Service</a> | <a href="https://matomo.org/privacy-policy/" rel="nofollow ugc">Privacy Policy</a></li>
</ul>
<h3>Privacy Policy</h3>
<p>This plugin stores data locally in your WordPress database only. No data is transmitted to the plugin author or any third-party service by this plugin itself.</p>
<h4>Data stored locally</h4>
<ul>
<li><strong>Consent log table</strong> (<code>{prefix}darwin_gdpr_consent_log</code>): When a visitor saves their consent choices, the plugin records a SHA-256 hash of the visitor’s IP address, the browser user-agent string, and the encoded consent payload. No plain-text IP addresses are stored. Entries are automatically deleted after the configured retention period (default: 180 days).</li>
<li><strong>Aggregate metrics table</strong> (<code>{prefix}darwin_gdpr_metrics</code>): Stores daily totals of banner views and consent accepts as integer counts. No visitor identifiers of any kind are stored in this table.</li>
<li><strong>Plugin options</strong>: Localized content strings and appearance settings are stored in the WordPress options table. These contain no visitor data.</li>
</ul>
<h4>Third-party service data</h4>
<p>When optional integrations are configured by the site administrator, scripts from third-party services are loaded in the visitor’s browser. Those services may collect data as described in their respective privacy policies, which are linked in the External Services section above. No data is sent to those services until the visitor grants the relevant consent category.</p>
<p>Site administrators should ensure their own privacy policy reflects the data practices described above, particularly the storage of hashed IP addresses and user-agent strings in the consent log.</p>


Darwin Cookie Consent

Cookie banner for Google Consent Mode v2, GDPR & FADP. Includes four built-in languages, privacy-safe metrics, and appearance controls.

Royal Plugins

<p><span class="embed-youtube" style="text-align:center; display: block;"><iframe loading="lazy" class="youtube-player" width="750" height="422" src="https://www.youtube.com/embed/R7WQkpP4gsU?version=3&rel=1&showsearch=0&showinfo=1&iv_load_policy=1&fs=1&hl=en-US&autohide=2&wmode=transparent" allowfullscreen="true" style="border:0;" sandbox="allow-scripts allow-same-origin allow-popups allow-presentation allow-popups-to-escape-sandbox"></iframe></span></p>
<p>RoyalComply is a cookie consent and privacy compliance plugin for WordPress. It blocks analytics and marketing scripts until consent is given, supports Google Consent Mode v2, and adapts banner behavior based on the visitor’s jurisdiction (GDPR, CCPA, and 19 US state privacy laws).</p>
<p>The plugin runs entirely on your server. It does not connect to any external services.</p>
<h4>Works With Your Stack</h4>
<p>RoyalComply integrates with the analytics, advertising, and tag management tools you already use — no per-vendor configuration required:</p>
<ul>
<li><strong>Analytics scripts</strong> — Common analytics platforms are auto-categorized as “Analytics” cookies and blocked until the visitor accepts analytics consent.</li>
<li><strong>Advertising pixels</strong> — Common ad-tech pixels are auto-categorized as “Marketing” cookies and blocked until the visitor accepts marketing consent.</li>
<li><strong>Themes and page builders</strong> — Works with any block or classic theme, and any page builder that outputs standard HTML.</li>
<li><strong>eCommerce and memberships</strong> — Cart and session cookies are auto-categorized as “Necessary” and never blocked.</li>
<li><strong>Caching plugins</strong> — Banner state is read client-side from localStorage so cached pages render correctly for every visitor. No cache exclusion rules required.</li>
<li><strong>Multilingual</strong> — Banner text supports per-language translation; language-selection cookies are auto-categorized as “Preferences”.</li>
<li><strong>CDN geo headers</strong> — Geo detection runs server-side from existing CDN request headers (<code>CF-IPCountry</code> and similar) with a browser-timezone fallback. No IP geolocation API is contacted.</li>
</ul>
<p><strong>Features:</strong></p>
<ul>
<li><strong>Script blocking</strong> — Uses the WordPress <code>script_loader_tag</code> filter to change the <code>type</code> attribute of analytics and marketing scripts to <code>text/plain</code> until consent is given, preventing execution.</li>
<li><strong>Google Consent Mode v2</strong> — Outputs the <code>gtag('consent', 'default', {...})</code> call with a denied state before Google Tag Manager loads, and sends <code>consent update</code> events when the visitor makes a choice.</li>
<li><strong>Regional banner behavior</strong> — Detects the visitor’s region from CDN request headers (Cloudflare <code>CF-IPCountry</code> etc.) with a browser-timezone fallback. Banner behavior switches between opt-in (GDPR), opt-out (CCPA), and other jurisdictions as configured.</li>
<li><strong>Cookie scanner</strong> — Scans your site’s rendered HTML for known third-party script hostname patterns and matches them against a built-in database of 50+ cookie names. The scanner reads HTML your site already produces. No outbound HTTP requests are made.</li>
<li><strong>Consent logging</strong> — Stores each consent choice with a SHA-256 hashed visitor identifier, timestamp, and category selections. Exportable to CSV. No IP addresses or personally identifiable information are stored.</li>
<li><strong>Banner customization</strong> — 6 position options, bar or box layout, full color control. Combined CSS and JavaScript on the frontend is under 8KB.</li>
<li><strong>Geo detection</strong> — Reads the <code>CF-IPCountry</code> and similar headers already present in the incoming request. Falls back to the browser’s timezone via JavaScript. No IP lookup service is called.</li>
</ul>
<p><strong>Cookie Categories:</strong></p>
<ul>
<li><strong>Necessary</strong> — Always allowed. WordPress sessions, eCommerce cart cookies, PHP sessions.</li>
<li><strong>Analytics</strong> — Common analytics scripts and measurement cookies.</li>
<li><strong>Marketing</strong> — Common advertising and remarketing pixels.</li>
<li><strong>Preferences</strong> — Language selection, user-interface customization, and similar non-essential preference cookies.</li>
</ul>
<p><strong>Compliance Coverage:</strong></p>
<ul>
<li>GDPR (EU/EEA) — Opt-in consent required</li>
<li>CCPA (California) — Opt-out with “Do Not Sell” link</li>
<li>VCDPA (Virginia), CPA (Colorado), CTDPA (Connecticut), UCPA (Utah), TIPA (Tennessee), ICDPA (Indiana), MTCDPA (Montana), TDPSA (Texas), OCPA (Oregon), DPDPA (Delaware), FDBR (Florida), NJDPA (New Jersey), NHDPA (New Hampshire), KCDPA (Kentucky), NEBDPA (Nebraska), ICDPA (Iowa), MCDPA (Maryland), MNDPA (Minnesota)</li>
</ul>
<h3>External services</h3>
<p>RoyalComply does not connect to any third-party services. The plugin runs entirely on your own WordPress install and does not send data to any external server, API, or CDN.</p>
<p>The built-in <strong>cookie scanner</strong> makes a single loopback HTTP request to your own site’s homepage (<code>home_url( '/' )</code>) using the WordPress <code>wp_remote_get()</code> function, with a 10-second timeout. This request goes to the same WordPress install; no third-party service is contacted. The scanner then reads the returned <code>Set-Cookie</code> response headers and the HTML response body, and searches the body for known third-party script hostnames (for example <code>google-analytics.com</code>, <code>connect.facebook.net</code>, <code>js.stripe.com</code>, <code>widget.intercom.io</code>, <code>cdnjs.cloudflare.com</code>). These hostnames are stored as pattern strings inside the plugin and are compared against the response body using PHP’s <code>stripos()</code> function. The plugin does not make any network requests to the services the pattern strings refer to; it only reads HTML that your own site already generates.</p>
<p>The scanner runs only when the site administrator clicks the “Scan Site” button in the RoyalComply admin screen. It is not run on a schedule and is not triggered by visitors.</p>
<p><strong>Geo detection</strong> reads HTTP headers that are already present in the incoming page request (for example Cloudflare’s <code>CF-IPCountry</code> header) and, as a JavaScript fallback, reads the visitor’s timezone from the browser using <code>Intl.DateTimeFormat().resolvedOptions().timeZone</code>. No IP geolocation API is contacted.</p>
<p><strong>Google Consent Mode v2</strong> outputs a <code>gtag('consent', 'default', {...})</code> JavaScript call in the page. This call runs in the visitor’s browser and is consumed by Google Tag Manager or gtag.js if those are already installed on the site. RoyalComply itself does not load Google’s scripts; the integration only configures the consent state that the site’s existing Google scripts read.</p>


RoyalComply – Cookie Consent, GDPR & CCPA Compliance Banner

GDPR and CCPA cookie consent banner with Google Consent Mode v2. Blocks analytics and marketing scripts until the visitor gives consent.

Darwin Cookie Consent vs RoyalComply – Cookie Consent, GDPR & CCPA Compliance Banner