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.

jumptech

<h3>Overview</h3>
<p>The WordPress Consent Solution Plugin is a powerful tool that empowers website owners to easily configure a Consent Management Platform (CMP) and preemptively block all trackers on their website. This plugin ensures compliance with privacy regulations by providing users with the ability to manage their consent preferences for tracking technologies.</p>
<h3>Features</h3>
<ol>
<li>Consent Management Platform (CMP)<br />
User-Friendly Interface: The plugin offers an intuitive dashboard for configuring and customizing the Consent Management Platform to suit your website’s needs.<br />
Customizable Cookie Banners: Easily create and customize consent banners to inform users about the use of trackers on your website.<br />
Consent Logging: Keep track of user consent preferences and ensure compliance with privacy regulations.</li>
<li>Tracker Preemptive Blocking<br />
Comprehensive Tracker Database: The plugin includes a regularly updated database of known trackers. It enables you to preemptively block these trackers, enhancing user privacy.<br />
The plugin preemptively blocks all the scripts that might contain a string in the <code>src</code> attribute or in the inner HTML that matches the strings you can configure on <a href="https://avacy.eu" rel="nofollow ugc">Avacy</a> for each vendor.</li>
</ol>
<p>Avacy is a SaaS-based CMP that helps websites manage user consents efficiently and in compliance with data protection regulations. The platform offers customizable consent forms and integrates seamlessly with various web properties.</p>
<h3>Compatible with WP Consent API</h3>
<p>Avacy integrates out-of-the-box with the <a href="https://wordpress.org/plugins/wp-consent-api/" rel="ugc">WP Consent API</a> plugin. When WP Consent API is active, Avacy:</p>
<ul>
<li>registers itself as a compliant CMP (no admin action required);</li>
<li>forces the <code>optin</code> consent type so other WP Consent API-aware plugins behave correctly by default;</li>
<li>bridges the Avacy banner consent event to <code>wp_set_consent</code>, mapping Google Consent Mode flags to WP Consent API categories.</li>
</ul>
<p>The mapping applied when the user interacts with the banner is:</p>
<p>  WP Consent API category<br />
  Granted when the user accepts…</p>
<p>  <code>functional</code><br />
  always <code>allow</code></p>
<p>  <code>preferences</code><br />
  <code>personalization_storage</code></p>
<p>  <code>statistics</code><br />
  <code>analytics_storage</code></p>
<p>  <code>statistics-anonymous</code><br />
  <code>analytics_storage</code></p>
<p>  <code>marketing</code><br />
  any of <code>ad_storage</code>, <code>ad_user_data</code>, <code>ad_personalization</code></p>
<p>The integration is dormant when WP Consent API is not installed, so it is safe to enable Avacy on any site.</p>
<h3>Usage</h3>
<h3>Cookie Banners:</h3>
<p>Cookie banners will automatically appear on your site once configured.<br />
Users can manage their consent preferences through these banners.</p>
<h3>Tracker Control:</h3>
<p>Trackers are preemptively blocked based on a blacklist JSON file hosted on an AWS content delivery network.<br />
Every time a page in the website is loaded, Avacy checks if scripts injected in the current page have <code>src</code> attribute or the <code>innerHTML</code> property containing a string matching the patterns in the blacklist and, if so, overrides some attributes and blocks the script.<br />
Every script blocked this way will be launched only if user grants consent to the corresponding vendor and purposes by opting-in from the first layer or by selecting the vendor and its purposes from the second layer (the preference center).</p>
<h4>CDN Information</h4>
<p>The CDN used by Avacy is CloudFront, pointing to the following S3 bucket:</p>
<pre><code>https://avacy-cdn.s3.eu-central-1.amazonaws.com/

https://assets.avacy-cdn.com/
</code></pre>
<p><strong>Integration Example</strong><br />
Each custom vendor list can be reached using the following format:</p>
<pre><code>https://assets.avacy-cdn.com/config/{avacy_team_name}/{avacy_webspace_key}/custom-vendor-list.json;
</code></pre>
<p><strong>Explanation</strong></p>
<p><strong>Base Url</strong>: The base URL for the configuration file is https://assets.avacy-cdn.com/config/.<br />
<strong><code>avacy_team_name</code></strong>: This option should be replaced with your specific tenant identifier. This is a unique identifier for your organization within Avacy.<br />
<strong><code>avacy_webspace_key</code></strong>: This option should be replaced with your specific webspace key. This is a unique identifier for your specific webspace within your tenant’s account.</p>
<p><strong>Example URL</strong><br />
Assuming the following:</p>
<p>Tenant ID: <em>tenant123</em><br />
Webspace Key: <em>webspace456</em><br />
The URL to access the custom vendor list would be:</p>
<pre><code>https://assets.avacy-cdn.com/config/tenant123/webspace456/custom-vendor-list.json
</code></pre>
<p><strong>Account Requirements</strong><br />
To connect to and utilize Avacy’s services, you need an active Avacy account with valid credentials, which include:</p>
<p><strong>Tenant ID</strong>: Provided upon registration with Avacy.<br />
<strong>Webspace Key</strong>: Generated after creating a new web space on Avacy.<br />
Ensure you have these credentials available to correctly generate the URLs needed for integration.</p>
<h3>Avacy Consent Solution API</h3>
<p>The plugin provides an interface that allows connecting to your consent archive on Avacy. To do this, it’s necessary to generate a token from the Avacy platform and insert it into the Token field in the API token tab. This way, all the forms present on the page will be visible, and it will be possible to select various options, including:</p>
<ul>
<li>the ability to store consents given for that specific form in the consent archive;</li>
<li>the fields to store for that form;</li>
<li>a field to identify the user who has given the consent to be stored in the archive.</li>
</ul>
<p>Everytime a user submits his data from a contact form, Avacy will perform a POST request towards Avacy Consent API, using the previously generated token as authenticator.</p>
<h4>Under What Circumstances is Avacy Used?</h4>
<p>Avacy is utilized whenever users provide consent through forms or interactions on your WordPress site. The plugin sends this consent data to Avacy’s servers for storage and processing.</p>
<h4>Avacy Service Link</h4>
<p>For more information about Avacy and its features, visit Avacy’s <a href="https://avacysolution.com/" rel="nofollow ugc">website</a>.</p>
<h4>Avacy Terms of Use and Privacy Policies</h4>
<p>Avacy uses 3rd party services as the Avacy REST API and AWS distributions to provide assets as the blacklist JSON file.<br />
Before integrating Avacy with this plugin, please review the Avacy <a href="https://avacy.eu/terms-and-conditions" rel="nofollow ugc">Terms of use</a> and <a href="https://api.avacy.eu/jumpgroup/privacypolicy/14/it" rel="nofollow ugc">Privacy Policy</a> to understand how your data is handled and what responsibilities you have as a user of their service.</p>
<p>We welcome your feedback and suggestions to improve the functionality of the plugin.</p>
<h3>Disclosure of Third-Party Service Usage</h3>
<p>Our plugin utilizes third-party services to enhance its functionality. Below, we detail the specific circumstances under which these services are used, along with links to the respective service providers, their terms of use, and privacy policies.</p>
<h3>Services Utilized</h3>
<p><strong>Amazon Web Services (AWS)</strong> is a leading cloud platform offering a wide range of services, including computing power, storage, and networking, as well as advanced technologies like machine learning and IoT. AWS is designed for flexibility, scalability, and service reliability.</p>
<p><strong>AWS CloudFront</strong> is a fast content delivery network (CDN) service that securely delivers data, videos, applications, and APIs to users globally with low latency and high transfer speeds.</p>
<blockquote>
<p>The URLs <em>https://jumpgroup.avacy-cdn.com</em> and <em>https://assets.avacy-cdn.com</em> are custom domains provided to access the AWS CloudFront service. Each asset is fetched from these URLs.</p>
</blockquote>
<p><strong>Script Enqueuing</strong><br />
Script enqueuing involves dynamically adding the main JavaScript core in order to display the cookie banner on your page. This method ensures that scripts are loaded only when needed, reducing page load times and improving performance.</p>
<p><strong>Configuration Fetching</strong><br />
CMP configuration fetching is used to dynamically load the latest CMP configuration settings and vendor lists from a remote server. This process ensures that the plugin operates with the most current data, improving security, compatibility, and functionality.</p>
<h4>Service Provider Information</h4>
<p><strong>Service URL</strong>: <a href="https://aws.amazon.com/" rel="nofollow ugc">Amazon Web Services</a><br />
<strong>Privacy Policy</strong>: <a href="https://d1.awsstatic.com/legal/privacypolicy/AWS%20Privacy%20Notice%20-%202024-01-01_IT.pdf" rel="nofollow ugc">AWS Privacy Policy</a><br />
<strong>Terms of Use</strong>: <a href="https://aws.amazon.com/it/service-terms/" rel="nofollow ugc">AWS Terms of Use</a></p>
<p><strong>Legal Protection</strong><br />
For your protection and to ensure transparency, we disclose the reliance on third-party services within our plugin. The URLs above provide detailed information on the terms of use and privacy policies of AWS. Users are encouraged to review these documents to understand the terms and conditions under which these third-party services operate.</p>
<p>By using our plugin, you acknowledge and agree to these terms and conditions. If you have any questions or concerns, please refer to the provided links or contact us directly for more information.</p>
<h3>License</h3>
<p>This WordPress Consent Solution Plugin is licensed under the <a href="https://www.gnu.org/licenses/gpl-2.0.html" rel="nofollow ugc">GNU General Public License v2.0 or later</a>.</p>


Oven Cookie Consent vs Avacy CMP