KYC policies: Rust operator evidence index
Official-source records for KYC policies across eight documented Rust-facing operators. Unknown facts remain unresolved and no transaction testing is claimed.
Dataset version 2026-10-26.1 · published · revised · latest source observation in this topic . A revision date does not renew older source observations.
When can an account require verification?
Read when checks can be requested, what they concern and which account actions depend on completion. A sign-in method does not answer those policy questions.
- Look for checks tied to account opening, contest entry, deposits, prizes or withdrawal requests.
- Separate identity and eligibility requirements from payment ownership or source-of-funds checks. Missing document tiers remain unknown.
Example from the registry: The recorded Howl withdrawal conditions connect cleared deposits and required identity checks; they also describe source-of-funds review. This documents conditions without establishing a user’s verification outcome. Read the Howl verification record.
| Operators | Recorded field | Status | Evidence |
|---|---|---|---|
| RustSnowball | Account and risk checks are described in the terms and withdrawal documentation.Established in the current official-source pack. | verified | rs-terms · official termsObserved Aug 30, 2026 · record hash a63b6bbc06e9 rs-crypto-withdraw · official helpObserved Aug 30, 2026 · record hash 0fa167d910f4 |
| RustClash | Section 2 permits requests for identity and eligibility documents before contest entry or a prize.No account verification was performed; document tiers are not established here. | verified | rc-terms · official termsObserved Sep 5, 2026 · record hash 624e7e05b895 |
| Howl | Withdrawal requires cleared deposits and any required identity checks; source-of-funds checks can prevent withdrawal of unspent deposits.Published conditions only; no account verification or document submission was performed. | verified | howl-policy-withdrawals-20260905 · official termsObserved Sep 5, 2026 · record hash 2402095d92bb |
| BanditCamp | Not established from the current official-source pack.Exact document tiers and account outcomes were not tested. | unknown | No supporting source |
| RustyLoot | Not established from the current official-source pack.Exact document tiers and account outcomes were not tested. | unknown | rustyloot-terms · official termsObserved Aug 27, 2026 · record hash 3739e38d41fa |
| RustMagic | Not established from the current official-source pack.Exact document tiers and account outcomes were not tested. | unknown | rustmagic-terms · official termsObserved Aug 27, 2026 · record hash f47a0a145cb3 |
| RustReaper | Not established from the current official-source pack.Exact document tiers and account outcomes were not tested. | unknown | rustreaper-terms · official termsObserved Aug 27, 2026 · record hash 740a945df70c |
| 500 Casino | The public terms describe account-verification controls.Exact document tiers and account outcomes were not tested. | partial | 500casino-terms · official termsObserved Aug 27, 2026 · record hash 5f027754dab9 |
Methodology, limitations and citation
- Public official sources only; no account, deposit, wager, KYC, support or withdrawal test was performed.
- Unknown means the current source pack did not establish a field; it does not prove absence.
- Record hashes identify normalized evidence records, not byte-for-byte archives of remote pages.
Suggested citation: rustgambling.site, Rust Operator Claim Graph 2026, version 2026-10-26.1, CC BY 4.0.
For a specific finding, include its claim ID, official source ID and source observation date. Link to the row anchor, for example rc-kyc, rather than citing the total number of sources. Download the derived coverage audit; unresolved values are preserved.