Corrections - AI Partner Guides
The corrections log
This page lists every factual correction made on AI Partner Guides: a wrong price, an outdated free allowance, a changed policy, a mistaken statement name, a broken promise in the text. Each entry gives the date, the page, what the page said, what it says now, and where the new fact came from.
| Date | Page | What was wrong | What it says now |
|---|---|---|---|
| - | - | No corrections yet | - |
The log is empty because the site is new. That does not mean the pages are perfect. Prices and policies in this category change often, and some facts on the site will turn out to be wrong or out of date. When that happens, the fix will be listed here, openly, with the date.
An empty log on an old site would be a warning sign; on a new one it only means the clock has just started.
Routine updates are not listed. When an app raises a price and the record is refreshed on its normal check, that is maintenance, and the new check date on the page shows it. A correction is different: it is a case where the site printed something that was wrong at the time, or kept printing something after it stopped being true. Those are the cases this log exists for.
What an entry will look like
Each entry is short and specific. Suppose a review said that an app's cheapest plan cost one amount, and the app's pricing screen showed a different amount on the day the page was printed. The entry would give the date the mistake was fixed, the name of the review, the old amount, the new amount and a link to the pricing screen that confirms it.
If the same fact appeared on a list and a comparison table, the entry would say so, because all of those pages change together.
An entry never hides behind vague wording such as "updated for accuracy". It says what was wrong in plain words, so a reader who acted on the old fact can recognise it. If the mistake could have cost a reader money, for example a price that was too low or a free allowance that was too generous, the entry says that too.
Why corrections are public
A review site asks you to trust numbers you cannot easily check yourself. The honest way to earn that trust is to show what happens when a number turns out to be wrong. Quietly editing a page protects the writer's pride; logging the change protects the reader.
If you once relied on a price that was wrong, you deserve to be able to see that it was corrected, and when.
There is a second reason. A public log makes it harder to cut corners. When every fix is written down with a source, it is obvious whether a page was careless or whether the app simply changed.
Over time, the log shows readers which kind of mistakes the site makes, and it shows me where the checks need to be stronger.
What counts as a correction
- A wrong fact. A price, an allowance, a plan name, a content policy or a statement name that did not match the source at the time it was printed.
- A stale fact. Something that was true when checked but kept being shown after the app changed it, when the change should have been caught.
- A wrong claim in the text. A sentence that says more than the record supports, such as an opinion written as a fact, or a finding from another reviewer written as if it were the author's own.
- A wrong label. A review labelled as a paid-plan test when the author only used the free tier, a hands-on label with no log behind it, or the reverse.
- A misleading link. A button or link whose label does not match where it goes.
Typos, layout fixes and rewrites for clarity are not listed, unless they changed the meaning of a sentence. If in doubt, the change is listed; a slightly longer log is a much smaller problem than a hidden correction.
- Apps tested
- 90hands-on, 73 of them on a paid plan
- Money spent
- $2,083subscriptions, paid with my own card
- Apps in the database
- 79every price with a check date
- Latest test
- FunFun AI
Computed from the test database when this page was built. The same numbers on every page. How the apps are checked
How a correction is made
Every correction follows the same steps, whether it was found by a reader or by a routine check.
First, the new fact is confirmed at a source. The strongest sources are the app's own pages: its pricing screen, help centre, terms or privacy policy, or its app store listing. A dated screenshot of a logged-in pricing screen also counts.
A forum post or a video is a useful pointer, but on its own it does not change a record.
Second, the record is changed, not the page. Every page on the site is built from one record per app, so the fix goes into the record with the new date and the source link. The old value is written into the log entry on this page, so the history is never lost.
Third, the site is rebuilt. Every page that printed the old fact, the review, the lists, the comparison tables, the deals page, now prints the new one at the same moment. This is why a correction here never leaves one page right and another wrong.
Fourth, the change is logged on this page. The entry says what was wrong, what it says now and where the new fact came from. If a reader reported it and wants to be thanked, their first name goes in the entry; if they prefer not, it does not.
Prices get extra care
Prices are the facts readers rely on most, and the ones most likely to change. Every price on the site carries the date it was checked, and the build refuses to print a price older than thirty days. That rule cannot catch a change that happened yesterday, but it does make sure that an old number disappears rather than lingering for months.
Some price differences are not mistakes. Apps can show different prices by country, by device, by account age or through an app store, and a reader may see a different number at checkout for a reason the site cannot see. When a report turns out to be one of those, the page may add a note about the difference instead of changing the price, and no correction is logged. The reader gets a reply explaining why.
Routine checks between corrections
Most changes are caught before anyone has to report them. Because a price older than thirty days disappears from the site, every price has to be checked again at least once a month to stay on the page. Those routine checks are when most changes in the category are found: a new plan, a renamed tier, a free allowance that shrank.
When a routine check finds that the site had already been showing something wrong, that becomes a correction and is logged. When it finds that an app changed since the last check, the record is simply updated with the new date.
Labels and first-hand claims
The site has a strict rule about first-hand claims: no page may say that the author used, paid for or tested something unless a dated log in the record backs it. Every review with a hands-on label rests on Chris Furrey's own notes from his use of the app between 2023 and 2026, printed on the page as a dated log. 73 apps carry the label "Hands-on test, paid plan", 17 carry "Hands-on test, free tier", and one, Dreemy AI, carries "Desk review - not paid for yet". Each app's current prices, plans and terms were re-checked on 23-24 September 2026.
If a page ever breaks that rule, for example by describing a plan the log does not show he paid for, by stretching a few weeks of use into months, or by printing a price from his notes as if it were today's price, that is a correction and it will be logged here. The same goes for a finding from another review site that was written as the author's own experience. The build checks for such sentences before a page goes live, but no check is perfect, and readers are welcome to point out anything that slipped through.
How to report a mistake
If you spot something wrong, write to [email protected] or use the contact page. The most useful reports include:
- the address of the page,
- the sentence or number that is wrong,
- what you see instead, and where,
- the country you are in, if it is about a price.
A screenshot of the app's pricing screen or a link to its help page is the fastest way to confirm a change. You will get a reply either way: that the page was corrected, or why it was not. Reports are welcome even when you are not sure; a question that turns out to be nothing costs a minute to check.
When the app is the problem
Sometimes a report is not about the site at all but about an app that did not do what its own pages promise: a free tier that ended sooner than stated, a cancel button that was hard to find, a charge that looked different on a statement. Those reports are still useful. They cannot change the facts an app publishes, but they can change what a page warns you about, and the page may say that readers have reported the difference.
The site cannot resolve the problem with the app for you; the review lists what is known about the app's refund terms and cancel steps.
Opinions and corrections
Not every disagreement is a correction. Verdicts on this site, such as who an app suits and who should skip it, are opinions built on the author's own use of the app and the facts in the record. Scores are the same kind of judgement: a score that changes after a fair argument is not logged, but a score that changes because a fact behind it was wrong is logged with that fact.
If a reader thinks a verdict is too harsh or too kind, that is a fair argument, and it may change a page, but it is not logged as a correction unless the verdict rested on a fact that was wrong. If a verdict changes because the facts behind it changed, the fact is corrected and logged, and the new verdict follows from it.
What happens when an app closes
Apps in this category close, merge or stop taking new users more often than you might expect. When that happens, the app's record is marked, its prices stop printing, and its review says what happened and when. That is an update, not a correction, unless the site kept recommending the app after it had closed. In that case the entry says so, and says how long the page was wrong.
Related pages
The rules behind the records and the labels are on the editorial policy page. How the site earns money, and what that can and cannot influence, is on the affiliate disclosure page. The about page explains what the site covers and who runs it.
Why a small site bothers
A one-person site could skip all of this and simply fix pages as problems come up. The reason not to is that the category has a trust problem. Many review pages describe weeks of testing that never happened, and prices copied from one site to the next long after the apps changed them.
A reader who has been burned by that has every reason to doubt the next site too. A public log with dates, sources and plain descriptions is one of the few things a new site can offer that is hard to fake, because every entry can be checked against the app's own pages.
It also keeps the work honest on the days when it would be easier not to be. Knowing that a mistake will be listed here with a date is a strong reason to check a fact twice before it goes live.
A promise about this page
This page will not be tidied. Entries are never removed or softened after they are posted, even when a mistake is embarrassing. If an entry itself turns out to be wrong, a new entry corrects it, and both stay. That is the only way a corrections log is worth reading.
If you ever find a correction that was made without an entry here, please report that too; a missing entry is a mistake of its own, and it will be logged like any other.