Skip to content
This repository has been archived by the owner on Jun 24, 2022. It is now read-only.

Is your webpage GDPR compliant? #475

Closed
ghost opened this issue May 29, 2018 · 10 comments
Closed

Is your webpage GDPR compliant? #475

ghost opened this issue May 29, 2018 · 10 comments

Comments

@ghost
Copy link

ghost commented May 29, 2018

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

@ghost
Copy link
Author

ghost commented May 29, 2018

@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
Copy link
Author

ghost commented May 29, 2018

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
Copy link
Author

ghost commented May 29, 2018

@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
Copy link
Author

ghost commented May 29, 2018

@ghost
Copy link
Author

ghost commented May 30, 2018

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
Copy link
Contributor

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

@jonaharagon jonaharagon mentioned this issue Mar 30, 2019
2 tasks
@jonaharagon
Copy link
Contributor

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

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants
@jonaharagon @hugoncosta and others