Full disclosure, I have some rather strong feelings about telemetry on gitlab and the implementation process itself.<p>-----------------------<p>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.<p>To keep this issue from just going private, it (and some other relevant issues) have been archived: <a href="http://web.archive.org/web/20211012193943/https://gitlab.com/gitlab-org/gitlab/-/issues/335709" rel="nofollow">http://web.archive.org/web/20211012193943/https://gitlab.com...</a><p>There is atleast one more telemetry related issue that[2] has had their access limited after being mentioned in the feedback thread.<p>Also, I'd recommend checking out:<p>* the last telemetry attempt from 2019: <a href="https://gitlab.com/gitlab-com/www-gitlab-com/-/issues/5672" rel="nofollow">https://gitlab.com/gitlab-com/www-gitlab-com/-/issues/5672</a><p>* feedback from last time: <a href="https://gitlab.com/gitlab-com/support/support-team-meta/-/issues/1926#note_239240932" rel="nofollow">https://gitlab.com/gitlab-com/support/support-team-meta/-/is...</a> & <a href="https://gitlab.com/groups/gitlab-org/-/epics/2280" rel="nofollow">https://gitlab.com/groups/gitlab-org/-/epics/2280</a><p>* self-hosted instance telemetry(operational data section) that is already live and has a pretty severe dark pattern for opting out: <a href="https://about.gitlab.com/blog/2021/07/20/improved-billing-and-subscription-management/" rel="nofollow">https://about.gitlab.com/blog/2021/07/20/improved-billing-an...</a><p>[1] - <a href="https://news.ycombinator.com/item?id=28840685" rel="nofollow">https://news.ycombinator.com/item?id=28840685</a><p>[2] - Telemetry .com user interviews - User interviews - GDPR compliance is the standard and absolutely required - <a href="https://gitlab.com/gitlab-org/uxr_insights/-/issues/839" rel="nofollow">https://gitlab.com/gitlab-org/uxr_insights/-/issues/839</a>