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 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 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.