How we work

Editorial policy

Effective August 28, 2026 · Version 1

Refund Radar is an educational, privacy-first utility. We publish general consumer guidance after review against primary sources where available. We do not accept payment to change a recommendation, label a time-sensitive issue, or alter a scanner result. If a link may earn a commission, we label it clearly and present the relevant official resource first.

The commitments on this page are written now, while the site carries no advertising, no sponsorship and no affiliate or referral links anywhere, and while nothing has been sold to anybody. A policy drafted after the first payment arrives is worth considerably less than one drafted before it.

They are also written down where the work happens rather than only here. The governance record for every scanner situation lives in content/sources.json in the site's repository, and it carries both the rule against paid placement and the field requirements the build enforces. This page explains the rest: where the facts come from, what each page has to carry, how a mistake gets corrected and how quickly, and what the site leaves to you.

How sources are selected

The order is fixed. A statement about a rule rests on the rule: the statute or regulation itself, or the enforcing agency's own consumer-facing page. In practice that means the Department of Transportation on airline refunds, the CFPB on card billing errors and disputes, the FTC on auto-renewals and shipping deadlines, and the CPSC on recalls.

For anything contractual rather than statutory — a return window, a marketplace protection period, a fare rule — the primary source is the company's own published terms, and the guide says plainly that it is policy rather than law.

Consumer blogs, forum threads, and journalism are read as context: useful for surfacing what is going wrong this month, useless as authority. Our standard is that no rule is stated here on the strength of a secondary summary.

What every page carries

The standard is that each scanner situation and each published guide carries four things: the date it was last reviewed, a named review owner, the jurisdiction the guidance is scoped to, and either at least one primary source or a written statement of why no primary source applies. The review owner is Refund Radar editorial at Oak and Main Developers LLC, the operator of the site.

For the scanner records that requirement is machine-checked. They live in content/sources.json, one entry per situation, and the build fails if an entry is missing its jurisdiction, its reviewed date, its review owner or its source list, or leaves the source list empty without writing down why. The guides carry the same four fields under the same rule, checked by reading rather than by a script.

That fourth item is the one people miss. An empty source list is a claim, not an omission: where no federal rule applies, the record says so and names what governs instead.

A reviewed date tells you how current our reading was on that day. It does not tell you the rule is unchanged today. Where your money or a deadline turns on the detail, read the official source before you act.

The review cadence

We aim to review each record quarterly, and the next review date is written into the record itself rather than kept in somebody's head. A review means reopening each linked page, checking it still says what we said it said, and either re-dating the record or changing the guidance. A fresh date on text nobody re-read is the failure this cadence exists to prevent.

A link checker requests every source URL the site publishes and reports anything that has moved or died. We run it before a source change goes out and again on the review date. It is deliberately outside the build check, so that a government site being briefly down cannot block a deployment — which does mean it depends on a person remembering to run it. If the rule moved with the link, the sentence is rewritten or removed before any date is refreshed.

These are the standards the site is held to, not a guarantee that every page meets them on any given day. If you find one that falls short — an unopened link, a missing jurisdiction line, a record sitting past its review date — tell us at [email protected] and it will be handled as a correction report.

How corrections work

Report a correction to [email protected]. A useful report gives the page address, the sentence you think is wrong, and where the official source says otherwise. Please do not send account numbers, card details, or claim documents; that address is also the privacy contact, and the site is built not to hold material of that kind.

We aim to acknowledge a report within two business days and to say what we intend to do about it. Once we agree a material correction is needed, the target is five business days to publish the fix. Where the error is deadline-bearing — a clock, a notice window, an order of steps that has to happen before a deadline runs out — it goes ahead of the queue, and the aim is to correct it or take it down the same day. If we think the page is right, you get the reasoning and the source rather than silence. These are targets rather than guarantees, and a missed one is itself worth reporting.

Independence from any future referral economics

The site is free to use and there is an intention to fund it eventually. The rules below are what a compensated link would have to satisfy before it could appear, and the same list gates the release that first carries one: the affiliate disclosure page, the terms page, and the governance record all change in that release rather than after it.

What this site deliberately does not do

Limits that catch people out