Royal Plugins

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).
The plugin runs entirely on your server. It does not connect to any external services.
Features:
<ul>
<li>Script blocking — 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>Google Consent Mode v2 — 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>Regional banner behavior — 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>Cookie scanner — Scans your site’s rendered HTML for known third-party script patterns (Google Analytics, Facebook Pixel, Hotjar, etc.) 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>Consent logging — 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>Banner customization — 6 position options, bar or box layout, full color control. Combined CSS and JavaScript on the frontend is under 8KB.</li>
<li>Geo detection — 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>
Cookie Categories:
<ul>
<li>Necessary — Always allowed. WordPress sessions, WooCommerce cart, PHP sessions.</li>
<li>Analytics — Google Analytics, Hotjar, Clarity, Matomo, Plausible.</li>
<li>Marketing — Facebook Pixel, Google Ads, LinkedIn, TikTok, Pinterest.</li>
<li>Preferences — Language selection (Polylang, WPML, qTranslate).</li>
</ul>
Compliance Coverage:
<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>
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.
The built-in cookie scanner 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.
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.
Geo detection 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.
Google Consent Mode v2 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.

RoyalComply

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

TrustArc

The TrustArc Cookie Consent Manager plugin assists WordPress site owners in configuring and integrating TrustArc’s Consent Management Platform (CMP). This plugin offers a user-friendly interface for adding the cookie consent manager script to the site without requiring any theme modifications.
Watch the plugin overview: 
See how the TrustArc Cookie Consent Manager works 
<a href="https://youtu.be/skRPKMfo-lQ" rel="nofollow ugc">Watch on YouTube →</a>
Why TrustArc Cookie Consent Manager?
<ul>
<li>
Easy installation and highly configurable for privacy-first optimal experiences
</li>
<li>
Real-time reporting on consent metrics and executive dashboards
</li>
<li>
Automated website discovery, categorization and management of tracking technologies and potential risks
</li>
<li>
Technical Account Management: Dedicated Technical Account Manager to support the implementation and optimization of your consent experiences and tracker management. Includes managed support, recurring tracker audits, and guidance for customized deployments across regions
</li>
<li>
Benefits: Ensure the best customer experience to improve consents and build trust while honoring and recognizing privacy and advertising requirements
</li>
</ul>
Key features:
<ul>
<li>
Automated website scanning – Unlimited scans up to 10,000 pages and including behind login scanning
</li>
<li>
Auto-blocking to drop cookies until consent is given
</li>
<li>
Dynamic tracker display
</li>
<li>
UI configuration interface
</li>
<li>
Custom CSS Support
</li>
<li>
Geo-IP detection
</li>
<li>
Google Consent Mode support and Google-certified CMP Partner (Gold Status)
</li>
<li>
GPC and DNT signal support
</li>
<li>
IAB and GPP support
</li>
<li>
AdChoices support
</li>
<li>
Tag Manager support
</li>
</ul>
Plugin functionality:
<ul>
<li>
Configure and inject the TrustArc CMP script
</li>
<li>
Load the banner container
</li>
<li>
Add a Cookie Preferences link anywhere on the site
</li>
<li>
Enable Google Consent Mode Integration
</li>
<li>
Enable WP Consent API Integration
</li>
<li>
Enable TrustArc Events
</li>
</ul>
<h3>Disclaimer</h3>
⚠️ Important: Installing this plugin does not automatically guarantee compliance with GDPR, CCPA, LGPD or other data privacy laws and regulations. TrustArc provides the tools to facilitate compliance, however website owners are solely responsible for configuring the plugin properly and ensuring that their cookie notice and consent management practices meet legal requirements.
<h3>External services</h3>
This plugin integrates with the TrustArc Consent Management Platform (CMP) to manage cookie consent on your website.
Requirements:
<ul>
<li>A valid TrustArc license is required to use this plugin. To purchase or get a demo of TrustArc Cookie Consent Manager, please contact TrustArc at [https://trustarc.com/demo-request/consent-consumer-rights/)</li>
</ul>
What data is sent?
The plugin sends the following data to TrustArc:
<ul>
<li>User’s location: To determine the applicable privacy regulations.</li>
<li>Browser information: To optimize the consent experience.</li>
<li>Consent choices: To record and manage user preferences.</li>
<li>Interactions with the CMP: To track opt-in/out rates and improve the CMP’s effectiveness.</li>
</ul>
When is data sent?
Data is sent to TrustArc when:
<ul>
<li>The CMP is loaded on a page.</li>
<li>A user interacts with the CMP (e.g., accepts or rejects cookies).</li>
</ul>
Why is data sent?
Data is sent to TrustArc to:
<ul>
<li>Provide and manage the cookie consent experience.</li>
<li>Comply with privacy regulations.</li>
</ul>
Where is data sent?
Data is sent to the following TrustArc endpoint:
<ul>
<li><code>https://consent.trustarc.com/</code>: To load the script, along with associated images, styles, and settings.</li>
</ul>
Links to TrustArc’s terms and policies:
<ul>
<li>Privacy Policy: <a href="https://trustarc.com/privacy-policy/" rel="nofollow ugc">https://trustarc.com/privacy-policy/</a></li>
<li>Terms of Service: <a href="https://trustarc.com/subscription-services-agreement/" rel="nofollow ugc">https://trustarc.com/subscription-services-agreement/</a></li>
</ul>
Important Note: Installing this plugin alone does not guarantee compliance with GDPR, CCPA, or other privacy laws. You need to configure the plugin appropriately and ensure your cookie notice and consent management practices meet the specific legal requirements.

RoyalComply vs TrustArc Cookie Consent Manager