EDITORIAL POLICY

Corrections Policy

When we get something wrong, we say so — in the open, on the page, with a timestamp. Here's exactly how that works.

What counts as a correction

A correction fixes a factual error — a wrong fee, an outdated feature, a misattributed quote, a stale price or statistic. A clarification adds context to something that was accurate but confusing or incomplete. An update reflects something that changed after publication — an exchange raised its fees, a wallet shipped new firmware — and isn't a correction of our original reporting.

How we mark corrections

Every corrected article carries a visible note directly below the headline or at the point of the fix: "Correction (date): [what changed and why]." We never silently edit a factual claim after publication. Typos, dead links, and formatting fixes are made without a note; anything that changes a claim, number, ranking, or recommendation gets one.

Review re-verification cadence

Exchange fee schedules and account terms are re-checked monthly. Wallet and hardware reviews are re-tested quarterly or on any major firmware release. ETF and IRA pages are re-verified whenever the underlying fund files new disclosures. Every review page shows a "last verified" date — that date reflects the last time a human on our team confirmed the figures against the primary source.

How to report an error

Email [email protected] with the page URL, the specific claim you believe is wrong, and — where you have it — a source. We reply to every substantive report. Confirmed errors are corrected within 48 hours; anything requiring a re-test (hardware, wallet firmware) is corrected as soon as testing completes, and the correction note says why the fix took longer.

Escalation and disputes

If a company or reader disagrees with how we've characterized something after a correction has been made, the matter goes to Editor-in-Chief Jason Viscosi for final review. We do not remove accurate, sourced criticism because a subject objects to it.
RELATED POLICIES
Spotted an error?
Report it and we'll fix it — with a note.
[email protected]