*.wp.com handle (Jetpack)

  • Resolved Nicola @ironicmoka Paroldo

    (@photoironic)


    4 years, 4 months ago

    Hi there,
    just to let you know that handling Jetpack is missing some urls from their image CDN: *.wp.com urls are listed in the “Embeds of external URLs to be checked” section. Maybe that’s because wp.com it could be used by other services but it could be useful to have the option to manually add them all to the Jetpack service.

Viewing 1 replies (of 1 total)
  • Plugin Author devowl.io GmbH

    (@devowl)

    4 years, 4 months ago

    Hi @photoironic,

    I’m sorry for the delay in responding. Unfortunately, your request has been lost.

    We must point out that the following statements do not constitute legal advice. Therefore, I can only give you evaluations from our intensive experience with the EU legal regulations in practice and a technical assessment of the situation.

    A CDN transmits data from a third-party server that the website visitor cannot expect. We are of the legal opinion that CDN third-party servers are to be treated like web hosts if they certainly do not collect data about the visitor for marketing purposes. This means you have to sign a data processing agreement with the operator and explain it in your privacy policy. We do not consider consent via the cookie banner necessary (so no content blocker either). Consequently, there is no service template for this.

    Best regards,

    Jan

Viewing 1 replies (of 1 total)

The topic ‘*.wp.com handle (Jetpack)’ is closed to new replies.