The GDPR and your Divi, Extra and Bloom forms
You have a Bloom optin in the footer, another that pops up after thirty seconds, and a contact form on your services page. All three store the email address of whoever fills them in, and none of them asks anybody for anything. The GDPR wants informed consent before that happens, and it wants you to be able to prove it.
You can fix it by hand. Bloom lets you add a checkbox field and mark it required, and so do Divi contact forms. The catch is that you have to do it form by form, remember to do it on every new one, and repeat your legal wording in each. The day you change your privacy policy, you open them all again. And when somebody asks you to prove they consented, to the exact wording they saw, you will have nothing to show them.
One layer, once, for the whole site
This plugin puts a consent layer over your forms. Your visitor clicks, reads your text, opens your privacy policy if they feel like it, and ticks the box. Until then the form does not submit.
You write the wording once and it shows up on every form on the site. Change your policy and you change it in one place.
The block is real
This is where nearly every consent overlay falls down. They cover the form with a layer, but underneath the button still works: close the layer, or press Enter in the email field, and the subscription goes through anyway.
This one runs before the code Bloom and Divi register, so their handlers never fire. We measured it: without the box ticked, the browser sends nothing at all. Closing the layer is not a shortcut either, because closing is not consenting.
On Divi contact forms it goes further and adds a genuine required field, the kind the browser itself refuses to submit. That one holds up even with JavaScript switched off.
It fits your design instead of ruining it
The layer picks up the colours of each form and works out the text colour by measuring the real contrast, so it stays readable whatever your layout looks like. If you would rather choose the colours yourself, there are colour pickers and an opacity control for letting the form show through.
And if a form already asks for consent on its own, the layer steps aside. There is no point asking the same thing twice.
The proof, which is what actually matters
Article 7.1 of the GDPR does not say ask for consent, it says be able to demonstrate it. Every acceptance is stored with the date, the email address, the IP, the form, the page and the exact wording that was on screen at that moment.
That part is handled by Terms & Conditions Consent Log, which seals each record with SHA-256, spots any later tampering, issues a downloadable PDF certificate and hooks into the WordPress privacy tools. If you would rather store them elsewhere, there is an action to hang your own code on.
The version of your policy is stored with each record too, so later you can tell apart who accepted the wording you have now and who accepted an older one.
Works with everything from Elegant Themes
Divi, including Divi 5. Extra. The Divi Builder plugin on any theme. And Bloom, with or without Divi, in all six layouts: popup, fly in, inline, below post, widget and locked content.
Accessible, and in your language
The layer is a proper dialog: it traps focus, closes with Escape, hands focus back where it came from and works entirely from the keyboard. While it is open the form underneath is inert, so screen readers and the Tab key stay out of it.
Leave the texts empty and they follow the language of each visitor, which is what you want on a multilingual site. Write your own and they are used exactly as typed. Ships in English and Spanish, ready for WPML and Polylang.
Coming from the old plugin?
Version 2.0.0 is a complete rewrite. Your texts, colours and settings are imported the first time you open the settings screen, and nothing from the old version is deleted, so you can go back if you want to.
If you are still on the 1.0.x line, you should know it does not run on PHP 8 at all.
Requirements
WordPress 6.0 or later and PHP 7.4 or later, plus Divi, Extra, the Divi Builder plugin or Bloom. Delivered as a ZIP, ready to upload from your plugins screen.
No overpromising
No plugin makes you GDPR compliant on its own, and anyone telling you otherwise is selling you something. It depends on everything you do with the data. What this one does is cover one specific part properly: asking for consent before you collect, and being able to prove it afterwards.
