privacyhubofficial

PrivacyHub Cookie Consent connects your WordPress site to the PrivacyHub consent platform.
It helps site owners deploy and manage consent banners, block non-essential scripts until consent is granted, and send Google Consent Mode v2 signals.
Supported banner and framework modes include:
<ul>
<li>Simple banner</li>
<li>Enhanced banner</li>
<li>IAB TCF for GDPR and ePrivacy use cases</li>
<li>US GPP banner for US state privacy use cases</li>
</ul>
PrivacyHub can be configured for websites operating in or targeting regions such as:
<ul>
<li>European Union and EEA</li>
<li>United Kingdom</li>
<li>Switzerland</li>
<li>United States</li>
<li>Canada</li>
<li>Brazil</li>
<li>South Africa</li>
<li>Australia</li>
<li>Singapore</li>
<li>Middle East deployments using PrivacyHub regional configurations</li>
</ul>
Key features:
<ul>
<li>Loads your configured PrivacyHub banner using your Website ID</li>
<li>Block-first handling for common analytics, marketing, and preferences scripts</li>
<li>Google Consent Mode v2 default and update signaling</li>
<li>Optional GA4 and GTM runtime loading after consent</li>
<li>Admin settings page for Website ID, script blocking, and Google Consent Mode configuration</li>
</ul>
<h4>External services</h4>
This plugin connects to external services to load the consent runtime and, when configured by the site owner, send Google Consent Mode v2 signals and load Google tags after consent.
It may contact:
<ul>
<li><code>https://api.privacyhub.ai/functions/v1/cookie-consent-script</code></li>
<li><code>https://api.privacyhub.ai/functions/v1/ph</code> (optional thin loader, when enabled by integrators)</li>
<li><code>https://www.googletagmanager.com/gtag/js</code> (when a GA4 Measurement ID is configured and analytics consent is granted)</li>
<li><code>https://www.googletagmanager.com/gtm.js</code> (when a GTM Container ID is configured and eligible consent is granted)</li>
</ul>
What the services are used for:
<ul>
<li>Retrieve and render the configured PrivacyHub consent banner for the current Website ID</li>
<li>Apply configured consent behavior for the active site and region setup</li>
<li>Process consent-related frontend runtime behavior configured in PrivacyHub</li>
<li>Initialize Google Consent Mode v2 defaults and updates</li>
<li>Load GA4 or GTM only after the relevant consent state allows it</li>
</ul>
When they are called:
<ul>
<li>On frontend page loads when the plugin is enabled and a Website ID is configured</li>
<li>After consent is granted, if GA4 and/or GTM IDs are configured by the site owner</li>
</ul>
What is sent:
<ul>
<li>The configured Website ID in the PrivacyHub script request query string</li>
<li>Standard browser request metadata automatically sent by the site visitor’s browser to the destination host</li>
<li>Google tag requests generated by the site owner’s configured GA4 or GTM implementation after consent</li>
</ul>
Service providers:
<ul>
<li>PrivacyHub</li>
<li>Google</li>
</ul>
Service links:
<ul>
<li>PrivacyHub website: https://www.privacyhub.ai/</li>
<li>Register: https://www.privacyhub.ai/register</li>
<li>Login: https://www.privacyhub.ai/login</li>
<li>Privacy policy: https://www.privacyhub.ai/privacy-policy</li>
<li>Help center: https://www.privacyhub.ai/help-center/enable-google-consent-mode</li>
<li>Google business privacy information: https://business.safety.google/privacy/</li>
</ul>
<h4>Asset licensing</h4>
The bundled plugin assets in the <code>assets/</code> directory are original PrivacyHub branding assets distributed with this plugin release for use within the plugin admin interface.

PrivacyHub Cookie Consent

Cookie consent banners, script blocking, and Google Consent Mode v2 for GDPR, UK/Swiss privacy, US state privacy, and more.

cookielex

CookieLex is a consent management platform for websites that need a configurable cookie banner and related privacy tools.
This plugin connects a WordPress site to a CookieLex account or CookieLex site key. After the site is connected, the plugin loads the CookieLex CMP script on public WordPress pages so the CookieLex banner can display and use the banner configuration from your CookieLex dashboard.
Depending on your CookieLex account and site configuration, CookieLex can help you manage consent choices, cookie categories, consent logging, cookie scanning, and privacy or cookie policy tools. Configuration is managed in CookieLex, not primarily inside WordPress.
Website owners remain responsible for configuring CookieLex appropriately for their site, jurisdiction, installed scripts, policies, and legal obligations. This plugin and the CookieLex service can support privacy compliance workflows, but they do not guarantee compliance with GDPR, ePrivacy, CCPA/CPRA, or any other law.
<h3>External services</h3>
This plugin connects to CookieLex services so it can connect your WordPress site to CookieLex, load the hosted consent banner, and synchronize the site connection.
This service is provided by CookieLex.
Website: https://cookielex.com/
Terms and conditions: https://app.cookielex.com/terms-and-conditions
Privacy policy: https://app.cookielex.com/privacy-policy
Production service domain used by the plugin: https://app.cookielex.com/
The plugin makes these external requests:
<ul>
<li>When an administrator clicks “Connect to CookieLex”, WordPress redirects the administrator to <code>https://app.cookielex.com/integrations/wordpress/connect</code>.</li>
<li>The connect request includes the WordPress callback URL, site URL, a temporary state value, plugin version, and WordPress version.</li>
<li>When CookieLex redirects back to WordPress with a connection token, the plugin sends that token to <code>https://app.cookielex.com/api/integrations/wordpress/exchange</code>.</li>
<li>After a successful connection, the plugin stores a heartbeat token in the WordPress option <code>cookielexccpc_heartbeat_token</code> and sends a daily WP-Cron heartbeat to <code>https://app.cookielex.com/api/integrations/wordpress/heartbeat</code>.</li>
<li>When a site key is saved or returned by the connection flow, the public site loads the CookieLex CMP script from the configured embed URL. By default this is <code>https://app.cookielex.com/cmp/embed/{site_key}</code>.</li>
</ul>
Data sent to CookieLex by this plugin may include:
<ul>
<li>Site key.</li>
<li>Site URL or domain.</li>
<li>WordPress version.</li>
<li>Plugin version.</li>
<li>Temporary connection state and connection token during the administrator connect flow.</li>
<li>Heartbeat token during the daily heartbeat request. The token is sent in a POST JSON request body and is used only to authenticate the plugin installation status.</li>
<li>Connection metadata returned by CookieLex, such as embed URL, dashboard URL, domain, and connection time, which is stored in the WordPress option <code>cookielexccpc_settings</code>.</li>
<li>Daily heartbeat metadata, including site key, plugin version, WordPress version, and site/domain information. This is used to show whether the WordPress plugin is actively installed and recently seen in CookieLex.</li>
</ul>
The frontend CookieLex CMP script is loaded by visitors’ browsers from CookieLex servers. That browser request includes normal web request data, such as IP address and user agent, as part of the request to CookieLex. The CMP script may process visitor consent choices according to your CookieLex account and banner configuration.
This plugin does not send raw WordPress administrator passwords to CookieLex. The WordPress admin screen masks the stored site key and does not print raw connection or heartbeat tokens.
CookieLex provides this service under its terms and conditions at https://app.cookielex.com/terms-and-conditions and privacy policy at https://app.cookielex.com/privacy-policy.
<h3>Data storage</h3>
The plugin stores only the integration settings needed to connect WordPress to CookieLex.
Data stored in WordPress options may include:
<ul>
<li><code>cookielexccpc_settings</code>: site key, embed URL, dashboard URL, connected domain, connection time, heartbeat URL, and last heartbeat time.</li>
<li><code>cookielexccpc_heartbeat_token</code>: heartbeat token returned by CookieLex after the site is connected.</li>
</ul>
The plugin also stores a temporary connection state in the transient <code>cookielexccpc_connect_state</code> during the administrator connect flow. This transient expires after 10 minutes.
When the site is disconnected from the CookieLex admin page, the plugin removes the stored CookieLex settings, heartbeat token, and scheduled heartbeat event. When the plugin is uninstalled, <code>uninstall.php</code> removes the same stored options, scheduled event, and temporary connection transient.

CookieLex Cookie Consent & Privacy Compliance

Add the CookieLex consent banner to WordPress and connect your site to CookieLex.

PrivacyHub Cookie Consent vs CookieLex Cookie Consent & Privacy Compliance