BC Game Iceland Privacy and Account Security

Keep Your BC Game Iceland Account Secure

Our live Privacy Notice and Terms explain how we process, verify and retain data and how you can make a rights request. You can directly control: sign-in identity, password, 2FA, sessions, Wallet references, promotion records and betting history.

Email, phone, Google and Telegram identity

Link your account to an email address, phone number or connected provider you control. Protect the underlying email, SIM and provider account because access to that route can support password recovery. Do not create duplicate profiles to work around a lost login; use the official recovery and support process.

Email verification

1. Open Security from the authenticated account.
2. Check the address displayed by the account.
3. Request the official verification message.
4. Open the message only after checking the sender and destination domain.
5. Complete verification and return to Security to confirm status.

Google Authenticator 2FA

1. Verify the required email or phone route first.
2. Open the 2FA setup control in Security.
3. Scan the displayed secret with the authenticator app.
4. Store the recovery secret offline and privately.
5. Enter a fresh six-digit code to complete setup.
6. Test sign-in before ending the original session.

Withdrawal restrictions after security changes

Our published instructions state that a password change can restrict withdrawals for 24 hours. Disabling 2FA can also create a 24-hour restriction. The delay separates a security change from an immediate payout attempt and gives the account owner time to react.

Use Your Account Records to Stay Protected

Information to preserve for support

• Asset, network, amount, address and time for a crypto transaction.
• Memo, Tag or Destination ID when the network uses one.
• Bet ID, event, market, accepted odds and stake for a sportsbook case.
• Game, provider, Round ID and displayed result for a casino case.
• Campaign name, activation time and Rollover status for a bonus case.

Send Crypto with the Right Network Details

A blockchain address may not display a legal name, but transactions are public and normally irreversible. Verify asset, exact network, destination and secondary destination data. ERC20 and TRC20 are different USDT routes. XRP, XLM and EOS can require Memo, Tag or Destination ID.

Protect Your Session on Every Device

Your browser can keep authentication and preference data. Sign out on a shared device, do not save the password in an unmanaged browser and remove the BC.GAME session when finished. Clearing cookies can end a session but does not delete server-side account and transaction records.

Spot Phishing before You Sign In

• Read the full domain before entering an identifier.
• Do not trust a shortened link from an unsolicited private message.
• Open mirrors through a verified BC Game route.
• Reject pages requesting a wallet seed phrase or private key.
• Do not approve a transaction simply to “verify” an account.

Before entering a password or 2FA code

Confirm the domain, HTTPS connection and context of the request. A 2FA code belongs only in the current official sign-in or security screen. We can identify your case using account references and should not ask you to send a live code in chat or email.

What We Will Never Ask You to Share

Secure Your Account after Suspicious Activity

1. Secure the linked email, phone or provider account.
2. Change the BC.GAME password through the official route.
3. Review Security and remove unfamiliar sessions.
4. Keep relevant Transaction, Bet ID and Round ID references.
5. Contact Live Support with timestamps and factual details.
6. Expect the published security hold when a password or 2FA setting changes.

Use a different password for BC.GAME, email and external wallets. Reuse turns one leaked credential into access across several services and can undermine recovery even when 2FA protects only one account. Keep recovery secrets offline and separate from the device that displays the ordinary six-digit authenticator code. Anyone holding both the device and recovery secret could defeat the separation that two-factor authentication is intended to provide.

When you send us a screenshot, crop it to the relevant status while keeping its timestamp and reference. Remove QR secrets, full recovery keys, passwords, current authenticator codes and unrelated personal messages. A masked account identifier can help support locate a profile without publishing the full email or phone number. Support can ask for the exact masked value shown by the account and then confirm the authenticated route for any further verification.

Public blockchain explorers reveal addresses, amounts and confirmation status. Share a TxID only with the official case that needs it and never sign an unrelated wallet message or transaction merely because a person claims it is required for lookup. Transaction references should be copied from the authenticated record to avoid transcription errors in a time-sensitive case. For a crypto case, verify the hash on the selected network explorer before copying it into the private support conversation.

When a device is lost, secure the connected email, SIM and provider first, then use the official BC.GAME recovery route. Review sessions and Wallet records, preserve unfamiliar references and contact Live Support with exact times. After recovery, rotate reused credentials on every affected service rather than treating the BC.GAME password change as sufficient. Also review connected-provider sessions and email forwarding rules, because an attacker can otherwise regain access after the platform password changes.

Connected Google or Telegram access should be reviewed at both ends. Remove an unfamiliar BC.GAME session in Security and also review authorised applications in the connected provider account.

Device notifications can expose account activity on a locked screen. Configure notification previews, protect email and SMS recovery, and avoid receiving one-time codes on a device that other people can unlock.

Send your privacy or rights request through the official channel named in our live Privacy Notice. State the account identifier and requested action precisely, but do not attach unrelated identity or financial data before the service confirms what is required.

BC Game Iceland privacy FAQ