Privacy / verification

What is in a diagnostic report, what is not, and how we prove it

“No telemetry” is easy to say. A support report you choose to send is the one time data leaves your machine — so it is the place where the claim has to be checkable rather than trusted.

It quotes a frozen snapshot

The report is assembled from one snapshot taken at the moment you press the button. It deliberately never reaches back into live state, because live state may have changed between the moment you saw the problem and the moment you reported it. Everything in the report is a plain value, and the whole builder is a pure function.

What it contains

What is removed on the way out

Why a pure function matters

Because the redaction becomes provable. The report builder takes plain values and returns text; it needs no display, no window and no network. That is what lets a self-test assert the redaction contract on a machine with no monitor attached — otherwise the only way to test it would be to have the very hardware whose serial you are trying not to leak.

Honest limits

Related