cookielex

<p>CookieLex is a consent management platform for websites that need a configurable cookie banner and related privacy tools.</p>
<p>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.</p>
<p>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.</p>
<p>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.</p>
<h3>External services</h3>
<p>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.</p>
<p>This service is provided by CookieLex.</p>
<p>Website: https://cookielex.com/</p>
<p>Terms and conditions: https://app.cookielex.com/terms-and-conditions</p>
<p>Privacy policy: https://app.cookielex.com/privacy-policy</p>
<p>Production service domain used by the plugin: https://app.cookielex.com/</p>
<p>The plugin makes these external requests:</p>
<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>
<p>Data sent to CookieLex by this plugin may include:</p>
<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>
<p>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.</p>
<p>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.</p>
<p>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.</p>
<h3>Data storage</h3>
<p>The plugin stores only the integration settings needed to connect WordPress to CookieLex.</p>
<p>Data stored in WordPress options may include:</p>
<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>
<p>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.</p>
<p>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.</p>


CookieLex Cookie Consent & Privacy Compliance

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

datareporter

<p><strong>Datareporter WebCare Integration</strong> integrates your <a href="https://www.datareporter.eu/products/webcare" rel="nofollow ugc">Datareporter WebCare</a> cookie consent banner, privacy policy, and legal imprint into WordPress. WebCare is a consent management platform from Austria. You configure your consent banner, privacy policy, and imprint in WebCare, and this plugin delivers them to your WordPress site.</p>
<h4>What the Plugin Does</h4>
<ul>
<li><strong>Cookie Consent Banner:</strong> Adds the WebCare consent banner to your site. The banner collects cookie consent and includes a tag manager that controls tracking scripts based on visitor consent.</li>
<li><strong>Privacy Policy:</strong> Displays your WebCare privacy policy on any page or post using the <code>[drwc_privacy]</code> shortcode. When you update the privacy policy in WebCare, the changes are reflected on your site automatically.</li>
<li><strong>Imprint:</strong> Displays your legal imprint using the <code>[drwc_imprint]</code> shortcode. Like the privacy policy, it stays in sync with your WebCare account.</li>
<li><strong>Embed Blocker:</strong> Blocks third-party embeds (YouTube, Vimeo, Twitter/X, TikTok, Google Maps) until visitors give consent. An overlay prompts visitors to allow content per provider (<strong>Feature requires WordPress 6.9 or later</strong>).</li>
</ul>
<h4>Key Technical Features</h4>
<ul>
<li><strong>Local Caching:</strong> Cache banner assets, privacy policy, and imprint content on your server for fewer external requests.</li>
<li><strong>Subresource Integrity (SRI):</strong> SRI support for the banner script, verifying that the banner loader has not been tampered with.</li>
<li><strong>Scheduled Cache Sync:</strong> An hourly background sync keeps cached content up to date with your WebCare account.</li>
</ul>
<h4>Shortcodes</h4>
<ul>
<li><code>[drwc_privacy]</code>: Displays your privacy policy.</li>
<li><code>[drwc_imprint]</code>: Displays your imprint.</li>
</ul>
<h4>Requirements</h4>
<p>This plugin requires an <strong>active WebCare license</strong>. You can get one at the <a href="https://store.datareporter.eu/" rel="nofollow ugc">Datareporter Store</a>. The integration key from your WebCare account is needed during setup.</p>
<h4>Documentation & Support</h4>
<p>For setup instructions, configuration details, and troubleshooting on WebCare visit the <a href="https://help.datareporter.eu/docs/webcare" rel="nofollow ugc">WebCare Help Center</a>.</p>
<h3>External services</h3>
<p>This plugin connects to the <a href="https://www.datareporter.eu/products/webcare" rel="nofollow ugc">Datareporter WebCare</a> CDN (Content Delivery Network), an external service operated by <a href="https://www.datareporter.eu/" rel="nofollow ugc">Datareporter GmbH</a> (Austria). The CDN is a network of servers that hosts and delivers the cookie consent banner, privacy policy, and legal imprint content to your WordPress site. Because this content is created and managed in your <a href="https://store.datareporter.eu/" rel="nofollow ugc">WebCare dashboard</a>, the plugin must fetch it from the CDN — it cannot be generated locally.</p>
<p>The content served by the CDN (including the cookie banner text, privacy policy, and imprint) is dynamically generated based on the settings you configure in your individual WebCare license via the <a href="https://store.datareporter.eu/" rel="nofollow ugc">WebCare dashboard</a>. When you update your settings there, the CDN-served content updates automatically.</p>
<h4>What the CDN is used for</h4>
<p>The plugin uses the Datareporter WebCare CDN for three purposes:</p>
<ol>
<li><strong>Cookie consent banner</strong>: The banner JavaScript, CSS, and configuration are loaded from the CDN so your consent banner appears on every page.</li>
<li><strong>Privacy policy and imprint</strong>: The plugin fetches your privacy policy and legal imprint content from the CDN and displays it on pages where you place the <code>[drwc_privacy]</code> or <code>[drwc_imprint]</code> shortcodes.</li>
<li><strong>Integration key verification</strong>: When you enter or save your integration key in the WordPress admin panel, the plugin sends a request to the CDN to verify that the key is valid so your WebCare content is reachable.</li>
</ol>
<h4>CDN domains</h4>
<p>The plugin communicates with the following domains. The exact domain used depends on your WebCare configuration:</p>
<ul>
<li><code>webcachex-eu.datareporter.eu</code></li>
<li><code>webcachex.datareporter.eu</code></li>
<li><code>webcache-eu.datareporter.eu</code></li>
<li><code>webcache.datareporter.eu</code></li>
</ul>
<p>For example, a request to load the banner design (stylesheet) would look like this:<br />
    https://webcachex-eu.datareporter.eu/c/xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx/yyyyyyyyyyyyyyy/zzz/banner.css<br />
where <code>xxxx...</code>, <code>yyy...</code>, <code>zzz</code> are parts from your individual integration key.</p>
<h4>When data is sent</h4>
<p>No requests are made to the CDN until a site administrator activates the plugin and enters an integration key.<br />
Once active:</p>
<ul>
<li><strong>CDN mode (default)</strong>: On every page load, your visitors’ browsers send requests directly to the CDN domains listed above to load the banner script, styles, privacy policy, and imprint content.</li>
<li><strong>Cache mode (optional)</strong>: Your WordPress server fetches the same resources from the CDN during an hourly background sync and serves them locally to visitors.</li>
<li><strong>Admin panel</strong>: When you save the integration key in the plugin settings, your server sends a single request to the CDN to verify the key.</li>
</ul>
<h4>What data is sent</h4>
<p>Each request to the CDN transmits the following data:</p>
<ul>
<li>The IP address of the requesting party (the visitor’s browser in CDN mode, or your server in cache mode).</li>
<li>Standard HTTP headers: User-Agent, Referer, and Accept-Language.</li>
<li>Integration key components (client ID, organization ID, and website ID) included in the request URL.</li>
</ul>
<h4>Service provider</h4>
<p>This service is provided by <a href="https://www.datareporter.eu/" rel="nofollow ugc">Datareporter GmbH</a> (Austria): <a href="https://webcache-eu.datareporter.eu/c/025cf622-aba5-4850-93fb-e23c508e9b7f/Ey1sy7yreWON/privacynotice_en.pdf" rel="nofollow ugc">privacy policy</a>.</p>
<h3>About Datareporter</h3>
<p><a href="https://www.datareporter.eu/" rel="nofollow ugc">Datareporter GmbH</a> is an Austrian company specializing in privacy and consent management. Their WebCare platform helps website operators meet GDPR requirements with automatically updated consent banners, privacy policies, and legal imprint management.<br />
More info about us can be found at <a href="https://www.datareporter.eu/company/info" rel="nofollow ugc">datareporter.eu/company/info</a>.</p>


Datareporter WebCare Integration

Integrate the Datareporter WebCare cookie consent banner, privacy policy, and imprint into your WordPress site.

CookieLex Cookie Consent & Privacy Compliance vs Datareporter WebCare Integration