BC Game Slovakia: Privacy and Account Data

We may process different categories of data across Profile, Wallet, Casino, Sportsbook, Promotions and Support. Share only the information needed to identify the specific case.

Profile and Login Data

E-mail, phone, username, region and verification status can form part of account data. Keep passwords and live 2FA codes separate.

Security and Technical Data

IP address, browser, device, session and authentication information can help protect access and review unusual activity.

Connected Login Providers

If you use Google or Telegram for Login, protect those accounts with strong passwords, 2FA and secure recovery too.

Wallet and Payment Data

Address, network, amount, Transaction status and Withdraw request form part of the financial context. Start payment cases with TxID.

Seed Phrase and Private Key

Our Support team does not need these wallet-control credentials. Never share them.

Casino History and Round ID

Round ID identifies one game event without requiring a screenshot of the whole Casino History.

Sportsbook History and Ticket ID

Ticket ID identifies a single bet in My Bets.

Promotion Data

Campaign name, Claim time, VIP, Rollover, expiry and exact error belong to the promotion context.

Cookies and Browser Data

Deleting cookies can end a local session or remove preferences, but it does not delete the your BC Game account.

Changing Devices

A new phone or browser changes the access point, not the server-side histories attached to the profile.

Verification Documents

Upload identity documents only through the official Verification flow or another confirmed secure channel.

BC Game Data Minimisation

Screenshots

Crop screenshots to the relevant error or status. Hide e-mail addresses, QR codes, balance and unrelated tickets.

Shared Devices

Use a real Logout and review saved credentials and autofill. Closing a browser tab does not always end the session.

Account Recovery

Protect recovery e-mail and connected accounts as carefully as the main Login.

Public Blockchain Data

A TxID can be public on-chain, but connecting it publicly with your name, e-mail and balance adds unnecessary personal context.

Formal Privacy Requests

An access, correction or deletion request may require identity verification and a dedicated privacy route.

GDPR and BC Game

The BC.GAME Privacy Policy refers to applicable data-protection frameworks, including GDPR where relevant. Use the current policy for purposes, retention and rights.

BC Game Payment Support: Share the Smallest Useful Data Set

TxID, asset, network, amount and approximate time are usually a strong starting point for a transfer review. Seed phrase and private key are not needed to identify the payment.

If the issue is only status, avoid a full Wallet screenshot that exposes unrelated balance or transaction history.

Our Sportsbook Support: Ticket ID Is Better Than a Full History

One Ticket ID identifies one sports bet. A full My Bets screenshot can expose several unrelated wagers without improving the case.

Add the market or event only when it helps with the specific settlement question.

Our Casino Support: Round ID Limits Oversharing

Round ID, game title and approximate time can isolate a single casino event. There is rarely a need to send the entire Casino History.

If the question concerns one round, keep other game activity outside the request.

BC Game Promotion Support: Start with Campaign Data

Campaign name, claim time, Rollover and exact error are the natural starting details for a reward issue. Add payment information only when Deposit is directly involved.

This keeps financial and promotional context separated.

Connected Accounts Need Their Own Protection

Google, Telegram or e-mail used for Login can become alternate routes into the same your BC Game profile. Protect them with strong passwords, 2FA and secure recovery.

A weak recovery route can undermine an otherwise strong account.

Crop Screenshots Before Sending Them

Full-screen images can reveal e-mail addresses, QR codes, balances, other bets or wallet addresses. Crop everything that does not help the specific case.

A smaller screenshot is often clearer and safer at the same time.

BC Game Case IDs Reduce Repeated Data Sharing

If Support assigns a case ID, keep it and use it in follow-up messages. You should not have to resend the same screenshots, transaction details or documents every time the conversation continues.

A stable case reference improves continuity while reducing unnecessary repeated disclosure.

BC Game Recovery Codes Are Sensitive Credentials

2FA recovery codes can restore access when the normal authentication method is unavailable. Keep them private, store them separately and do not include them in Support chats or ordinary screenshots.

The same care applies to recovery e-mail and connected login accounts because they can provide another route into the profile.

BC Game and Shared Devices

Closing a browser tab does not always end a session. On a shared device, use Logout and review saved passwords, autofill and remembered accounts.

If the browser belongs to someone else, avoid allowing it to store credentials in the first place.

BC Game Formal Privacy Requests and Technical Support Are Different

A request for access, correction or deletion of personal data may require a dedicated privacy route and identity verification. A technical question about a ticket, transfer or round usually needs much less personal information.

Using the right channel helps keep the request focused and reduces unnecessary disclosure.

Privacy FAQ

Does Our Support team need my seed phrase?

No.