QuietStewardship
Don’t trust us — check

Verify it yourself

The whole promise is that your machine’s diagnostics never leave your machine. That’s not something you should take on faith. Here are two ways to confirm it — one for anyone, one for the technically inclined.

The airplane-mode test (anyone can do this)

If the dashboard keeps showing your machine’s data after you disconnect from the internet, then the data is obviously coming from your own computer — not from us.

  1. 1Install and start the local agent, then open the dashboard. You'll see your live CPU, memory, disk, and recent activity.
  2. 2Turn off Wi-Fi / unplug the network (or switch on airplane mode). The badge below will flip to “Offline”.
  3. 3Watch the dashboard keep updating. With no internet, the only place that data can be coming from is your own machine.

Why this works: a web page can’t reach a server that isn’t there. Offline, the dashboard has no way to send anything anywhere — yet it still shows your data, because it’s reading the agent on localhost (your own computer).

For the technically inclined

1. Read our Content-Security-Policy

In DevTools → Network, click the page request and read the Content-Security-Policy response header. Its connect-src lists every origin this site is permitted to talk to:

connect-src 'self'
            https://localhost:*  https://127.0.0.1:*   (your machine's agent — host data)
            http://localhost:*   http://127.0.0.1:*
            https://us.i.posthog.com  https://us-assets.i.posthog.com   (anonymous site analytics)

The browser enforces this list. The only destinations are your own loopback (where your host diagnostics are read — and they are never put into an analytics event) and our anonymous website analytics (PostHog: page views, downloads, feature clicks). There is no advertising or cross-site tracking origin, and you can opt out of analytics. See the analytics disclosure.

2. Watch the network traffic

Keep the DevTools Network tab open while the dashboard runs. Every request for your machine’s data goes to https://localhost:47600(or your configured port) and nowhere else. The only other requests are small anonymous analytics pings (page view, download) to PostHog — they carry no host data, and stop entirely if you opt out.

3. Inspect the agent itself

The agent binds to loopback only and never opens an outbound connection. Confirm it:

# the agent listens only on 127.0.0.1 — never 0.0.0.0
netstat -ano | findstr 47600        # Windows
lsof -nP -iTCP:47600 -sTCP:LISTEN   # macOS / Linux

# block it from the internet in your firewall — it keeps working,
# because it never needed to reach out in the first place.

4. Read the source

The agent is deliberately small and single-purpose. We intend to publish the source so its behaviour is fully auditable — the ultimate verification.

Want even less running? Use the agent in on-demand mode— it only runs while you’re looking at your data, and isn’t a background service at all. See the agent data-handling disclosure and security & trust pages.