Correction & Takedown Procedure
Reports and teardowns are generated from public data under a published, versioned policy. Public data can be delayed, incomplete, or wrong — so there is a standing procedure for reporting errors and requesting removal. This page describes that procedure. It is not itself legal advice.
What this covers
This procedure applies to any content this site publishes: shared report permalinks, the sample report, teardowns, and methodology descriptions.
It covers two kinds of requests: a correction request (a specific claim is factually wrong) and a takedown request (published content should be removed, for example because it identifies a person or was shared without authority).
How to submit a request
A request is fastest to process when it includes:
- The URL of the page or report in question (report permalinks include a report id).
- The specific statement or data point being disputed, quoted or clearly identified.
- For corrections: the evidence — a transaction hash, contract address, or other public source that contradicts the published claim.
- For takedowns: the reason removal is requested and, where relevant, the basis for claiming authority over the address or content.
What happens next
Requests are acknowledged within 3 business days. Corrections are reviewed against the same public sources the engine reads; the review checks the disputed claim, not the requester’s identity.
A verified factual error is corrected in place and the affected page is annotated with what changed and when. Where the error came from an upstream data source, the correction notes that provenance.
A dispute that cannot be resolved from public data is disclosed rather than hidden: the disputed claim is annotated as contested. Content is not silently edited.
Takedown outcomes
A report permalink is removed when the request comes with reasonable evidence of authority over the analyzed address, or when the page links a wallet to an identifiable person.
Teardown content about protocols and publicly marketed products is treated as commentary on public conduct; it is corrected where wrong, annotated where disputed, and removed where the legal basis for removal is established.
Every removal or refusal is logged internally with its reason. A refusal states the reason to the requester.
Timelines
Acknowledgement: within 3 business days. Resolution of a straightforward correction: within 7 business days of acknowledgement. Complex disputes can take longer; the requester is told when that is the case.
Where to send requests
Correction and takedown requests, with the details above: hello@checkup.earn-defi.com