Manpages should be about commands, flags, and nothing else. But too often, browsing a manpage leaks details — telemetry, usage logs, fingerprints of who searched for what and when. This data is collected quietly, without need or reason. It’s time to cut that out. Privacy by default is not a luxury in developer tools. It’s the baseline.
Privacy by default means no hidden network calls. No third-party pings. No recording keystrokes to "improve the experience."It means a manpage request lives and dies locally on your machine. It carries zero context to anyone else. You never have to toggle a flag to "opt out,"because there’s nothing to opt out from. You don’t wonder if you’ve missed a switch in the settings. The tool ships with nothing to track.
A privacy‑first manpage system ensures your documentation workflow cannot be turned into a data stream. This eliminates the risk of metadata aggregation, profiling, or compliance headaches. The promise is simple: manpages exist to inform, not to spy. That’s the difference between software you can trust and software that asks you to gamble with your users’ and your own information.