Hacktoberfest 2026：维护者为十月标记出来的 issue，仍然开放、适合新手。 浏览 Hacktoberfest issue

Telemetry: a persistent machine_id makes the data pseudonymous, and default-on collection lacks prior consent for EU users (GDPR / ePrivacy)

未关闭
  • 哪里不对？
#1,868 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
5/5
预计耗时
一周以上
新手友好度
25/100
Issue 类型
功能
描述清晰度
基本清楚
活跃度
活跃
技术栈
markdown, sql
领域
backend, documentation, security

调研方向

Start by reading TELEMETRY.md, the telemetry command and CLI notice, and telemetry-worker/migrations/0001_init.sql; trace where machine_id is created, stored, sent, and retained. Then compare the suggested opt-in, identifier rotation or removal, retention, and wording changes. Done means the project has chosen and implemented a coherent approach, with documentation and user-facing messages matching its behavior.

由索引模型根据 Issue 内容生成。

描述

Summary

Telemetry is described as anonymous, but every payload carries machine_id, a random UUID stored in ~/.codegraph/telemetry.json that never expires. Because it links all events from the same machine over time, the data is pseudonymous rather than anonymous. Under the GDPR, pseudonymous data is still personal data. Combined with the default-on setting, I believe the current design is unlikely to be compliant for users in the EU, and I'd like to suggest some changes.

Context: CodeGraph 1.6.0 on Windows 11 (npm install). I never ran the interactive installer, so no toggle was shown. The one-line notice appeared during my first codegraph index, in the same run as the first POST, so there was no opportunity to refuse before data left the machine.

Details

  1. Pseudonymous, not anonymous. A stable identifier that lets you recognise the same machine across sends is pseudonymisation (GDPR Art. 4(5), Recital 26), and the data stays within the scope of the GDPR. The words "anonymous usage stats" in TELEMETRY.md, the CLI notice and the telemetry command output are therefore misleading for EU users. The client IP is also exposed to the hosting provider when the request is made, even though the worker itself never reads it.

  2. Consent before storing an identifier on the device. Writing an identifier to the user's machine and reading it back for analytics falls under Art. 5(3) of the ePrivacy Directive (in France, Article 82 of the Loi Informatique et Libertés). It requires prior consent unless the storage is strictly necessary for the service the user asked for, and usage statistics are not. The EDPB Guidelines 2/2023 on the technical scope of Art. 5(3) make clear this is not limited to browser cookies. A default-on toggle, or a notice printed when the first send happens, is not valid consent: consent must be a clear affirmative act (CJEU C-673/17, Planet49).

  3. Retention. Raw events are purged after 90 days, but according to telemetry-worker/migrations/0001_init.sql, machine_days and machine_first_seen keep the machine ID and its active days with no limit. For comparison, the French regulator (CNIL) only exempts audience measurement from consent when the identifier lasts at most 13 months and the data is kept at most 25 months. The current design does not meet those conditions either.

Suggestions

  • Make telemetry opt-in, or at least keep it off in non-interactive runs until the user has explicitly made a choice.
  • If a persistent ID is kept, rotate it (for example every 13 months at most) and put a retention limit on machine_days and machine_first_seen. Alternatively, drop the persistent ID in favour of a per-day random value.
  • Describe the data as pseudonymous in TELEMETRY.md, the notice and the CLI messages. Also name the data controller and give a contact for access and erasure requests (a deletion request can only be matched through the machine ID).

I'm not a lawyer, and I'm happy to be corrected on any of these points. Thanks for the detailed TELEMETRY.md and for publishing the worker code, which made all of this easy to check.

主要语言
C
星标
73.2k
派生
4.7k
平均合并
7 小时 49 分钟
30 天内合并 PR
629

环境准备

这个项目没有提供开发容器、Dockerfile 或贡献指南，环境需要你自己搭建：先看它的 README，通用步骤见我们的新手贡献指南。

从这里开始

  1. 先读完整个 Issue，再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库，在一个分支上完成修改。
  4. 提交 Pull Request，并在描述里引用这个 Issue 编号。

colbymchenry/codegraph 的其他 Issue

查看 colbymchenry/codegraph 的全部 Issue

相似的 Issue

更多 C Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。