cookie aux fines chips

WyConsent – Self-Hosted GDPR & Law 25 Cookie Consent Plugin

Version :

1.0.8

This plugin is used by 13 websites up to date !
The 100% local CMP for your WordPress site
WordPress

Since the strict enforcement of the GDPR, Quebec’s Law 25 and the guidelines of France’s data protection authority (CNIL), every website must obtain its visitors’ consent before setting any non-essential tracker. WyConsent handles this obligation end to end, right inside WordPress: consent banner, prior script blocking, proof-of-consent log and cookie scanner.

Unlike SaaS solutions billed per site and per traffic volume, WyConsent is 100% self-hosted. Everything runs on your own server: no visitor data ever leaves your site, no traffic-based subscription, no pageview cap, no dependency on an external platform.

The core of the product is real blocking: non-essential scripts, iframes and pixels are neutralized until the visitor has given consent (deny by default). Showing a banner while Google Analytics and Meta are already running in the background is a common compliance failure. WyConsent prevents it by design.

The banner is fully customizable through a visual configurator (layout, colors, typography, position), with one-click import of your Elementor Kit styles. The “Reject all” button is given the same prominence as “Accept all”, as required by the CNIL and Law 25.

WyConsent also includes: a local cookie scanner (server-side analysis + browser capture), a cookie table you can publish via shortcode on your existing policy page, Google Consent Mode v2 support, Polylang and WPML compatibility for multilingual sites, a WP Consent API relay, and a privacy-friendly consent log (timestamped proof, no plain-text IP addresses, CSV export).

No code to write. A setup wizard guides you from installation to compliance. Compatible with WordPress 6.4+, PHP 8.1+, WooCommerce and Elementor.

1

Licence
40 $
  • Annual payment

5

Licences
160 $
  • Annual payment

∞

Licences illimitées
250 $
  • Annual payment

You will also have the option to choose a lifetime license from each of our offers on the payment page.

As we provide an environment to test our plugins, we do not provide refunds once the plugin is purchased. We have had too many smart guys who install the plugins, ask for a refund and continue using our plugins.

Are you more into video or screenshot?

Because having a choice is good :)

Discover our extension in action in video & through the image gallery.

mailgun elementor,elementor form mailgun,mailgun wordpress plugin,connect mailgun elementor form
FAQS

Here you will find some frequently asked questions about this plugin. If you cannot find the answer to your questions, do not hesitate to contact us, we will respond quickly !

Yes, by design. WyConsent blocks non-essential trackers before consent, records minimized proof of consent, and lets you choose the legal framework that applies to your visitors (GDPR/CNIL, Quebec’s Law 25, PIPEDA). The consent model adjusts automatically: strict opt-in for Europe, privacy by default for Quebec. WyConsent covers the technical side of compliance; drafting your privacy policy is still up to you, ideally with the help of legal counsel.
Those solutions run as SaaS: they charge per site and per traffic volume, and they store your visitors’ consent records on their own servers. WyConsent is fully self-hosted. The price depends neither on your traffic nor on your number of pages, no data leaves your site, and you don’t rely on a third-party platform that could raise its prices or shut down.
No. The banner, blocking, scanner and consent log all run on your server. No external request is made when your pages load. Consent records are stored in your own WordPress database, pseudonymized and without plain-text IP addresses.
No. Each module only loads its assets where they are needed, and there are no calls to any external server. The plugin is compatible with the main caching plugins (WP Rocket, LiteSpeed…) and causes no layout shift when the banner loads.
No. Installation works like any other WordPress plugin. A setup wizard guides you through a few steps: choosing the legal framework, scanning your site, categorizing the detected trackers, customizing the banner, then publishing. All that’s left is to paste the cookie table shortcode into your privacy policy page.
mailgun elementor,elementor form mailgun,mailgun wordpress plugin,connect mailgun elementor form

= 1.0.8 =
* Improved: WyConsent now formally declares itself to the WP Consent API, so Site Health and plugins relying on the Consent API (such as Site Kit) recognize it as the consent manager of your site.

= 1.0.7 =
* Fixed: after importing an Elementor Kit, the “Save appearance” button could do nothing. Kits that use a line height such as 1.25 are now accepted and saved normally.

= 1.0.6 =
* Maintenance: updated the bundled licensing library to its latest version.

= 1.0.5 =
* Fixed: a script you had set to “Never block” in Cookie management was blocked anyway, under the default category. The setting is now honoured, everywhere it applies: scripts, iframes, tracking pixels and connection hints.
* Fixed: a blocked script that came with its own configuration snippet (a very common pattern, used by many plugins) never came back after consent. It was stripped of its address but not marked as restorable, so it stayed dead even for visitors who accepted everything. Those scripts now come back, in the right order.
* Fixed: a restored script could run before the snippet that configures it, because a script re-inserted by JavaScript runs asynchronously by default. The original order is now preserved.
* New: Cloudflare Turnstile and hCaptcha ship as essential and are never blocked. They protect the form the visitor is trying to send, and blocking them stopped submissions for anyone who declined. Google reCAPTCHA stays under Functional: Google reuses the data for its own purposes, so that call is left to you, from Cookie management.
* New: WyConsent fires a `wyco:scripts-restored` browser event once scripts come back, so a theme snippet or another plugin can re-run against a library that was held back.

= 1.0.4 =
* New: WyConsent now blocks trackers that load from an inline bootstrap script with no visible address (the Google Tag Manager pattern), such as the Tawk.to and Crisp live chats, Meta Pixel, Hotjar or LinkedIn Insight. They were detected but could still drop cookies before consent; they are now held back like any other tracker.
* New: the « content blocked » card shown in place of a video pending consent can now display the YouTube thumbnail with a dimming overlay and a play icon, so visitors recognize the video before allowing it. Off by default: turning it on loads the preview image from YouTube (a Google server) before consent, and the setting says so.
* New: full styling of that card in Appearance › Blocked embeds — title text, button label, background, overlay colour and opacity, button colours (normal and hover) and corner radius, with a live preview.
* New: for Google Maps embeds (which have no free preview image like YouTube), you can upload your own background image. It is served from your site, so no request reaches Google before consent, and it applies to Maps embeds only.

= 1.0.3 =
* New: the compliance dashboard now shows who is sending consent signals to Google (Consent Mode) — managed by Site Kit, managed by WyConsent, or not managed at all. If nobody is handling it while a Google tag is present on your site, you get a clear warning with a one-click link to fix it. Sites with no Google tools see no false alarm.
* Improved: the Google Consent Mode module card now warns when no system is relaying consent to Google, instead of staying silent.
* Improved: the banner close (×) button is now fully customizable (background, hover, icon color, corner radius) and no longer inherits your theme’s button style.
* Improved: per-button text colour on hover for the Accept / Reject / Preferences / Save buttons, and the preferences-panel title now follows the size set in the plugin.
* Improved: Polylang’s language cookie (pll_language) is now classified as strictly necessary out of the box, with a clear description.

= 1.0.2 =
* Fixed: consent choices were not recorded on some Firefox and Safari versions, so nothing appeared in the consent registry. Consent proofs are now sent reliably across browsers.
* Fixed: the consent dashboard could show figures up to 5 minutes old; it now refreshes as soon as a new choice is recorded.
* Improved: the consent runtime configuration is now shielded from JavaScript optimization (combine/defer/delay), and switching consent recording on or off automatically clears the known page caches so the change takes effect right away.

= 1.0.1 =
* Fixed: the « reopen preferences » widget could appear next to the banner on a first visit when a cache plugin (LiteSpeed, WP Rocket…) removed unused CSS. WyConsent now tells the known cache/optimization plugins to leave its own assets untouched; page caching stays enabled.
* Fixed: after activating a license, the plugin now opens the onboarding wizard and the « Manage my license » button always reaches the license screen.
* Improved: the « Open Site Kit Analytics settings » link now opens in a new tab so you don’t lose the scanner/onboarding page.

= 1.0.0 =
Initial public release.
* Consent banner and granular preferences panel with a live visual configurator.
* Prior blocking (deny by default) of scripts, iframes and pixels, with click-to-load placeholders.
* Self-hosted consent log: timestamped, minimized proof, dashboard, CSV export, automatic retention, WordPress privacy-tools integration.
* Cookie scanner (server crawl + assisted browser capture) and unified Cookie management workspace.
* Cookie table shortcode and editor block for the privacy policy.
* Google Consent Mode v2.
* Multilingual support via Polylang and WPML String Translation.
* Elementor Kit color/font import.
* WP Consent API relay.
* Legal frameworks: GDPR/CNIL, Law 25 (Quebec), PIPEDA and a flexible mode.

Leave a Reply

Your email address will not be published. Required fields are marked *

OR
Un projet en tête ?
C’est le moment de nous contacter ! 🤓
Merci d'indiquer le budget maximum à ne pas dépasser pour ce projet.