Corrections, source questions, and privacy notes
TRACED is maintained by Jonathan R. Reed as a public breach archive and privacy-first password exposure checker. If a case file needs a correction, a source should be clarified, or a privacy concern needs review, send the note through Jonathan's primary site.
Do not send passwords, private keys, personal documents, or breach samples through a contact form. TRACED does not need sensitive material to answer archive corrections or source questions.
Useful correction notes include the case name, the public source that should be checked, and a short description of what looks inaccurate. For privacy questions, include only the minimum context needed to understand the concern.
TRACED does not investigate private account ownership, remove records from Have I Been Pwned, or accept raw breached data. The archive points people toward public context and safer credential habits without collecting more information.
If a source link changes, include the original case URL, the replacement public reference, and the reason the archive should be updated. If the issue is about a password check, describe the browser behavior without sending the password, hash, or any private account identifier.
Good archive feedback separates public source corrections from personal support requests. TRACED can improve a case title, date, data-class label, source reference, or explanatory note when the public record supports the change. It cannot confirm whether an individual person was included in a breach or remove data from the original HIBP dataset.
For responsible notes about the site itself, include the page URL, browser, device, and the exact behavior you saw. Reports about broken navigation, inaccessible controls, incorrect schema, missing context, or outdated external references help keep the archive readable and useful without asking visitors for sensitive evidence.