-
Notifications
You must be signed in to change notification settings - Fork 463
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
EU-GDPR - Privacy by design and default #2449
Comments
I also think that when it comes to the data export, there should be a flag the user can opt into that indicates that the user agrees to export their data. If not set, then the data should not be exported. In order to mitigate the fact that this would cause significantly fewer devices and users to be exported over time, we could add a summary.xml to the export that includes:
Stats sites could then use this data to provide aggregate data graphs for the project. |
Sounds good. FTR: yet the consent to publish the personal stats data doesn't relieve the projects of GDPR's requirement to propagate a data erasure request to downstream data consumers. That effectively means you need to keep track of who you publish to. |
Remember that BOINC itself participates in this merry-go-round of exported and re-imported stats to drive pages like https://boinc.berkeley.edu/chart_list.php I think the data is aggregated by http://boinc.netsoft-online.com/e107_plugins/boinc/bp_home.php (another page which can't be accessed by https, it seems), which also provides the data for the 'Projects in which Richard Haselgrove is participating' panel on public pages like https://setiathome.berkeley.edu/show_user.php?userid=5509 - I'm not sure whether WCG participates in this process, so @TheAspens may not be so familiar with it. Provided netsoft-online updates its code and processes along the lines we've been discussing, proper GDPR compliance should follow automatically, but it might be wise to reach out to James Drews sooner rather than later, because his site is rather less independent from BOINC than some of the others. |
The good things is that as soon as we lock down our stats exports, everyone we missed will surely be in contact very soon. But yes, Willy and James are on our radar. Thanks. |
We (Oliver Tristan and I) discussed offline that the consent to stats exports, mentioned above, could be rolled into the Opt-in consent work/PR I am currently working on. The front-end is simply an additional privacy preference, similar to the show computers preference, where the user consents to having his/her stats exported. The back-end would use the new |
When creating a user account, show_hosts flag is false by default. Part of BOINC#2449
Is there something left here or this ticket can be closed? |
The main item for this ticket, setting |
@davidpanderson opened a ticket about host name and IP address. #2836
Hmm, maybe better ask volunteers instead. |
Closing this as 'Done' |
Let's use this issue for privacy-by-design-related topics that need to be addressed. I start with this one:
show_hosts
).send_email
to be problematic is this doesn't cause personal data to be shared.The text was updated successfully, but these errors were encountered: