Corrections
The policy
The CryptoGuardz Register Desk is accountable for every finding published here and the person a correction reaches. We acknowledge a report within three working days, and say at that point either what we are changing or why we are not. A corrections policy with no clock is a promise with no term, which is the criticism this register makes of operator payout clauses.
When we get something wrong we correct it, date the correction, and leave the original visible. We do not quietly edit a page and let the old version disappear, because a register whose history can be rewritten is not a register.
Factual errors are corrected on receipt of a primary source. Disagreements about interpretation are published as the operator’s stated position alongside our finding, so a reader can see both and decide.
Operator right of reply
Any operator we write about can respond, and we will publish the response on the entry. If documentation shows a finding is wrong, the finding changes. If it shows the finding is right but incomplete, the missing context goes on the page.
We will not remove an accurate, sourced finding on request, including from operators who pay us. That is the whole point of the disclosure on every page.
What counts as a correction
A factual error: a wrong licence number, a misread clause, a stale figure presented as current, a claim attributed to the wrong document. Updating a page because an operator changed its terms is not a correction, it is a review, and it shows up as a new last-reviewed date instead of here.
The log
| Date | Page | Was | Now | Why |
|---|---|---|---|---|
| 2026-09-24 | /tools/wagering-calculator/ | The calculator opened pre-filled with a 150 per cent match, a 1,500 cap and a 35x requirement on bonus plus deposit, which is one named commercial partner's live offer, with no disclosure beside it. | Round default figures belonging to no operator, and a disclosure block where the partner is named in the prose. | A calculator on a site that intends to be paid by an operator should not open on that operator’s promotion. The arithmetic was correct and the defaults were advertising. |
| 2026-09-24 | /tools/risk-of-ruin-calculator/ | Blank results and no verdict for any bankroll worth more than about 8,900 times the bet size, for example $1,000 played at ten cents a spin. | The ruin probability is computed in log space and returns a figure at every input the form accepts. | The direct form of the gambler’s-ruin expression overflowed to infinity at large unit counts and produced a division of infinity by infinity. The tool failed silently on one of the commonest inputs anyone would type. |
| 2026-09-24 | /tools/bonus-value-calculator/ | A game contribution of zero was floored to one per cent, an RTP above 100 per cent produced a positive expected value and a verdict recommending the offer, and a maximum bonus of zero was read as no maximum. | Each of those inputs is refused with a sentence saying why, and an empty maximum-bonus field means no maximum while a typed zero means zero. | Silently substituting a different number for the one a reader typed turns a wrong input into a confident wrong answer, which on a bonus calculator is the answer they act on. |
| 2026-09-24 | /cookies/ | A table of four cookies, including an analytics cookie and a consent cookie for an analytics prompt. | This site sets no cookies. Two localStorage values are listed instead, and the Google Fonts request is disclosed. | None of the four existed. The site sets no cookies, runs no analytics and has never shown a consent prompt. The page described a build that was never shipped. |
| 2026-09-24 | /privacy/ | "We do run analytics" and a description of aggregate page analytics at country level. Affiliate links described as carrying a referral identifier. | No analytics of any kind, and no outbound link carrying affiliate tracking today. | Both statements were untrue of the build and the second contradicted our own disclosure page, which already said we had earned nothing. |
| 2026-09-24 | /responsible-gambling/ | A hand-typed country table listing Loket Kansspel on 0800 022 2030 for the Netherlands, and the BZgA helpline for Germany. | The table is rendered from the same verified directory as the footer band: Open over Gokken on 0800 24 000 22, and Check dein Spiel. | Loket Kansspel had been superseded by OpenOverGokken and check-dein-spiel.de rebranded from BZgA to BIOeG. Both were already recorded as corrected in our own data file; the prose page was not updated with it. A person in the Netherlands following this page would have called a dead number. |
| 2026-09-24 | /verified-licence/ | "Five of them sit on the register with the contradiction attached." | Three of them. | Five operators present a Curacao licence whose registry term has ended. Of those five, three also carry the certificate-portal-says-Active contradiction. Two other pages stated three correctly. |
| 2026-09-24 | /licences/costa-rica/ | A table headed "Operators on the register under this jurisdiction" listing Anjouan licence numbers under a page stating that Costa Rica issues no gambling licences. | Operators are listed under the authority that issued their licence only. | The query matched an operator’s governing-law jurisdiction as well as its licensing authority, so three Anjouan licensees rendered on the Costa Rica page. The licence index also totalled 17 operators for a register of 14. |
| 2026-09-24 | /chains/usdt/ | USDT described as arriving "mostly TRX $1.36bn, ETH $1.02bn, SOL $583m". | The per-chain split is not published. | Those are whole-chain totals for all tokens, not USDT on those chains. The source publishes a per-chain breakdown and a per-token breakdown with no cross-tabulation, so the figure stated could not be derived from it. |
Report an error to , marked for the attention of the register desk. Its standing and the byline arrangement are set out on the editorial byline page.