Is your webpage GDPR compliant? #475

Closed
opened 2018-05-29 07:27:31 +00:00 by ghost · 8 comments
ghost commented 2018-05-29 07:27:31 +00:00 (Migrated from github.com)

I think you need to write Privacy Policy because you are collecting data(piwik and Cloudflare Analytics).

I think you need to write Privacy Policy because you are collecting data(piwik and Cloudflare Analytics).
ghost commented 2018-05-29 07:28:23 +00:00 (Migrated from github.com)
https://www.hallaminternet.com/how-to-make-your-website-gdpr-compliant/ https://getpublii.com/blog/website-gdpr-compliant.html
ghost commented 2018-05-29 07:59:37 +00:00 (Migrated from github.com)

@CHEF-KOCH Interesting. But I found a webpage - not a nodejs "tool" - that create GDPR privacy policy text a month ago. Forgot a URL though.

@CHEF-KOCH Interesting. But I found a webpage - not a nodejs "tool" - that create GDPR privacy policy text a month ago. Forgot a URL though.
ghost commented 2018-05-29 13:11:47 +00:00 (Migrated from github.com)

We're not giving any data to third parties (at least as far as we know, @privacytoolsIO?), so a page that says we're using Piwik and an option to opt out of Piwik should be enough I think.

We're not giving any data to third parties (at least as far as *we* know, @privacytoolsIO?), so a page that says we're using Piwik and an option to opt out of Piwik should be enough I think.
ghost commented 2018-05-29 23:44:21 +00:00 (Migrated from github.com)

@Shifterovich IP address is a privacy data, read the law. Also the website is proxied by Cloudflare so you should mention piwik, cloudflare and what data(ip, ua, time, uri) you log.

@Shifterovich IP address is a privacy data, read the law. Also the website is proxied by Cloudflare so you should mention piwik, cloudflare and what data(ip, ua, time, uri) you log.
ghost commented 2018-05-29 23:46:02 +00:00 (Migrated from github.com)
https://github.com/privacytoolsIO/privacytools.io/issues/374
ghost commented 2018-05-30 13:17:48 +00:00 (Migrated from github.com)

IP address is a privacy data, read the law.

So what? Even e-shops don't have to care about giving customer data to delivery companies due to consent to that being implied by making the order. Giving the data to third parties that are not vital to the order is what you have to tell your customers about.

What are we doing with the IP address that we need to tell customer about? Mere storing with limited access to it is fine.

> IP address is a privacy data, read the law. So what? Even e-shops don't have to care about giving customer data to delivery companies due to consent to that being implied by making the order. Giving the data to third parties that are not vital to the order is what you have to tell your customers about. What are we doing with the IP address that we need to tell customer about? Mere storing with limited access to it is fine.
hugoncosta commented 2018-06-04 15:00:19 +00:00 (Migrated from github.com)

But I wonder why you need to collect hardware for something which should 'only' protect something against DOS attacks.

My guess is they're getting ready to do the whole "solve this math puzzle to pass the captcha" for those that don't want to do the pictures. It's actually a pretty clever deal for them. Right now, we're helping classify images for their ever growing machine learning library. Soon, we'll be able to opt to either keep classifying them (which btw has changed in the last couple of weeks, they're focused on classifying image layers that completly obliterate their algos) or we'll lend our processing power for a couple secs to train the algos. Either way, they're collecting it without our explicit consent. I believe GDPR isn't just anti-targeted-ads, it's against hoarding data just cuz

>But I wonder why you need to collect hardware for something which should 'only' protect something against DOS attacks. My guess is they're getting ready to do the whole "solve this math puzzle to pass the captcha" for those that don't want to do the pictures. It's actually a pretty clever deal for them. Right now, we're helping classify images for their ever growing machine learning library. Soon, we'll be able to opt to either keep classifying them (which btw has changed in the last couple of weeks, they're focused on classifying image layers that completly obliterate their algos) or we'll lend our processing power for a couple secs to train the algos. Either way, they're collecting it without our explicit consent. I believe GDPR isn't just anti-targeted-ads, it's against hoarding data just cuz

After #795 I believe this issue can be closed, unless someone has a further concern.

After #795 I believe this issue can be closed, unless someone has a further concern.
This repo is archived. You cannot comment on issues.
No Label
1 Participants
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: privacyguides/privacytools.io#475
No description provided.