Why a CDN?

  • Resolved hal9099

    (@hal9099)


    9 months, 1 week ago

    The plugin could be GDPR compliant if it didn’t load the widget.js from the Elementor CDN. Why is that? It’s advertised as GDPR-compliant, but user consent is required just for this one file. So, data still has to be collected here; after all, nothing comes for free. Unfortunately, this renders the plugin completely unusable, just because someone in the marketing department decided to collect even the last data. Truly pathetic.

Viewing 2 replies - 1 through 2 (of 2 total)
  • Plugin Support Nema from Elementor

    (@masancvarak)

    8 months, 4 weeks ago

    Hi!

    Our CDN requirement is for the connection to elementor, ally is GDPR compliant under our ambrella in Elementor. Privacy-related requirements are addressed in our Data Processing Agreement. To ensure compliance with your privacy obligations, you must list us as a sub-processor in your privacy notice.

    Thread Starter hal9099

    (@hal9099)

    8 months, 2 weeks ago

    I don’t use Elementor. The plugin loads ja javascript from cdn.elementor.com/a11y/widget.js
    As far as I know, it’s not permitted in the EU to load scripts from outside the EU without the user’s prior active consent. Do I need a consent banner just for this plugin? Do you sell one? You should at least be familiar with the laws of the countries in which a product is sold. Besides, it’s completely unnecessary to solve it this way. It raises the suspicion that this was just implemented in such a way that users metadata can be intercepted and stored. This is precisely one of the reasons why such a practice is not permitted in the EU.

Viewing 2 replies - 1 through 2 (of 2 total)

The topic ‘Why a CDN?’ is closed to new replies.