| 01Legal operator identity | DocumentedThe terms footer names Twocent Technology Limited as the operator of BC.GAME. The footer gives Belize company number 41939 and an address at Sea Urchin Street #2, San Pedro, Ambergris Caye. The licences page, the privacy policy and the AML policy give the same company as number 000041939 at Sea Urchin Street, without the house number. The Anjouan licence register names the same company for bc.game. The pages were read on the official mirror bc.co, which the operator lists at bcgame.com. | DocumentedThe operator and regulator records bind Medium Rare N.V. to stake.com. |
|---|
| 02Licence and domain coverage | Partial evidenceThe footer, the licences page and the privacy policy state licence ALSI-202410011-FI1 from the Government of the Autonomous Island of Anjouan, Union of Comoros. The public licence register at anjouangaming.com lists the same number for Twocent Technology Limited. The register shows status valid, type B2C, issue date 2024-10-02 and expiry date 2027-10-01. The register row lists bc.game among 12 domains. It does not list bc.co, the mirror that RTP Ledger read. Coverage gaps: licence status. | DocumentedThe regulator certificate listed the covered domain, licensee, number and active status. The Curaçao Gaming Control Board's bulk licence registry PDF is dated 2026-09-10. The registry PDF lists the same licence number and Medium Rare N.V., company number 145353. The registry PDF gives an issued date of 9 December 2025 and an expiry date of 9 June 2026. The registry PDF gives a different status: "Assessment in progress". RTP Ledger does not resolve this discrepancy between the two regulator-published sources. |
|---|
| 03Country restrictions | DocumentedTerms clause 4.3 bars residents of, and access from, 12 named territories. They are Australia, Austria, France, Germany, the Netherlands, Spain, the Union of the Comoros, the United Kingdom, mainland China, Hong Kong, Macau and the United States. The clause also bars all FATF-blacklisted countries and other jurisdictions that the Anjouan Offshore Financial Authority prohibits. The KYC help article lists unsupported regions for verification. That list adds Brazil as a temporary restriction and does not name China, Hong Kong or Macau. The two published lists do not match. | DocumentedThe global terms enumerate 45 prohibited jurisdictions and prohibit VPN or proxy location manipulation; a named region is not silently expanded to an entire country. Checked Aug 1, 2026Stake terms ↗ |
|---|
| 04Account journey and closure | DocumentedTerms clause 5.1 allows one personal account for each individual. Registration is an invitation to contract, and acceptance occurs only when the account is created. Clause 4.1 sets a minimum age of 18, or a higher age where the law requires it. The registration page states that the registered email address cannot be changed later. The KYC help article describes two levels. Basic KYC needs a government photo ID and a selfie taken from five angles. Advanced KYC needs a proof of address dated within the last 3 months, but only on request. Review is automated in most cases. A player can resubmit up to 6 times, and some cases go to manual review. The article states that a player who fails KYC can still play, but some currencies need KYC for deposits or withdrawals. The self-exclusion help article states that permanent self-exclusion is also used to close accounts. After a permanent exclusion, the player has a 7-day withdrawal period from the date of notification. The account then becomes inaccessible and any remaining balance is forfeited. Funds with open wagering requirements are forfeited at once. The registration page tells a player who needs a new email address to close the account and open a new one. | Partial evidenceThe public terms state the age condition and contractual registration step. Coverage gaps: observed verification journey, observed account-closure journey. Checked Aug 1, 2026Stake terms ↗ |
|---|
| 05Payment catalogue | DocumentedThe deposit-confirmation article gives a table of 15 entries: BTC, SATS, ETH, XRP, DOGE, USDT, LTC, BCH, XLM, TRX, BSV, EOS, DAI, USDC and XMR. The article tells USDT senders to use the specific ERC20 or TRC20 address. The deposit guide tells the player to choose the coin and the network in the cashier. XRP, XLM and EOS also need a memo, tag or destination ID. Neither article states that the table is the complete list. | Documented9 payments.asset_withdrawal_table records cover BTC, DOGE, ETH, LTC, SOL, TRX, USDC, USDT, XRP. Each record follows the same documented pattern: BTC appears in Stake's public asset-level withdrawal table. The source does not bind the row to a specific network, so RTP Ledger does not treat it as an exact route claim. 17 payment route list records cover BTC on Bitcoin, DOGE on Dogecoin, ETH on ERC-20, ETH on BEP-20, LTC on Litecoin, SOL on Solana, TRX on TRC-20, USDC on ERC-20, USDC on BEP-20, USDC on Polygon, USDC on Solana, USDT on ERC-20, USDT on BEP-20, USDT on Polygon, USDT on TRC-20, USDT on Solana, XRP on XRP Ledger. Each record follows the same documented pattern: BTC and Bitcoin appear together in Stake's accepted-networks table for deposits. RTP Ledger does not transfer asset-level withdrawal minimums or fees onto this route. |
|---|
| 06Deposit terms | DocumentedThe deposit-confirmation article states that the minimum deposit differs by cryptocurrency and that support can give the figure. It states that there is no maximum. Deposits take between 1 minute and 2 hours. Deposits from contract wallets can take up to 12 hours. The table asks 1-3 confirmations for BTC, 6 for ETH and USDT, 2 for BCH, 9 for BSV and 6-12 for most other coins. Terms clause 10.5 states that limits normally show before the transaction completes. | Partial evidenceRTP Ledger checked the public crypto withdrawal table, but it does not establish exact deposit-route terms. Deposit minimums, fees, confirmation requirements and crediting stages remain unknown. Coverage gaps: deposit route terms. |
|---|
| 07Withdrawal terms | Partial evidenceTerms clause 11.1 makes withdrawals subject to identity verification and promotional conditions. Clause 11.4 allows a delay while the operator reviews fraud or compliance risk. Clause 11.7 allows a withdrawal fee only where it shows before confirmation. The fee guide states a minimum withdrawal fee of 0.1%. The VIP page lists fee-free deposits and withdrawals as a VIP reward. Help articles state a 24-hour withdrawal hold after a password change and after 2FA is disabled. No checked page states a minimum withdrawal amount. RTP Ledger has not observed a withdrawal on bc.game. Processing time and effective fees are not established. Coverage gaps: first-party withdrawal processing observation. | Partial evidenceThe public terms describe four material withdrawal conditions but do not provide an observed processing time. Coverage gaps: first-party withdrawal processing observation. Checked Aug 1, 2026Stake terms ↗ |
|---|
| 08Bonus terms | Partial evidenceThe Monthly 4 Deposit Bonus article lists four stages in a fixed order. They are 180% from a $5.00 deposit, 240% from $10.00, 300% from $20.00 and 360% from $30.00. The bonus goes to locked rakeback. It unlocks into withdrawable cash as the player wagers on non-PvP games. The stages reset on the 1st of each month at 00:00 UTC. The article does not state the unlock rate, a maximum bonus amount or an expiry. Terms clause 12.2 states that each promotion can carry its own rules. Coverage gaps: bonus eligibility and expiry. | Partial evidenceStake publishes that a valid affiliate code entered within 24 hours unlocks rakeback equal to 3.5% of house edge. RTP Ledger does not infer a fixed deposit-match amount, wagering requirement or account-specific eligibility. Coverage gaps: bonus eligibility and expiry. |
|---|
| 09KYC and source-of-funds process | Partial evidenceTerms clause 5.3 allows document requests at any time, including before deposits or withdrawals. Clause 6.2 lists photo ID, proof of address, payment-method and wallet ownership, a selfie, source of funds and source of wealth. Clause 6.7 allows delayed withdrawals and a suspended account if the player does not complete verification. The KYC help article states that some currencies need KYC for deposits or withdrawals. No checked page states a withdrawal amount that triggers verification. RTP Ledger has not run a test account on bc.game. The stage where verification is requested in practice is not established. Coverage gaps: observed KYC trigger and stage. | Partial evidencePublished records support possible withdrawal KYC and a detailed source-of-income document list, not the trigger timing for a specific account. Coverage gaps: observed KYC trigger and stage. |
|---|
| 10Responsible-gambling controls | DocumentedThe gambling limits page offers loss or wagering limits over a daily, weekly, monthly or quarterly period. Active limits reset at 00:00 UTC at the end of each period. Removing a limit takes effect at 00:00 UTC after a cooling-off period of at least 24 hours. Terms clause 16.4 also names deposit limits, session reminders and cooling-off periods where the platform supports them. The self-exclusion page and help article describe a 24-hour cooldown first. The player then chooses 1 day, 1 week, 1 month, 6 months or a permanent exclusion. Both pages state that self-exclusion cannot be reversed. A self-excluded player can still log in to withdraw. Discrepancy: the responsible gambling FAQ states that self-exclusion locks the account for a minimum of 6 months. The same FAQ offers a 7-day cooling-off period. This claim record states both and does not resolve the difference. | DocumentedThe help centre publishes loss and wager limits plus a delay before an increase takes effect. The help centre publishes both indefinite self-exclusion and shorter break-in-play options. |
|---|
| 11RTP Ledger cashout test | Partial evidenceRTP Ledger has not withdrawn funds from a bc.game test account. Cashout speed and fees are not observed. Coverage gaps: first-party cashout test. No dated source | Partial evidenceRTP Ledger has not registered a completed Stake cashout observation. Published withdrawal rules are not a substitute for a first-party cashout test. Coverage gaps: first-party cashout test. No dated source |
|---|
| 12Complaint handling | Partial evidenceTerms clause 20.1 tells players to contact customer support first. Clause 20.2 allows escalation for internal review. Clause 20.5 allows confidential arbitration under rules that the company specifies, where the law permits. The terms do not name an external dispute body or a response deadline. Coverage gaps: attributable complaint cases. | Not checkedComplaint handling and resolution outcomes are not checked in a dated source record. No dated source |
|---|
| 13Ownership and related brands | Partial evidenceThe Anjouan register row for Twocent Technology Limited lists 12 domains under one licence, including hash.game, bc.fun, bcpoker.com and blaze.game. The licences page names two more brands under other companies and other licences. BlockDance Africa Limited runs bcbet.ng under a Nigerian permit. PRODUCCIONES MOVILES S.A DE C.V. runs bcgame.mx under a Mexican permit, and PUBLIPLAY MEXICO, S.A. of C.V. manages it. The privacy policy mentions affiliated companies within a BC.GAME corporate group. No checked page names a parent company. Coverage gaps: parent/legal-group relationship. | Partial evidenceThe terms call both payment-processing companies wholly owned subsidiaries. Coverage gaps: parent/legal-group relationship, related-brand relationship. Checked Aug 1, 2026Stake terms ↗ |
|---|
| 14Game catalogue and RTP evidence | Partial evidenceThe provably fair page gives a worked Crash calculation that sets a 1% house edge. The responsible gambling FAQ states that all games have an RTP and a house edge. No checked page publishes an RTP figure for each game. RTP Ledger records the catalogue fields as unknown. Coverage gaps: published game RTP values. | DocumentedThe public Stake Engine catalogue lists game, RTP and event-count records for each mode. RTP Ledger has no permanent archived copy of the catalogue. RTP Ledger does not infer account-specific availability from the catalogue. |
|---|
| 15Fairness and verification | Partial evidenceThe provably fair page states that BC.GAME generated 10 million hashes for Crash and releases them in reverse order. Each hash maps to one Crash multiplier, so each result exists before the round starts. The page shows how to turn a hash into a multiplier with a 1% house edge. It links to a verification script on GitHub. The checked section covers Crash only. RTP Ledger has not reproduced a BC.GAME Crash round with the published method. Independent confirmation of a real result is not established. Coverage gaps: reproduced account-bet verification. | Partial evidenceStake publishes the algorithm and inputs for supported verifiable bets. Coverage gaps: reproduced account-bet verification. |
|---|
| 16Account and withdrawal security | Partial evidenceThe 2FA help article explains how to enable authenticator-app 2FA after email or phone verification. The Google Authenticator page states that an enabled 2FA code is required at each login and each withdrawal. The 2FA article states that withdrawals are disabled for 24 hours after 2FA is disabled. Terms clause 7.2 recommends multi-factor authentication where available. The password-change article states that withdrawals stop for 24 hours after any password change. Terms clause 7.3 asks the player to report a suspected compromise without delay. The same clause lets the operator suspend access while it completes security and identity checks. Coverage gaps: withdrawal re-verification. | Partial evidenceThe help centre documents 2FA coverage and activation. The help centre documents an extra withdrawal authentication step for supported social logins. Coverage gaps: recovery and session controls. |
|---|
| 17Support and escalation | Partial evidenceThe support page states that a 24-hour online customer support team is available at any time. The licences page gives compliance@bcgame.com for legal and compliance questions. Terms clause 20.1 sends complaints to customer support first. RTP Ledger has not timed a support request on bc.game. Response times are not established. Coverage gaps: timestamped support-response test. | Partial evidenceThe terms publish the channels and stated availability, not observed response quality. Coverage gaps: timestamped support-response test. Checked Aug 1, 2026Stake terms ↗ |
|---|
| 18Product and user experience | Not checkedProduct catalogue, devices and observed usability defects are not checked. No dated source | Not checkedProduct catalogue, devices and observed usability defects are not checked. No dated source |
|---|
| 19VIP and loyalty mechanics | Partial evidenceThe VIP level article lists seven tiers: Beginner, Bronze, Silver, Gold, Platinum, Diamond and Eternal. Each tier has levels I to X. XP comes from valid bets on non-PvP games. Each level gives a level-up reward with no expiry. The VIP Club page lists lossback, reloads, fee-free deposits and withdrawals and a VIP host. The page states no rate or threshold for those perks. Coverage gaps: effective VIP value and expiry. | Partial evidenceThe help centre names recurring promotion and loyalty mechanisms without proving account-specific value. Coverage gaps: effective VIP value and expiry. |
|---|
| 20Privacy and data rights | DocumentedThe privacy policy names Twocent Technology Limited as the company that processes personal data. Section 2 lists account, contact, device, financial, location, government ID, usage and fraud-prevention data. Section 4 allows transfers outside the player's country under Standard Contractual Clauses and Data Processing Agreements. Section 9 allows sharing within the BC.GAME corporate group and with service providers. Section 5 of the privacy policy keeps account data while the account is active. It keeps transaction records for up to 7 years and fraud-prevention data for up to 5 years. It keeps marketing preferences until the player opts out. After those periods the data is deleted or anonymised, unless the law requires longer retention. Section 6 of the privacy policy lists a right to erasure when it is legally applicable, plus rights to access, correction, restriction, objection and portability. The policy does not describe a separate deletion request path. The self-exclusion help article states that permanent self-exclusion is used to close accounts. | Partial evidenceThe policy covers the main data lifecycle but does not publish a fixed duration for every category. The help centre distinguishes account closure from complete deletion. Coverage gaps: category-level retention schedule. |
|---|
vs
