Skip to content

Current telemetry implementation violates GDPR #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

Closed
runiq opened this issue Mar 24, 2021 · 1 comment
Closed

Current telemetry implementation violates GDPR #463

runiq opened this issue Mar 24, 2021 · 1 comment

Comments

@runiq
Copy link

runiq commented Mar 24, 2021

Hey,

I was made aware that this langserver uses telemetry with a unique identifier (log/token). I don't mind that much, but the way it's written now (always on, not mentioned in the Readme, or upon starting the langserver), it's a GDPR violation.

Which means I'm not allowed to use the langserver at work. Which is a shame because I like it :(

I understand telemetry uses a lot of its usefulness if it's opt-in by default, so I'm not suggesting to make it opt-in—but could you at least clearly, obviously mention, preferably in multiple places, that you log telemetry data?

  • In the readme
  • Upon installation, right at the end, so it's in the face of the user
  • Upon startup (maybe even every time, until the user sets a config like i_know_god_stop_yelling_about_telemetry)
@runiq
Copy link
Author

runiq commented Mar 24, 2021

Ninja'd by #462 :) I'll close this one.

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

No branches or pull requests

1 participant