Comment by jen729w

4 years ago

Mate, 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.

4 comments

jen729w

Reply
m463  4 years ago

You 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  4 years ago

There'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  4 years 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  4 years ago

      Then 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"