I tried doing that on the tool-specific detail page, but they’re broad categories, e.g. “Device, Environment, Usage” for Next.js. Do you think that’s sufficient?
I saw (after posting) that all the tool specific pages do link specifically to each project's documentation about what telemetry data is collected.
Those categories feel a little too broad to me, especially without clearly stated definitions. "Environment" in particular made me second guess if dev tools were leaking secrets. But, thankfully, the projects I looked at were very clear that they don't collect anything from the shell environments.
Maybe all it really needs is some detail for what's in the category. "Device (OS, core count, available memory)" or "Usage (command, plugins, timing)"?
I reviewed the source-code before adding them to the site. I can’t say for sure IP addresses aren’t stored server-side, so we have to trust them that they don’t, but most tools do find creative ways to get some kind of unique and persistent IDs. For example, Astro computes a hash for the git repository remote URL, and Storybook computes an ID by hashing the first commit hash in the repo.
The intent of the GDPR is to prevent the act of non-consensual tracking and not some specific technical method of achieving that, so even a deterministic ID generation method that doesn't rely on any client-side storage would still be in scope, as would a hypothetical crystal ball if it worked better than random chance at reidentifying a unique user.
The currently available information is all from browsing documentation and scanning source code. Some people suggested looking into JetBrains IDEs, which isn’t open-source, and thus would require packet sniffing.
I did browse VS Code’s source code and I can’t recall seeing anything other than straightforward, albeit verbose, telemetry. When I find the time, I’ll reiterate on clarity! I’ll try to be more thorough, too, if time lets me. I want to verify everything before it goes online, which is time-consuming — an already scarce resource.