Billy Wilcosky

<p>Oven integrates the <a href="https://github.com/orestbida/cookieconsent" rel="nofollow ugc">CookieConsent</a> JavaScript library (v3.1.0) into WordPress to provide a compliant, accessible cookie consent experience.</p>
<h4>Features</h4>
<ul>
<li><strong>Cookie consent banner</strong> – Shows a consent modal to visitors on first visit with Accept all, Essential only, and Manage preferences.</li>
<li><strong>Automatic cookie detection</strong> – Enable “Cookie detection mode” in settings, then browse your site while logged in as an administrator. Cookies set during your visit are detected and added to the list.</li>
<li><strong>Essential vs non-essential</strong> – WordPress core cookies (login, session, comments, settings) are classified as essential; third-party and analytics cookies as non-essential. Visitors see both categories in the preferences modal.</li>
<li><strong>Revision and re-consent</strong> – When a new cookie is detected and added, the revision number is incremented. All visitors (including those who had previously accepted) must consent again.</li>
<li><strong>Logged-in vs guest</strong> – For guests, consent is stored in a cookie so they are not prompted on every visit (until the revision changes). For logged-in users, consent is stored in the database (user meta) tied to their account.</li>
<li><strong>Consent logging</strong> – For logged-in users, each consent choice is recorded in their profile. Admins and editors can view when a user accepted and which cookies they accepted (Users <span aria-hidden="true" class="wp-exclude-emoji">→</span> edit user <span aria-hidden="true" class="wp-exclude-emoji">→</span> Cookie consent).</li>
<li><strong>Cookie descriptions</strong> – You can edit a short description for each cookie so visitors know what it does. Descriptions are shown in the preferences modal.</li>
<li><strong>Privacy policy link</strong> – Optional privacy policy URL in settings is shown in the consent modal (recommended for GDPR).</li>
<li><strong>Accessibility</strong> – Uses the CookieConsent library’s built-in ARIA attributes and keyboard support.</li>
</ul>
<h4>Settings</h4>
<ul>
<li><strong>Settings <span aria-hidden="true" class="wp-exclude-emoji">→</span> Oven</strong> – Enable cookie consent, enable cookie detection mode, set an optional privacy policy URL (recommended for GDPR), and view or edit the list of detected cookies and their descriptions.</li>
</ul>
<h4>GDPR and compliance</h4>
<p>Oven is designed to support compliance with the GDPR and similar laws:</p>
<ul>
<li><strong>Consent before non-essential cookies</strong> – Non-essential cookies and scripts that set them are blocked until the user accepts. Essential cookies (e.g. login, session) are allowed without consent.</li>
<li><strong>Clear information</strong> – Visitors see a list of cookies with names and descriptions (editable in settings). You can link to your privacy policy from the consent modal.</li>
<li><strong>Granular choice</strong> – Users can accept all, essential only, or manage preferences and toggle individual non-essential cookies.</li>
<li><strong>Withdraw consent</strong> – Users can reopen the preferences modal and change or withdraw consent at any time. Rejected non-essential cookies are cleared on each visit.</li>
<li><strong>Re-consent when policy changes</strong> – When you add or reclassify cookies, the revision number increases and all visitors are asked to consent again.</li>
<li><strong>Consent logging (logged-in users)</strong> – For registered users, consent choices and timestamps are stored in their profile. Admins and editors can view consent history under Users <span aria-hidden="true" class="wp-exclude-emoji">→</span> [user] <span aria-hidden="true" class="wp-exclude-emoji">→</span> Cookie consent. Guest consent is not logged (stored only in a cookie).</li>
<li><strong>Transparency</strong> – Cookie detection mode helps you build an accurate cookie list; you can add cookies manually and describe what each one does.</li>
</ul>
<h4>Requirements</h4>
<ul>
<li>PHP 7.4 or higher</li>
<li>WordPress 5.9 or higher</li>
</ul>
<h3>Credits</h3>
<ul>
<li>CookieConsent (v3.1.0) by Orest Bida – https://github.com/orestbida/cookieconsent – MIT License.</li>
</ul>


Oven Cookie Consent

Cookie consent for WordPress: detect cookies, classify essential vs non-essential, and re-prompt visitors when your cookie list changes.

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.

Oven Cookie Consent vs Darwin Cookie Consent