This is our corrections policy. It explains how to tell us we got something wrong, what we do next, and how you can see what changed. It ends with a public log of every correction we have made.
Haxies publishes numbers: wagering multiples, clearing costs, payout speeds, licence numbers. Numbers are easy to get wrong and easy to check, which is exactly why we want you checking them.
A mistake on a casino comparison site isn't harmless. If we misprice a bonus, someone might claim an offer that costs far more than we said. So we treat corrections as part of the work, not an embarrassment to hide.
Why Haxies has a corrections policy
Haxies has a corrections policy because every score we publish rests on facts you can verify, and some of those facts will be wrong or go stale. The policy commits us to checking every report against the source, fixing confirmed errors quickly, dating every change and listing the ones that could have misled you in a public log.
The alternative is quietly editing pages and hoping nobody noticed. Plenty of sites work that way. We think it's a bad habit, and it makes every number on the page less trustworthy, including the correct ones.
How to report an error
The fastest route is an email to [email protected], the address on the contact Haxies page. A good report has three parts:
- The page URL where you saw the problem.
- What you think is wrong, in a sentence or two.
- A source, ideally a link to the operator's own published terms, licence register or help centre.
The source is the part that speeds things up most. "Your Wild.io page is wrong" takes us a while to investigate. "Wild.io's welcome package terms now say 35x, not 40x, link here" can be checked in minutes.
You don't need to be certain you're right. If something looks off, tell us. Half the value of reader reports is that they make us look again.
Who can report an error
Anyone. Readers, players, other publishers and casino operators all use the same route and get the same treatment. Operators don't get a private channel or faster handling. If an operator shows us a published term we misread, we fix it. If an operator simply disagrees with a score, we explain the working, and the score stays where the maths puts it.
What happens after you report
Each report goes through the same steps:
- Log. The report is recorded with the date received.
- Check. A fact-checker compares the claim against the cited source and our dated data sheet.
- Decide. If we were wrong, the error is classified (see below). If we were right, we reply explaining why.
- Fix. The terms reader and maths checker update the facts and any scores they affect.
- Edit. The editor checks the fix reads correctly and that every page carrying the fact has been updated.
- Mark and log. The page is dated, and the correction is added to the log if it qualifies.
That last step matters more than it looks. A wrong wagering base on one review usually also appears in the bonus list, the toplist and a coin page or two. Fixing the review but leaving three other pages wrong would be worse than useless.
Response time goal
We aim to reply to every error report within two working days. For confirmed errors in prices, scores, licence numbers or anything that affects money, we aim to publish the fix within the same window.
That's a goal, not a guarantee. Some reports need us to wait for an operator to clarify an ambiguous clause, or for a terms page that has gone offline to come back. When that happens, we tell you, and the affected figure is marked "not confirmed yet" on the page until we can settle it.
Corrections versus updates
Not every change is a correction. The difference matters because it tells you whether we got it wrong or the world moved.
| Type | What it means | How it is marked | Logged below? |
|---|---|---|---|
| Correction | We published something wrong at the time we published it | Dated note on the page explaining what was wrong | Yes, if it could have misled a reader |
| Update | The operator changed its terms, or new information became available | New "figures read" date on the page | No |
| Clarification | The fact was right but our wording could be misread | Dated note on the page if meaning changed | Only if it affected a decision |
| Typo fix | Spelling or formatting with no change in meaning | Silent | No |
Example of a correction
Say a review stated that a casino's 40x rollover applies to the bonus only, when the terms actually said deposit plus bonus. On a $100 deposit with a $100 bonus, the true turnover is $8,000, not $4,000. At a 2% house edge, the expected cost is about $160, not $80. That moves the casino from the top Clear band into a lower one, which changes its Index score and its Index rank. That is a correction, and it gets logged.
Example of an update
Say the same casino later cuts its rollover from 40x to 35x. We weren't wrong before. The terms changed. The page gets a new "figures read" date, the score is recalculated, and the change is noted on the review. It doesn't go in the corrections log because there was no error to correct.
How corrections are marked on the page
When a correction is made, the page carries a short dated note near the affected section. It says what was wrong, what is right now, and when it changed. Something like: "Corrected 12 November: wagering base is deposit plus bonus, not bonus only. Clear score changed from 40 to 24."
We don't strike through old text or leave the error visible in the body. The note is enough to tell you something changed, and the body should always read correctly to someone arriving fresh.
If a correction changes a score, every list carrying that casino updates at the same time, including the main best crypto casinos list.
Which facts get the closest attention
Some facts carry more weight than others, so they get checked first and fixed fastest:
- Wagering multiple and wagering base. These drive the Clear score and the expected cost of every bonus.
- Withdrawal caps. A published cap costs 5 points of Cashout and matters a great deal to anyone with a large balance.
- Licence numbers. Readers use them to look up an operator with its regulator in Curaçao or Anjouan.
- Owner names. These tell you which company is legally responsible for your balance.
- Coin support. Sending a coin on an unsupported network, say an ERC-20 token to a TRC-20 address, can mean lost funds.
The scoring method behind all of this is documented in how we test crypto casinos. If the method itself ever changes, that page changes first and every affected score follows, with a dated note.
How to check a Haxies figure yourself
You don't need to trust us. Every brand fact on Haxies comes from a source you can open, and most checks take a couple of minutes.
- Bonus terms. Each review lists the operator's terms source and the date we read it. Open it, find the wagering clause, and look for two things: the multiple (40x, 60x and so on) and the base (bonus only, or deposit plus bonus).
- Clearing cost. Multiply the bonus by the multiple to get turnover, adding the deposit if the base includes it. Multiply turnover by 2% for a rough expected cost on a high-RTP slot. If your number differs from ours by a lot, tell us.
- Licence. Copy the licence number from our page and search for it on the regulator's register. An Anjouan number starts with ALSI. A Curaçao number usually starts with OGL. Brands on our list of new crypto casinos have shorter track records, so the licence check is worth the extra minute there.
- Payout speed. Check the operator's cashier or help centre for its stated speed. Remember we publish what the operator states, so a mismatch there means the operator changed its claim.
Every one of our crypto casino reviews carries the same fact box, so the check works the same way on every brand.
Mistakes we expect to see most
Being honest about where errors creep in helps you spot them. The usual suspects are wagering bases buried in a different clause from the multiple, tiered rollovers that change from deposit to deposit, withdrawal caps that rise with VIP level, and bonus codes that operators rotate without notice. Codes are especially fragile, so treat any entry in our crypto casino bonus codes list as accurate on the date its figures were read, and confirm it in the cashier before you deposit.
Fast-moving coin support is another. An operator may add Solana or drop a network, and if you send funds on a network the cashier no longer accepts, recovery can be slow or impossible. Always confirm the network in the cashier before you send, whatever any comparison site says.
What we won't change on request
Some requests aren't corrections. We won't change a score because an operator dislikes it, remove a fair criticism because it hurts sales, or swap "stated" for a stronger word without evidence. Payout speeds stay labelled as the operator's stated figures, and we won't present one as our own measurement.
We also won't delete a correction note after the fact. Once a correction is published, it stays on the page and in the log. Commercial relationships play no part in any of this, as our affiliate disclosure explains in detail.
Who handles corrections
Corrections run through the same Haxies group that produces the pages: a terms reader, a maths checker, a fact-checker and an editor. Each role checks its own part of the fix. The Haxies editorial team page describes those roles and the sourcing rules they work to.
When a mistake comes from a weakness in our process, such as relying on a third-party summary that turned out to be wrong, we fix the process too. That might mean going back to the operator's own terms for every casino where we used that source.
When a correction touches a listing
Every casino on Haxies was tested and confirmed by multiple sources in the group and approved by Team Lead Harrison Ayla before it was scored. If a reported error suggests a listed brand no longer meets that bar, for example a licence that can no longer be confirmed, the correction goes back to Harrison as well as to the scoring roles. He decides whether the brand stays listed, and the outcome is dated like any other change.
Corrections policy questions
How do I report a mistake on Haxies?
Email [email protected] with the page URL, what you think is wrong, and a link to the source. A link to the operator's own published terms gets the fastest check.
How quickly does Haxies fix errors?
We aim to reply within two working days and to publish fixes for confirmed money-related errors in the same window. Some fixes wait on an operator clarifying a term, and we tell you when that happens.
What is the difference between a correction and an update?
A correction fixes something we got wrong when we published it. An update reflects a change the operator made later, such as a new rollover or a new licence. Both are dated, but only corrections that could mislead go in the log.
Will Haxies tell me if my report was wrong?
Yes. If we check the source and the page is already correct, we reply with the term or calculation that supports it. You're welcome to come back with more evidence.
Can a casino ask Haxies to change its score?
A casino can report a factual error like any reader, and we fix genuine mistakes. A casino cannot get a score changed because it disagrees with the method or the result.
Does Haxies remove old correction notes?
No. Once a correction is published, the note stays on the page and the entry stays in the log. Deleting it later would defeat the purpose.
What if the operator's terms page is offline?
The affected figure is marked "not confirmed yet" until we can read a current version. We don't guess, and we don't keep publishing a figure we can no longer verify as current.
Corrections log
Each entry lists the date, the page, what was wrong and what changed. Newest entries appear first.
7 October 2026. Site launched. No corrections yet.
This log starts on launch day because that is when Haxies started publishing. New corrections appear at the top with their date and details. We would rather this log grew slowly, but we would much rather it grew honestly than stayed empty because we stopped looking.