• Plugin Author dFactory

    (@dfactory)


    Hi everyone,

    I’m Bartosz Arendt, founder of dFactory and a creator of the Cookie Notice plugin.
    Wanted to inform all of you that the reason for closing the plugin was NOT a security issue.

    The problem reported by the Plugin Review Team is as follows:

    “Your plugin claims 100% GDPR Compliance.

    Sadly, no plugin in and of itself can provide absolute legal compliance. While a plugin can certainly assist in automating the steps on a compliance journey, or allow people to develop a workflow to solve the situation, they cannot protect a site administrator from mistakes or lack of compliance, nor can they protect site users from incorrect or incomplete legal compliance on the part of the web site.”

    I’m sorry to say this, but I don’t understand it. Is this a reason to close a plugin used by 1 million websites? Is this a reason to expose so many people to stress?

    We’ll do as they suggest and update the plugin even though I’m 100% sure that the plugin can be GDPR compliant itself and the argumentation shows a deep misunderstanding of what GDPR is and how it can be implemented.

    • This topic was modified 5 years, 12 months ago by dFactory.
    • This topic was modified 5 years, 12 months ago by dFactory.
  • The topic ‘Why plugin closed? – answer’ is closed to new replies.