BC Game Spain: Privacy and Account Data

BC Game account activity can generate different categories of data across Profile, Wallet, Casino, Sportsbook, Promotions and Support. Share only the information needed to identify the specific case you want reviewed.

Profile and Login Data

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

Security and Technical Data

IP address, browser, device, session and authentication information can be used to protect account access and review unusual activity.

Connected Login Providers

If you use Google or Telegram to sign in, secure those services too. Strong passwords, 2FA and safe recovery matter because they can become another route into the same BC Game account.

Wallet and Payment Data

Address, network, amount, transaction status and withdrawal request belong to the financial context. For a payment issue, start with TxID rather than exposing unrelated wallet information.

Seed Phrase and Private Key

BC Game Support does not need these wallet-control credentials. Never share them.

Casino History and Round ID

Round ID identifies one game event without requiring you to expose the whole Casino History. Add the game title and approximate time only when useful.

Sportsbook History and Ticket ID

Ticket ID points to one bet in My Bets and usually gives cleaner context than a screenshot containing several other tickets.

Promotion Data

Campaign name, claim time, VIP, Rollover, expiry and exact error belong to the promotion context. Do not add wallet data unless a payment is directly involved.

Cookies and Browser Data

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

Changing Devices

A new phone or browser changes the access point, not the server-side records attached to the profile. With the same login, your histories should remain available.

Verification Documents

Upload identity documents only through an official Verification flow or another secure channel explicitly confirmed by the service. A question about a game round or bonus does not automatically require identity documents.

BC Game Data Minimisation

Screenshots

Crop screenshots to the relevant error or status. Hide e-mail addresses, QR codes, unrelated balances, other tickets and any personal details that do not help resolve the case.

Shared Devices

Use a real Logout, screen lock and careful browser settings. Closing a tab does not always end a session, and saved credentials can reopen an account later.

Account Recovery

Protect recovery e-mail and connected accounts as carefully as the main login. Weak recovery can undermine a strong password.

Public Blockchain Data

A TxID can be visible on-chain, but connecting it publicly with your name, e-mail and account balance adds personal context that usually is not necessary.

Formal Privacy Requests

A formal data-access or deletion request can require identity verification and a dedicated privacy route separate from ordinary product Support.

GDPR and BC Game

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

Start Payment Cases with the Transaction Reference

TxID, asset, network, amount and approximate time usually give enough context for an initial payment review. Seed phrases and private keys are not required to identify the transfer.

Ticket ID Is Better Than a Full Sportsbook Screenshot

One Ticket ID points to one sports bet. A screenshot of the entire My Bets history may expose unrelated wagers without helping the case.

Round ID Limits Casino Data Sharing

Round ID, game title and approximate time can isolate one casino event. Start there before sharing wider Casino History.

Promotion Cases Need Campaign Data

Campaign name, claim time, Rollover and exact error are the natural starting points for a bonus issue. Wallet information should only be added when a payment is genuinely involved.

Connected Logins Need Their Own Security

If you use Google or Telegram, protect those accounts with strong passwords, 2FA and secure recovery. They can become an alternative route into the same BC Game profile.

Screenshots Should Be Cropped Before Sending

Show the error or status that matters and hide e-mail addresses, QR codes, balances and unrelated records. A smaller screenshot is often both safer and clearer.

Case IDs Reduce Repeated Data Sharing

If Support gives you a case ID, keep it. You can continue the same review without resending the same screenshots or documents.

Password Managers Reduce Credential Reuse

Using a unique BC Game password and storing it in a reputable password manager can reduce the risk that a breach on another service affects the same account. Reused credentials make unrelated services part of the same security problem.

2FA Recovery Codes Are Sensitive Access Credentials

Recovery codes can restore access when the normal 2FA method is unavailable, so keep them out of Support chats and ordinary screenshots. Store them privately and separately from the device you normally use to log in.

Logging Out Matters on Shared Devices

Closing the browser tab may leave the session active. On a shared computer or phone, use Logout and check whether the browser has stored passwords, autofill or another shortcut that could reopen the account.

Use the Right Channel for the Right Type of Request

A product issue, payment review and formal privacy request may require different information and different handling. Keep the request focused on its purpose so you do not share identity documents or financial data where they are not needed.

Privacy FAQ