3 ms·
"Unfortunately, that tool only gives me all of the data I put on there myself. So nothing I didn't already have. After all, why would I leave my only copy of a
by 3xblah 7y ago
"Unfortunately, that tool only gives me all of the data I put on there myself. So nothing I didn't already have. After all, why would I leave my only copy of a photo on Facebook? So no, this tool does not allow me to exercise my GDPR rights."
When the author is visiting a website that hosts a "Like" button, the author's web browser makes a request to Facebook's (httpd) servers for the button image. He then sends data to Facebook in HTTP headers. If he uses third party DNS service, it is possible he could also be sending part of his IP address, i.e., location data, to Facebook's (authoritative DNS) servers in the DNS request packet. For example, see https://developers.google.com/speed/public-dns/docs/ecs https://developers.google.com/speed/public-dns/docs/ecs
Did the GDPR drafters consider that data?
- atoav 7y agoPersonal data is anything that can be linked to your person in the context of the GDPR. Doesn’t matter if they store your IP or the movements of your mousepointer or your user agent, it is all personal data, unless they store it in a way that can’t link back to you (e.g. just counting the number of useragents of each kind). And the author is right. There is with high certainty a lot of data about you that you didn’t explicitly upload and I don’t see why facebook shouldn’t give it to him. I see why they don’t want to give it to him (because it would show the extent of their data collection), but exactly for that reason it is even more important that they comply.