Dispute Beast
Editorial standards

Editorial policy

Credit advice is only useful if you can tell where it came from. This page explains who writes our guides, what we check before publishing, how we use AI, and how to get a correction made.

Last reviewed: November 2026

Who writes and reviews our guides

Dispute Beast publishes under one editorial identity: the Dispute Beast Editorial Team. The team writes about credit reports, disputes and monitoring from inside the product, so a guide describes what the app actually does, not what a press release says it does.

When a guide carries a named byline, that person wrote the draft and the editorial team reviewed it before publishing. We do not publish invented biographies, stock headshots, or credentials we cannot document.

How we research a claim

Credit writing is full of numbers that get copied without a source. We work from primary material first: the Fair Credit Reporting Act (15 U.S.C. §1681 and the related CFR sections), CFPB guidance and complaint data, the dispute instructions published by Equifax, Experian and TransUnion, and the scored models themselves (VantageScore 3.0 and FICO 8).

When a claim is about the product, we check it in the app or against the engineering change that shipped it. When a claim is about an outcome, we point to the published cohort data rather than an anecdote.

Where the law or a bureau process is ambiguous, we say so in the guide. A clear maybe is more useful than a confident wrong answer.

How we use AI

AI helps us draft, outline and check consistency across a long library. It does not get the final word. A person reviews every guide before it publishes, checks the cited facts, and decides what the page claims.

The credit guidance inside the Dispute Beast app is separate from this blog. The app reads a member's own report and generates dispute letters for that report; it does not guarantee an outcome. The blog explains the process in general terms.

Statistics and results

We publish performance numbers only when we can show the cohort, the method and the time window. Every average score change on this site traces back to the disclosures page, which states the sample, the starting point and the limits of the measurement.

Results vary. A credit profile, the response of a bureau or furnisher, and how consistently a person uses the product all change the outcome. No page on this site promises a specific score, a deletion, or an approval.

Read the performance disclosures

Corrections and review dates

Guides show the date they were last reviewed. We revisit high-traffic guides at least every six months, and sooner when a rule, a bureau process or a product change makes the old text wrong.

If something here is out of date or incorrect, tell us and we will fix it. Email [email protected] with the page URL and the correction. Confirmed factual errors are corrected at the source, and the reviewed date changes so readers can see the edit.

Independence and partners

Dispute Beast is the free app that reads a credit report and writes dispute letters. It is not a credit repair organization and it does not decide what a member disputes.

Credit monitoring is how the app imports a three-bureau report. Brief Credit, Beast Credit Monitoring and ProCreditWatch are separate companies with their own subscriptions, billed by them, not by Dispute Beast. Sprint Mail is an independent mailing partner that prints and mails letters for a fee. We name the price and who bills it on every page that mentions them.

A partnership never buys a conclusion. Comparisons on this site state the criteria and the trade-offs, including where another option is the better fit.

Citing Dispute Beast

You may quote or cite a guide with a link back to the page and the reviewed date shown on it. For data, cite the disclosures page rather than a marketing number, so the cohort and method travel with the figure.

For press, research or partnership questions, email [email protected].

Report an error

Email [email protected]with the page URL and what looks wrong. We review every report and update the page when the correction is confirmed.