What about GDPR?

Hi, to be compliant with GDPR, all you need to do is add a note to your form’s footer informing new subscribers that by signing up, they consent to receive emails from you.

However, we understand why you would want to explicitly display a consent checkbox and this will be possible in today’s update.

This is now live ??

Do get in touch if you have any more questions.

Sounds, well, reads great, Brian. I will have a look.

Cheers, Frank

Hi Brian,

I re-installed and had a look. The whole interface is soooo intuitive — I am definitely a fan of Noptin (and I know what I am talking about, having tested many other newsletter plugins). The explicit GDPR hint/checkbox is well integrated and works fine (not that I expected anything else).

So I sent a first test newsletter and again: Compared to all other newsletter plugins I saw so far (a lot!) this works just fine: No checking of code necessary, the email editor works just fine with all the standards I expect from WordPress.

It works out of the box.

Chapeau!

Frank

PS. Two cents regarding GDPR:

The whole thing is still rather new — and complicated. One can still find tons of websites where the Cookie Consent gives users no other choice than to accept all cookies — which is not ok after the European Court decision from October 2019.

When it comes to a consent to store personal data of a person who suscribes to a newsletter I think that one is on the safe side if an explicit consent is requested.

The solution you provided (thanks again!) is sufficient for today and probably for tomorrow. Nevertheless I would prefer the consent as a “normal” field with a checkbox, followed by a label to edit (html should be possible to add the link) and the choice to make this a required field.

Such a solution would answer all future requests I can think of today. If someone came up with the idea that a privacy notice has to be agreed with explicitely (using a checkbox) this could be solved by standard fields then in Noptin.

Hi Frank,

I appreciate you taking the time to provide such detailed feedback. We already had plans to add a checkbox field (as well as a few other fields) in this update but we sort of ran out of time. Next week’s update will include those fields.