'No telemetry' is testable — here's how we'd prove it on your machine

The verification path

1. Baseline the process: launch the tool, note PID. netstat -ano | findstr <pid> — a local-first app shows no non-loopback endpoints at all across a session.
2. Leave it running through its features: scan, report, settings, export-preview. Every feature that needs network is a feature doing more than advertised.
3. Optional heavyweight: pktmon start -c for a timed session, then convert the ETL and filter by process name. Total silence across a full exercise cycle is the evidence level that convinces auditors.

Why it matters enough to be testable

Marketing “privacy” claims are two-a-penny; per-permission manifests that are unable to make a call are a structural argument. On Windows the presence of a WinINet/WinHTTP stack in the binary is easy to eyeball — both the manifest and the import table tell the same consistent story when the claim is true. When it's false, one netstat row ends the conversation.

ProofTune ProjectEngineering notes — every claim here names the bytes a real tool touches. Verify first, install second.