TRACEHUSH / METHODOLOGY
A careful way to hold uncertainty.
Tracehush organizes context around a possible sensor, camera, vehicle, or report. It makes the reasoning visible without claiming a remote system can be detected or a person can be identified from incomplete evidence.
01 / Inputs
Six context categories, kept distinct.
- Location and proximity: whether the setting and distance provide usable context.
- Time: how recent, sustained, and precisely bounded the reported event is.
- Vehicle relationship: whether the vehicle details fit the reported setting and signal.
- Sensor evidence: what was directly observed, suspected, or inferred.
- Source quality: whether the source is a log, direct observation, public record, report, or online claim, and how verifiable it is.
- Corroboration: whether independent sources agree, provide no support, or conflict.
Two outputs, not one verdict.
The exposure estimate is limited, plausible, or elevated. Confidence in that readout is low, medium, or high.
Unknowns, suspected signals, approximate timing, weak sources, and conflicting accounts limit the result rather than disappearing inside a single score.
What the method cannot tell you.
A limited result does not prove that no system exists. An elevated result does not identify a particular system, operator, person, or legal violation. The check uses self-reported context, and the meaning of privacy, recording, property, workplace, transport, and evidence rules depends on the jurisdiction and facts.
02 / Use it responsibly
Preserve options before escalating.
Keep original records unchanged, review only the controls you own or are authorized to manage, and use official channels for follow-up. For legal interpretation or evidence handling, seek qualified local advice. Read the FAQ for the short version of the confidence, registry, and moderation boundaries. Read the retention policy for the data windows and account-deletion outcomes.