Summary
The killpnpm website is a static informational site. It does not create accounts, run ads, sell personal information, or intentionally collect analytics from visitors.
The CLI runs locally on your machine. It inspects local process and filesystem metadata so you can find pnpm-related work, understand disk usage, and choose whether to stop processes or build cleanup plans.
Information the website handles
This site does not include first-party tracking scripts, login forms, newsletter forms, payment forms, or advertising pixels.
Hosting providers, browsers, npm, GitHub, and network infrastructure may process ordinary request data such as IP address, user agent, timestamps, and referrer information under their own policies.
Information the CLI handles
When you run killpnpm locally, it may read:
- process IDs, process groups, parent process relationships, command arguments, and working directories;
- local pnpm store, cache, and Library/XDG cache paths when diagnostic commands request them;
- file and directory sizes needed to report disk usage and cleanup plans.
The CLI is designed for local inspection and process control. It does not intentionally transmit that local diagnostic data to the killpnpm project, GitHub, npm, or any third-party service.
Commands that change local state
Some commands can send signals to local processes when you explicitly ask them to do so. Cleanup planning
is guarded: killpnpm clean --plan builds a plan and does not delete files by default.
Third-party links
The site links to GitHub and npm. Those services have separate privacy practices, account systems, logs, cookies, and terms.
Security reports and privacy questions
Please open a focused report through GitHub Issues. Do not post secrets, private logs, tokens, private repository paths, or sensitive process output in a public issue.
Changes
This policy may change as the project evolves. Material updates should be reflected in the repository so users can inspect the change history.