Corrections Policy
Last updated: June 2026
ChasingFalls aims to report public data faithfully. When we get something wrong, we want to fix it quickly and in the open. This policy explains how to report an error and what we do with it.
How to report a correction
Email hello@chasingfalls.org — or use our contact page — with:
- The exact page URL on chasingfalls.org
- The specific value or statement you believe is wrong
- If you have one, the record, citation, or source link you believe is correct
The more specific the report, the faster we can verify and fix it. We read every correction request.
What happens next
We verify the reported issue against the USGS Geographic Names Information System (GNIS) and federal land-management records. Corrections we can confirm against the underlying public record are the fastest to make. If a figure on chasingfalls.org does not match the source, we correct chasingfalls.org to match the source. If the source itself is what is disputed, we will say so rather than silently change a number.
Two kinds of correction
- Processing errors on our side — a parsing mistake, a stale value, a broken calculation. We fix these directly and as soon as we can confirm them.
- Source restatements — when the issuing agency revises or restates a record after publication, ChasingFalls follows on the next data refresh. There may be a lag between the agency’s update and ours.
How we disclose corrections
Routine data refreshes update figures continuously and are reflected by the “Last updated” date on each dataset page. For a substantive correction — one that materially changes a score, ranking, or headline figure — we note that a correction was made rather than overwriting the record without a trace. We do not remove accurate, properly sourced information because a subject dislikes it.
Corrections log
No substantive corrections have been logged yet. When one is made, it will be listed here with the date and a short description.
Contact
Reach the corrections desk at hello@chasingfalls.org. For the standards behind our numbers, see our Fact-Checking Policy and Editorial Policy.