Corrections and appeals

If a Fact-check or UnEcho Chamber result got something wrong, or an outlet’s listing or lean on unAlgorithm Cloud’s source list looks wrong, tell us. We fix causes, publish what changed and count every request in the transparency reports.

What never to send

Use your own words: never the post, a screenshot of it, a link to it, or anyone’s name. Describe the claim or the story as you understood it, so your request carries only what you write.

An appeal filed on GitHub shows your GitHub username to everyone. To appeal privately, email the address given below.

Ask for a correction

Ask from unAlgorithm itself: under a finished result in Highlights, choose Report a wrong verdict (Fact-check) or Report a mistake (UnEcho Chamber). A page opens that shows what your request will carry: the feature, the version of its AI instructions, for UnEcho Chamber whether it used unAlgorithm Cloud’s source list or your own, and which kind of AI made the result. Never the post, the claims, the sources, the link or your list. On that page:

  • choose what’s wrong;
  • describe the claim or the story as you understood it, and why the result is wrong, in your own words (email addresses, phone numbers and links are removed before anything is sent);
  • add your email address if you’d like a reply.

Nothing is sent until you click Send report. Your request goes privately to HeitechSoft, through unAlgorithm Cloud, and only HeitechSoft’s team reads it. The page gives you a reference, such as 7KQ3-M2PA.

If you can’t use the extension, email support@heitechsoft.com instead, with the feature, the claim or the story in your own words, what it showed (a verdict such as Disputed, or a point of a comparison), why it’s wrong, and any public sources that show it.

If you left an email address, or wrote to us, you get an answer within 5 business days and a decision within 30 days. Without an email we can’t reply, but we review every correction and count it in the transparency report. unAlgorithm keeps no one’s results (they live only in your browser), so a correction fixes the cause: a prompt, the blocklist, a bug or a model choice. When the mistake can be reproduced, a made-up example of it joins the evaluation set, so every later change is tested against it. The outcome is sent to you by email when you gave one, described in the release notes when code changes, and counted in the next transparency report. Your words are never published.

The outcome is one of:

  • Corrected, with what changed;
  • No change, with the reason;
  • Out of scope: an opinion, a prediction, or a claim about a private person.

We keep a correction for 90 days, and your email address until 30 days after we answer, never more than 60 days. After that, only a count remains, for the transparency report (privacy policy).

If the result used your own source list, its leans are yours: change them in Settings → AI.

Source list appeals

Anyone may appeal, the outlet included, an outlet’s lean, name, web addresses or country on unAlgorithm Cloud’s source list.

Include the outlet’s id, as the source list page shows it; what is wrong; public evidence; and whether you represent the outlet.

Use the appeal form, or email legal@heitechsoft.com.

An unAlgorithm Cloud admin decides within 30 days. When the Cloud has more than one admin, one who did not make the change appealed decides; while it has one, that admin decides, and the public change history and the quarterly audit below are the check.

During an appeal the lean stays, unless the admin finds it clearly wrong. Then it is removed at once, and that removal is published and listed like any change.

The outcome is a change to the list, or none. It is published at once and listed in the change history, the reasons are given on the issue or by email, and the appeal is counted in the transparency report.

Own lists belong to the people who made them and are not appealed.

Quarterly audit

Every quarter, an unAlgorithm Cloud admin reviews:

  • every change made to the source list that quarter, from its public change history;
  • every outlet appealed;
  • a random 10 % of the outlets with a lean, at least 10 (all of them when there are fewer);
  • every lean unchanged for more than 12 months;
  • every correction;
  • the latest live evaluation results.

When the Cloud has more than one admin, changes are reviewed by an admin who did not make them. The findings are published in that quarter’s transparency report.

Try unAlgorithm Feed

Free and open source. No account, no setup: it starts working on your next scroll.