GDPR Compliance

  • Resolved rapportdesign

    (@rapportdesign)


    5 years, 11 months ago

    I’m currently working through a list of plugins that we use, trying to establish the following.

    1. What cookie files (inc. local storage etc) containing personal data are being set by the plugin?
    2. Do any settings need to be changed within the plugin, to make it GDPR Compliant?
    3. Are we adding all the relevant information in relation to the plugin, to our websites privacy policy?

    It’s my understanding that…

    • Classic Editor doesn’t set any cookie files (inc. local storage etc) containing personal data.
    • There are no settings within the Classic Editor plugin, which need to be changed for GDPR Compliance.
    • There’s no information that needs to be included in our websites privacy policy, in relation to the Classic Editor plugin?

    Please, could you confirm that this is correct?

Viewing 2 replies - 1 through 2 (of 2 total)
  • Moderator Marius L. J.

    (@clorith)

    The Classic Editor plugin is intended for back-end use, and as such has no direct GDPR implication.

    That said, the plugin does not store any information about site visitors, so you do not need to include any notion of it in your privacy policy by default, exceptions may apply depending on what other plugins or themes do with the plugin active, but that would not be directly related to this plugin.

    That’s great… Thanks for the update!

    I was also rapportdesign who created the post.
    I didn’t know at that point, duplicate accounts weren’t allowed.

    • This reply was modified 5 years, 10 months ago by kwebdesign.
Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘GDPR Compliance’ is closed to new replies.