Full disclosure, I have some rather strong feelings about telemetry on gitlab and the implementation process itself.

-----------------------

I originally posted a different issue labeled "Pseudonymization MVC Rollout Plan"[1] but that issue went private rather quickly after appearing here. Sadly it wasn't archived.

To keep this issue from just going private, it (and some other relevant issues) have been archived: http://web.archive.org/web/20211012193943/https://gitlab.com...

There is atleast one more telemetry related issue that[2] has had their access limited after being mentioned in the feedback thread.

Also, I'd recommend checking out:

* the last telemetry attempt from 2019: https://gitlab.com/gitlab-com/www-gitlab-com/-/issues/5672

* feedback from last time: https://gitlab.com/gitlab-com/support/support-team-meta/-/is... & https://gitlab.com/groups/gitlab-org/-/epics/2280

* self-hosted instance telemetry(operational data section) that is already live and has a pretty severe dark pattern for opting out: https://about.gitlab.com/blog/2021/07/20/improved-billing-an...

[1] - https://news.ycombinator.com/item?id=28840685

[2] - Telemetry .com user interviews - User interviews - GDPR compliance is the standard and absolutely required - https://gitlab.com/gitlab-org/uxr_insights/-/issues/839