WP Upgrader

Sowmedia

The best GDPR compliance available! Allows visitors to grant explicit consent for ANY feature of your site. Control activation and deactivation of plugins, content, scripts and more before WordPress is even loaded. 
Helps you to truely comply with European GDPR standards.
<ul>
<li>Disables all plugins in WordPress at root level, when setup to work with GDPR Consent plugin.</li>
<li>Managed plugins only activate once the user gives consent</li>
<li>Manage your external scripts and inline content with GDPR consents</li>
</ul>
<h3>Quick Start Guide</h3>
<h4>Shortcodes</h4>
<ul>
<li><code>[gdpr_consent_settings]</code> This will render the GDPR Settings page. Options include:
<ul>
<li><code>popup</code> (bool) TRUE/FALSE</li>
<li><code>open</code> (bool) TRUE/FALSE</li>
<li><code>suffix</code> (string) Can be any string, this will be appended to the #id</li>
</ul>
</li>
<li><code>[gdpr_consent_embed]...[/gdpr_consent_embed]</code> This will wrap Inline content and hides it as long as NO consent is given. If consent is given the content is shown. Options include:
<ul>
<li><code>title</code> The title to render above the Inline consent block (Optional)</li>
<li><code>id</code> or <code>ids</code> the ID or list of ID’s (comma seperated) of consents needed to Activate the content.</li>
<li><code>widget</code> (BOOL) true/false (Show the widget? Or just display a Notification ‘No consent was given.” This can be configured in the WP Admin Settings)</li>
<li><code>suffix</code> Can be any string, this will be appended to the #ID (maybe used to resolve conflicts or display multiple settings pages.)</li>
</ul>
</li>
<li>Inline shortcode: <code>[gdpr_consent_inactive_content]</code> (only work within <code>[gdpr_consent_embed]</code>) splits the content as such; above is the Active content, below is the Inactive content. Depending on if consent was given or not it will be either the Active or Inactive content.</li>
</ul>
<h4>Programmatic</h4>
(This feature is for Developers) 
You can Programmatically check if a consent was given using WordPress Actions.
PLEASE NOTE: 
Use <code>do_action</code> NOT <code>add_action</code> to check if the consent was set!
Available actions: 
* gdprc_consent_%ID%_given
Example: 
 <code>if(do_action('gdprc_consent_2635_given')){ 
 echo 'Consent was given!'; 
}else{ 
 // No consent was given 
}</code>
Alternatively you may use the wrapper method <code>gdpr_consent(2635)</code> which is a regular PHP function.
<h4>Template filters</h4>
This allows you to fully customize the look & feel of the plugin! 
Available WordPress Template Filters for altering the HTML sections the GDPR Settings page.
<ul>
<li>gdprc_settings_before</li>
<li>gdprc_settings_after</li>
<li>gdprc_settings_consents_before</li>
<li>gdprc_settings_consents_after</li>
<li>gdprc_settings_acceptall_before</li>
<li>gdprc_settings_acceptall_after</li>
<li>gdprc_settings_actions_before</li>
<li>gdprc_settings_actions_after</li>
</ul>
Available WordPress Template Filters for altering the HTML sections of GDPR Consents.
<ul>
<li>gdprc_consent_before</li>
<li>gdprc_consent_after</li>
<li>gdprc_consent_classes</li>
<li>gdprc_consent_title</li>
<li>gdprc_consent_iconclass</li>
<li>gdprc_consent_description</li>
<li>gdprc_consent_%ID%_before</li>
<li>gdprc_consent_%ID%_after</li>
<li>gdprc_consent_%ID%_classes</li>
<li>gdprc_consent_%ID%_title</li>
<li>gdprc_consent_%ID%_iconclass</li>
<li>gdprc_consent_%ID%_description</li>
</ul>
Available WordPress Template Filters for altering the HTML sections of GDPR Embedded Content shortcode.
<ul>
<li>gdprc_embed_before</li>
<li>gdprc_embed_after</li>
<li>gdprc_embed_header</li>
<li>gdprc_embed_consents_before</li>
<li>gdprc_embed_consents_after</li>
<li>gdprc_embed_actions_before</li>
<li>gdprc_embed_actions_after</li>
</ul>
Available WordPress Template Filters for altering the HTML sections of GDPR Permissionbar.
<ul>
<li>gdprc_bar_before</li>
<li>gdprc_bar_after</li>
<li>gdprc_bar_header</li>
<li>gdprc_bar_acceptall_before</li>
<li>gdprc_bar_acceptall_after</li>
<li>gdprc_bar_actions_before</li>
<li>gdprc_bar_actions_after</li>
<li>gdprc_bar_links_before (null, $seperator)</li>
<li>gdprc_bar_links_after (null, $seperator)</li>
<li>gdprc_bar_settings_before</li>
<li>gdprc_bar_settings</li>
<li>gdprc_bar_settings_after</li>
</ul>
Available WordPress Template Filters for altering the CSS rules of all GDPR elements.
<ul>
<li>gdprc_stylesheet_before</li>
<li>gdprc_stylesheet_after</li>
<li>gdprc_stylesheet_background</li>
<li>gdprc_stylesheet_border</li>
<li>gdprc_stylesheet_embed</li>
<li>gdprc_stylesheet_embed_popup</li>
<li>gdprc_stylesheet_bar_settings</li>
</ul>

GDPR Consent Plugin

The best GDPR compliance available! Allows visitors to grant explicit consent for ANY feature of your site. Control activation and deactivation of plu …

Ronni K. Gothard Christiansen

Gia Phú

Viet Nguyen

AesirX

AesirX CMP is a privacy-first Consent Management Platform for WordPress built for consent-before-tracking.
AesirX CMP helps you collect and manage user consent in a clear and compliant way – and, importantly, it helps you hold back scripts, cookies, and tracking technologies until consent is given using a first-party enforcement approach.
You get a practical CMP baseline for free forever, and you can upgrade to AesirX CMP Pro to unlock advanced automation, consent analytics, and additional compliance tooling.
<h4>How AesirX CMP for WordPress Solves Problems:</h4>
<ol>
<li>Consent-before-tracking: Configure consent flows and ensure tracking is blocked until the user opts in.</li>
<li>Covers all tracking technologies: Not just cookies, as the many alternatives that is non-compliant.</li>
<li>First-party enforcement: Manage consent inside WordPress without relying on third-party CMP services.</li>
<li>Free forever: CMP Freemium functionality is available at no cost.</li>
<li>Upgradeable Pro versions: Add advanced features when needed (AI advisor / auto-block, consent analytics, ID/age verification, privacy scanning, and more).</li>
</ol>
<h4>Features (Free)</h4>
<ul>
<li>Overview: See your consent configuration status at a glance.</li>
<li>Consent Modal (Templates): Create and customize your consent modal using ready-to-use templates.</li>
<li>Consent Logic (Basic): Configure consent mode (opt-in / opt-out) and Global Privacy Controls (GPC) behavior (where applicable).</li>
<li>Consent Log: Record consent events (log only – no consent analytics in free).</li>
<li>Geo-handling: Apply region-aware consent behavior and templates.</li>
<li>Consent Shield (Lite): Hold back tracking until consent using:
<ul>
<li>WP plugin blocking + category mapping</li>
<li>Domain Shield / Path Shield rules</li>
</ul>
</li>
</ul>
Lite version does not include Permanent Block and does not include first-party/third-party blocking mode options.
<h4>Pro Versions (Optional Upgrades)</h4>
Upgrade to AesirX CMP Pro to unlock:
<ul>
<li>Consent Shield (Full): Includes Permanent Block and advanced blocking modes/options.</li>
<li>Consent Analytics: Analyze consent rates and consent performance.</li>
<li>AI Privacy Advisor: Automation and recommendations to improve compliance and setup.</li>
<li>AI Auto-Blocking: Configure block of 3rd parties and plugins based on AI Privacy Advisor.</li>
<li>Privacy Scanner: Detect tracking technologies and compliance risks.</li>
<li>ID Verification: Optional verification flows (e.g., age/ID) for regulated experiences using zero-knowledge proofs.</li>
</ul>
<h4>3rd party services</h4>
AesirX CMP does not require third-party services for standard consent mode and consent enforcement. 
However, AesirX CMP includes an optional Decentralized Consent mode. If the site owner enables Decentralized Consent and the site visitor chooses to use it, the plugin will load and use the following third-party services to establish the decentralized consent flow:
<ul>
<li>WalletConnect (used to connect the visitor’s wallet for signing the decentralized consent action)</li>
<li>Concordium (used as part of the decentralized consent verification and ID anchoring flow, depending on configuration)</li>
</ul>
These services are not loaded unless Decentralized Consent mode is enabled and selected by the visitor.
This may transmit wallet connection metadata and a signed consent payload.
When used for ID verification zero-knowledge proofs are used as privacy preserving technologies (PETs) to ensure the personal data is not shared with the website owner.
<h4>Source code for compressed content</h4>
Human-readable source code: 
* AesirX CMP Freemium for WP: https://github.com/aesirxio/wordpress-freemium-consent-plugin
<h4>Validation</h4>
Terms of service: https://aesirx.io/terms-conditions 
Privacy policy: https://aesirx.io/privacy-policy

AesirX Consent

Integrating first-party consent for GDPR/ePrivacy compliance.

GDPR Consent Plugin vs AesirX Consent