# Corrections

> How Email Fast fixes factual mistakes on this site: quarterly re-verification of every comparative claim, a stated correction window, and how to report an error.

Canonical: https://emailfast.dev/legal/corrections

## The commitment

If something factual on this site is wrong — a number, a comparison, a capability claim
— we will correct it. Report it to **hello@emailfast.dev** and we commit to responding
and, where the claim is inaccurate, publishing a correction **within 10 business days**.

## How comparative claims are kept current

Statements about other platforms are the highest-liability copy on any site, and they
decay silently as those platforms change. So they are on a schedule, not on vibes:

- **Quarterly re-verification.** Every named-competitor claim is re-checked against a
  fresh capture of that platform's own public pages each quarter, and its verification
  date is refreshed. Our method and the platforms we survey are on the
  [claims methodology](/legal/claims-methodology) page.
- **Evidence captured.** Each comparative claim will be backed by an archived snapshot
  of the source page it mirrors, kept alongside our internal claims ledger.
- **Mirror, don't infer.** We phrase each claim to say what the source document says,
  not what we infer from it — so a claim can never outrun its evidence.

## The mechanical backstop

Every load-bearing factual claim on this site is written as a ledger entry and resolved
when the site is built. The build **fails** if a page cites a claim the ledger doesn't
recognize, or uses a phrase we've told it we may not honestly make. The marketing
literally cannot ship ahead of the product. The [claims methodology](/legal/claims-methodology)
explains how that gate works.

## When we're wrong

A correction says what was wrong, what it's now, and when it changed — the same plain
posture we take with [incidents](/status). We'd rather you catch us and see us fix it
than never make a claim worth checking.