3 ms·
Looks not valid in terms of GDPR. What are my rights and in which paragraph are those rights stated? How long is data stored? Which log files of my visit arise
by a3w 6y ago
Looks not valid in terms of GDPR. What are my rights and in which paragraph are those rights stated? How long is data stored? Which log files of my visit arise (just my IP and date of visit? Who hosts that site, if it's not a machine you physically own? Do they store that data? More data, like browser or OS version?)
You are usually allowed to use that data for debugging and intrusion detection etc. but you still need to mention it, if that data is collected, even by a third party you hired.
- jen729w 6y agoMate, it’s a website. You come, you read it, you leave. Next you’ll want a GDPR policy for your library book. If that privacy policy doesn’t make it screamingly obvious that I’m not tracking you in any way then holy moly I don’t know what to do.
- m463 6y agoYou could add a clause: "If your email address contains the string "a3w" it will be immediately forgotten." :) I think if[1] I ever had a website, and if[2] I had advertising I would choose one advertiser per month, display a static image at the top of each page, and clicking on it would take you to a static page on an advertiser's website. and it would have a privacy policy like your good example [1] big if [2] bigger if
- p_l 6y agoThere's not much to change there to actually make it "more GDPR-like". It already does what GDPR wants to cause, i.e. you don't gather Personal Data, with the only exception being the email, and given that it's not operating as an organisation it's probably in the clear. Maaaaaybeee you might want to strip last octet in IP number from logs, but that's pretty much it. Complex GDPR policies are only necessary when you want to store and process Personal Data.
- jen729w 6y ago> Maaaaaybeee you might want to strip last octet in IP number from logs, but that's pretty much it. It’s hosted on Netlify, so I don’t even have logs. :-)
- p_l 6y agoThen you point to netlify as responsible party and I guess you might be done ;) GDPR compliance is overblown, when the simplest way to be compliant is to "just don't store nor process personal data"