Hi there,
Thanks for your feedback and for using our plugin!
It strikes me that leaving the notice/accept button visible util the user ‘ACCEPT’s it, is going to annoy people – it may cover stuff they want to read – it may seem like nagging??
It will likely annoy users but that’s what we need to do in order to comply with GDPR.
A Reject button means setting a (temporary) cookie to indicate a user has declined cookies tho – some people think that’s not allowed?
Our understanding is that this is not allowed. No cookie should be stored on users computers unless they specifically allow it.
Disclaimer: we strongly recommend you to seek an independent legal advice on the implementation of GDPR.
Sorry we can’t be of more help on this.
Moove Agency team.
I also would like to see an optional decline button or option.
I think it is fine to store functional cookies without consent as long as you mention it in your privacy policy.
I’ve read-up a fair bit on this as well as looking at what other sites/plugins/tools are doing and I’d say you CAN have a Reject Button and you ARE allowed to set a cookie to ‘remember’ that choice so long as you make it clear you’re doing that (and why – e.g. to stop bugging them to Accept)
The ‘user has rejected cookies’ cookie would be an ‘essential’ cookie – one required for the site to function – it’s not ‘tracking’ them and only stores their desire to NOT track them (a core concept in the GDPR!)
A Reject option is a better solution than permanently offering an Accept button – that seems like annoying people in the hope they’ll Accept just to get rid of the box…
End of the day we need practical solutions – a permanent question, massive Privacy Policy and/or lists of 100s of partner/cookies isn’t helpful to anyone, however ‘compliant’ it might be.
