Aslam Hasib

Zenaul Islam

DevItems

Madhusudan

<p>CookieRay is a cookie consent and privacy tooling plugin for WordPress. It stores data on your hosting account and runs in your environment. There is no external SaaS dashboard for site operation.</p>
<p>CookieRay helps website owners manage cookie consent settings for GDPR, CCPA, ePrivacy, and other privacy-related requirements. Legal compliance depends on your website setup, third-party tools, region, and how the plugin is configured.</p>
<p>CookieRay provides a visitor-facing consent experience, configurable script blocking, cookie discovery from your site, detailed consent records, and a setup dashboard to help you manage cookie consent records and support privacy-related workflows.</p>
<h4>Cookie consent banner</h4>
<p>A customizable consent surface with card and bar layouts, live preview in the admin, and nine placement positions. Visitors can Accept All, Decline All, or open a Preferences modal to choose which categories to allow (Necessary, Analytical, Functional, and Marketing). Banner text, colors, buttons, and fonts are editable without writing code.</p>
<h4>Script blocking</h4>
<p>Choose Log Only recording or Strict blocking in Settings. In Strict mode, CookieRay delays known tracking scripts until the visitor agrees to categories that match those trackers. Common patterns for services such as Google Analytics, Meta Pixel, Hotjar, HubSpot, TikTok Pixel, and many others are included out of the box.</p>
<h4>Google Consent Mode v2</h4>
<p>When enabled, CookieRay outputs consent state in the visitor’s browser for Google tags (such as GA4, Google Ads, or Google Tag Manager) that <strong>you have already placed on your site</strong>. Google Consent Mode v2 lets Google tags adjust their behavior based on visitor consent choices while supporting privacy-conscious measurement modes when consent is withheld.</p>
<p>CookieRay itself does not open separate server-side uploads of visitor payloads to Google; instead it surfaces JavaScript so tags you load can read consent signaling. Behavior of those downstream tags depends on how you configured Google products.</p>
<p>Further reading: Google’s Consent Mode documentation (linked under External Services).</p>
<h4>Cookie scanner</h4>
<p>Run a cookie scan from the WordPress admin to detect cookies surfaced on responses from your own site.</p>
<p>When an administrator starts a scan, CookieRay queues work on your server and uses the WordPress HTTP API to request public URLs belonging to <strong>your site domain</strong> (for example the homepage, published content URLs, WooCommerce storefront pages where applicable, and related routes depending on plugins). Cookie names surfaced in responses can be merged with your inventory for categorization alongside the plugin’s bundled tracking-cookie reference data.</p>
<p>CookieRay also runs deeper script-discovery passes that analyze HTML fetched from a bounded set of URLs (the embeddable deep scan inspects up to 50 URLs on the same domain, chosen from the XML sitemap when available or from the home page plus recent posts and pages). Scan coverage still depends on plugins, caches, authenticated-only flows, and what responses your site serves to CookieRay’s unauthenticated crawler.</p>
<p>There is <strong>no recurring unattended scan timetable built into CookieRay</strong>. You start scans from CookieRay screens (background processing completes those runs without another manual click).</p>
<h4>Cookie inventory</h4>
<p>View, edit, and categorize cookies discovered on your site. Assign cookies to Necessary, Analytical, Functional, or Marketing categories. Bulk-categorize or delete entries. Custom cookies can be added manually, with regex pattern support where appropriate.</p>
<h4>Consent logs</h4>
<p>Consent events can be logged with identifiers, statuses, granted categories, page URL, banner version, and timestamp fields available for review. Entries are searchable and filterable in the admin. You can export records as CSV, and export individual receipts as PDF for your record-keeping process.</p>
<h4>Dashboard</h4>
<p>See a summarized score guided by configurable checks (blocking mode, categorized cookies, policy link usage, consent expiry and scan recency reminders, whether Google Consent Mode output is enabled, and related items). Use it as onboarding guidance alongside your legal or compliance review.</p>
<h4>Scan history</h4>
<p>Review past scans: timing, URLs covered, counts, and summaries of results to track changes over time.</p>
<h4>Settings</h4>
<p>Configure consent behavior (Log Only vs Strict blocking), consent expiry, consent log retention, Google Consent Mode v2 toggle, optional data portability export flows, and related options. Banner and behavior settings are stored through WordPress options alongside plugin metadata.</p>
<h4>Privacy and data handling</h4>
<p>CookieRay does not send usage data, telemetry, or visitor payloads to CookieRay-operated servers. Consent logs and inventories stay in your site’s database unless you export them elsewhere.</p>
<p>Third-party trackers you integrate yourself (such as Google Analytics, Google Ads, Google Tag Manager, Meta Pixel, marketing pixels, embedded chat widgets, and similar vendors) may still collect information according to their own tags, configurations, vendor accounts, regions, and published policies, even when CookieRay delays or respects categories for scripts it recognizes.</p>
<p>A WordPress Cron task deletes consent records older than the retention period configured in Settings, whenever WordPress Cron runs normally on your host.</p>
<h3>Pro Features</h3>
<ul>
<li>Scheduled automatic cookie scans</li>
<li>Geo targeting – show or hide the banner by country</li>
<li>Integration with Google Tag Manager, Meta Pixel, Adobe Experience Platform</li>
<li>Trust Badge – “Privacy Protected” badge displayed in the site footer</li>
<li>Premium support and priority updates</li>
</ul>
<p><a href="https://wp.cookieray.com/#pricing" rel="nofollow ugc">Upgrade to CookieRay Pro</a></p>
<h3>Support</h3>
<p>For questions, bug reports, or help with configuration, visit the <a href="https://wp.cookieray.com/contact" rel="nofollow ugc">CookieRay support page</a>.</p>
<h3>External Services</h3>
<p>CookieRay does not send analytics, telemetry, or visitor data to CookieRay-operated servers.</p>
<h4>1. Same-site cookie scanner</h4>
<p>When an administrator runs a cookie scan, CookieRay uses the WordPress HTTP API (wp_remote_get) to fetch public URLs belonging to the same WordPress site — for example the homepage, published post URLs, WooCommerce storefront pages, and sitemap entries.</p>
<p>What is sent: Standard HTTP GET requests to your own site’s public URLs.<br />
When: Only when an administrator triggers a scan from CookieRay admin screens.<br />
Who receives the requests: Your own web server. No data is sent to CookieRay or any third party.<br />
Source file: includes/class-scanner.php</p>
<h4>2. Google Consent Mode v2 (optional, admin-enabled)</h4>
<p>When enabled in Settings, CookieRay outputs JavaScript on visitor pages that signals consent state to Google tags you have independently installed (e.g. GA4, Google Ads, Google Tag Manager). CookieRay does not make server-side HTTP calls to Google.</p>
<p>What is sent: Browser-side consent signals read by locally loaded Google tags you control.<br />
When: When Consent Mode is enabled in CookieRay Settings and visitors load pages that include your Google tags.<br />
Who receives downstream data: Google, per your Google account and tag configuration.</p>
<p>Google Privacy Policy: https://policies.google.com/privacy<br />
Google Terms of Service: https://policies.google.com/terms<br />
Google Consent Mode documentation: https://support.google.com/analytics/answer/9976101</p>


CookieRay – Cookie Banner for Cookie Consent (GDPR/CCPA Compliant)

Cookie consent banner, script blocking, Google Consent Mode v2, cookie scanner, and consent logs for WordPress.

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.

CookieRay – Cookie Banner for Cookie Consent (GDPR/CCPA Compliant) vs RoyalComply – Cookie Consent, GDPR & CCPA Compliance Banner