Corrections
Abstract
When vet402 publishes something about an address and gets it wrong, the correction is published here with what was wrong and what changed. We never silently edit or silently remove an entry to make ourselves look better. What we will do is honor verified data-protection requests: an entry can be restricted or annotated — see 2.4 below — but the log is never quietly rewritten as if a mistake had not happened.
1.Issued corrections
Empty log
No corrections have been issued yet.
This is the count, not a claim about our accuracy: the product is in closed beta and the volume of published verdicts about named addresses is still small. The page exists before the first entry for the same reason the accuracy ledger published its methodology before it had numbers — a log that appears only once there is something flattering to put in it is not a log.
2.What lands here, and what does not
A fact we got wrong, and fixed. If we published something about an address that was not true — a mis-read signal, a mis-attributed wallet, a stale input treated as current — the correction and the re-score are logged, whether the challenge came from a customer or from a stranger.
Not: a score that moved on its own. Scores change constantly as on-chain behavior changes. That is the instrument working, not a correction, and logging it would bury the entries that matter.
Not: a disagreement we did not concede. A score is our opinion and sometimes we will disagree with the person challenging it. Those are answered directly, in writing, and are not corrections. The route stays open either way.
Data-protection requests are honored, not logged away. If an entry names an address that is personal data about you, you can ask us to erase it or to restrict it, and we weigh each request individually — the grounds and the process are in the privacy policy. Where a request is granted in part, the entry is restricted or annotated in place rather than silently deleted: the log keeps the fact that a correction was issued, without continuing to publish data we no longer have grounds to publish. Every entry here states what we verified, in factual terms and with its date; the log does not brand anyone a fraudster.
3.If you think a score about you is wrong
You do not need an account, an API key, a payment, or a lawyer to challenge a score. Two routes, both free: prove control of the address by signing our canonical message and posting it to /api/v1/payees/verify, or write to support@vet402.com with the address and what you think is wrong. One person reads that inbox and will acknowledge within 5 business days. Section 8 of the Terms of Service is the full text of both.