• MonkderVierte@lemmy.ml
    link
    fedilink
    English
    arrow-up
    17
    ·
    edit-2
    2 months ago

    Put a Facebook like button on your website, it’s loaded directly from Facebook servers. Now they can put a cookie on your computer with an identifier.

    Which is not allowed by GDPR btw, because they do that even if you don’t click them. There are plenty guides online, how to create your own, not tracking, facebook like button.

    • Dave@lemmy.nz
      link
      fedilink
      English
      arrow-up
      5
      ·
      2 months ago

      How does GDPR fit in to Google Analytics and personalised ads?

      I would have thought it went something like: random identifier: not linked to personal info, just a collection of browsing history for an unidentified person, not under GDPR as not personal info.

      Link to account: let them request deletion (or more specifically, delinking the info from your account is what Facebook lets you do), GDPR compliant.

      Both Google and Facebook run analytics software that tracks users. I presume letting people request deletion once it’s personally linked to them is probably what let’s them do it? But I don’t live in a GDPR country, so I don’t know a whole lot about it.

      • MonkderVierte@lemmy.ml
        link
        fedilink
        English
        arrow-up
        5
        ·
        2 months ago

        No, it should’ve been opt-in. But loophole with “vital interest” and politics being slow and surface-level like politics.