On this page
Sourcing
Every factual claim on this site is sourced from one of:
- Primary documents (regulator websites, operator legal pages, public blockchain explorers, published specifications).
- Reproducible observations of the operator's own site or product at a specific date.
- Statements we attribute to an identified third-party reviewer (by name of organisation).
We do not use anonymous forum posts, marketing brochures, or affiliate pages as primary sources.
Verified claim vs editorial interpretation — how we mark them
Every page on this site contains a mix of three claim types. We try to phrase each one in a way that signals which category it sits in.
| Type | Phrasing we use | Example |
|---|---|---|
| Verifiable from a public source | Plain assertive sentences with a link. | "The Jeton wallet is published on Google Play under package com.jeton.app." (Link → Play Store.) |
| Observed pattern, not personally tested end-to-end | "at the time of review", "appears to", "Google currently shows" | "jetton.games rendered for us from Canadian IPs at the time of review." |
| Editorial interpretation | "in our editorial view", "reads as", "our scorecard rates this" | "In our editorial view, the operator's terms have a few clauses worth re-reading." |
If a page mixes the three without making clear which is which, that's a bug. Email us via the contact page and we'll fix it.
What we routinely don't verify
For full transparency. These are categories where we paraphrase or describe rather than independently confirm:
- Corporate ownership of third-party domains. When several jetton.* domains appear in a SERP, we don't run registry checks on each.
- End-to-end deposits and withdrawals at international operators. We describe documented behaviour patterns; we don't enrol real accounts at scale.
- Operator-side internal compliance controls. KYC depth, AML controls, RG tooling — we describe what's publicly observable, not what's behind the cashier.
- Smart-contract / RNG audits. We're not a code-audit firm. If an operator publishes an audit report, we link it; we don't re-perform it.
- Live geo-blocking. An operator's geo-block is fluid; we report what we observed in our spot-checks, not what's true today.
- Specific CA bank chargeback policies. We point readers to their card issuer; we don't speak for any bank.
Writing and review
Every page is drafted by one editor, reviewed by another, and fact-checked against the cited sources before publication. Major factual claims are cross-referenced to at least two sources where possible. Claims for which we cannot find solid sourcing are either removed or explicitly flagged as unverified.
Updates and last-reviewed dates
Gambling regulation and operator behaviour change. Every page shows its last reviewed date. When meaningful facts change (bonus structure, regional availability, registration status, operator ownership), we update the page and add a line about what changed. We do not alter dates to appear fresher than we are.
Conflicts of interest
- We don't accept free play credits, promotional tokens, or other in-kind benefits from operators.
- We don't invest in the operators we cover.
- We don't take advertising, affiliate commissions, or referral fees.
If any of this changes, we will disclose it both here and on every affected page.
Corrections
If you spot a substantive error, email us via the contact page with the page URL and the source you'd like us to look at. Substantive corrections are logged on the About page corrections log; minor edits (typos, link fixes) are not.
Process:
- We confirm the source you cite is reachable and credible.
- We re-check the relevant page section.
- If the original is wrong, we fix it within a week and add a corrections-log entry. If we disagree, we reply explaining why.
- If a correction is material, we also update the page's last-reviewed date.
AI tools
We use AI tools to help with drafting, grammar, and cross-checking. Every page is reviewed, edited and fact-checked by a human editor before publication. No page is published as raw AI output. Factual claims are not generated by AI tools without human sourcing.