Don't trust us. Audit us.
Every claim we make, and exactly how to check it yourself.
Software that hooks your keyboard should be treated with suspicion — we'd grind it through an analyzer too. So instead of asking you to trust our word, here is each claim we make and the fastest way to test it on your own machine, with your own tools. If any test on this page fails, one of two things is broken: our software or our honesty. Either one is a bug — report it.
Claim 1 — It never talks to the network
We say: Couchwarden contains no networking code at all. Not "we don't collect" — the program is incapable of transmitting.
Check it:
- Run any packet capture (Wireshark, or your firewall's per-app view) for as long as you like. You will see zero connections from Couchwarden — at install, at launch, in use, ever.
- Point a firewall rule at it and set it to alert. It will never fire.
- Going deeper? Inspect the program itself: there are no socket, HTTP, or DNS capabilities to find.
Claim 2 — The log records decisions, never what you type
We say: Couchwarden keeps a plain-text activity log so you can hold it accountable — every suppression, every toggle, timestamped, with its reason. What that log never contains: which keys you pressed, what you typed, or anything else you produced.
Check it: open couch_guard.log in Notepad. It's
next to the program, unencrypted, written in plain English. Read it after a
day of use. That file is the same one we use to debug — there is no second,
hidden log.
Claim 3 — Everything it knows lives in one folder, in plain text
We say: settings in config.json, activity in the
log — both human-readable, both next to the program, both yours to edit or
delete. No hidden state, no cloud copy, no account.
Check it: watch it with Process Monitor (free, from Microsoft's own Sysinternals). Filter on the process and observe what it reads and writes.
Claim 4 — This website practices what the software preaches
We say: no cookies, no analytics, no trackers, no third-party requests. A static page has no business phoning home either.
Check it: open your browser's developer tools (F12 → Network) and reload this page. Count the third-party requests: zero.
Why we operate this way
A tool whose job is deciding which of your keystrokes count must be the most accountable program on your machine — that responsibility is the product. So our house rule is simple: our software logs its own decisions and never your content. The log file is our confession, kept where you can read it. When your audit and our log tell the same story, that's not luck. That's the design.