-
Notifications
You must be signed in to change notification settings - Fork 453
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
GDPR compliance #2571
Comments
Hi @idleberg , thank you for reaching out! Atom-Beautify is currently using I see your points on how this can be improved and would be happy to accept a Pull Request improving this area. To help you or others write such a Pull Request, here are links to applicable code which would be useful:
Thanks for your interest and supporting this open source project! |
Situs Judi Togel Terpercaya Dan Terlengkap 2022 GASKEN88 DAFTAR Bandar Togel Terpercaya Padakali ini kami akan membahas sebuah bandar togel terpercaya dan terbaik di indonesia yang menurut kami terbaik dan terbesar di asia karena dengan semua bandar togel terpercaya yang akan kami bahas kali ini adalah Bandar Togel Hadiah 4d 10 Juta terbesar di indonesia dengan semua reputasi yang kami rekomendasikan adalah salah satu situs togel online terpercaya yang terbaik di indonesia. |
This plugin is not GDPR-compliant and the same might be true for other privacy regulations, e.g. the CCPA. I will continue to use the GDPR as an umbrella term for similar regulations.
At the time of this writing, the authors assume that consent is given through the consent for GitHub's
metric
package. This is problematic in many ways. Let's take a look at these simple definitions:I think these definitions are easy enough to understand for non-lawyers and it should be clear that all of these are violated. When accepted, each of these definitions is fulfilled between GitHub and the user. However, GitHub cannot be made liable for everyone else jumping the train – they don't know anything about what your code does, why would they vouch for it? Also, GitHub sends user data to its own servers, while this package sends it to a different party: Google Analytics.
Here's a simple example to illustrate the problem: A user installs Atom on January 1st, on the first startup he accepts the privacy policy between him/her and GitHub Inc. Nine months later, the user installs
atom-beautify
. GitHub's policy is specific to the data collection of themetrics
package, the user is uninformed about the data collection ofatom-beautify
— because GitHub's privacy policy is unambiguous that it applies to the collection by themetrics
package.It should be enough, if this package pops up a notification with "Accept" / "Reject" buttons and a link to your privacy policy. Or better, replicate the consent page used by the
metrics
package. However, since I'm not a lawyer, you might want to read about this online. There are plenty of free resources that provide guidance, including here on GitHub.The text was updated successfully, but these errors were encountered: