Consent Warden

FAQ

Does this plugin block scripts or cookies until consent is given?

Not in the free edition. The free edition displays a consent notice and records acceptance via a browser cookie. Script blocking (preventing analytics or marketing scripts from loading before consent), Google Consent Mode v2, and per-category consent management are available in the paid editions.

Where is consent stored?

Consent is stored in a browser cookie named cwarden_consent on the visitor’s device. No consent data is sent to the server or stored in the WordPress database. The cookie uses SameSite=Lax and expires after the number of days you configure (default: 365).

What JavaScript event fires when a visitor accepts?

The plugin dispatches a cwarden:consent CustomEvent on document when the visitor clicks Accept. You can listen for it in your own scripts:

document.addEventListener('cwarden:consent', function(e) { /* your code */ });

Is this plugin GDPR compliant?

This plugin provides the consent mechanism — the banner and cookie — that GDPR requires before setting non-essential cookies. Actual compliance depends on your site as a whole: your privacy policy, the cookies your site sets, and how you process visitor data. Consult a legal professional for advice specific to your situation.

Will this conflict with other cookie consent plugins?

You should only run one consent plugin at a time. Deactivate any other cookie consent or GDPR plugins before activating Consent Warden.

How do I reset or remove the banner for a specific visitor?

The visitor can clear their browser cookies. Alternatively, you can delete the cwarden_consent cookie from your browser developer tools to see the banner again.

How do I remove all plugin data on uninstall?

Deleting the plugin from the WordPress Plugins screen removes all saved settings (cwarden_settings option) from the database automatically.

Does the banner work with page caching?

Yes. The banner is rendered in the footer via PHP and shown or hidden client-side based on the consent cookie. It is compatible with full-page caching plugins (WP Super Cache, W3 Total Cache, WP Rocket, etc.) because the consent check runs in the visitor’s browser, not on the server.