BC Game France Privacy and Account Data

Profile, Wallet, Casino, Sportsbook, Promotions and Support generate different categories of data. The most practical privacy rule is to share only what is needed to identify the specific action under review.

Profile and Login Data

E-mail, phone, username, region, connected login provider and verification status can belong to the account profile. They support registration, login, recovery and account management.

Security and Technical Data

IP, browser, device, session information and 2FA state can be part of the security context. A new device can trigger additional checks without creating a new account.

Wallet and Payment Data

Crypto address, network, transaction status and withdrawal requests belong to the financial layer. TxID identifies a blockchain transfer but does not provide control over the wallet.

Seed Phrase and Private Key

These are control credentials, not support references. They should not be sent in a chat, screenshot or support ticket.

Casino and Sportsbook Histories

Round ID identifies a specific casino event, while Ticket ID identifies a sports bet. Both are more precise than sharing a full history page.

Promotion Data

Claim history, VIP state, Rollover and expiry can create a separate promotional record. A bonus issue therefore needs different evidence from a payment issue.

Cookies and Device Changes

Clearing cookies can end a local session, but it does not erase Wallet, My Bets or server-side account records. Changing device also changes access, not ownership of the profile.

Verification Documents

Identity documents should be uploaded only through an official verification flow or a secure route explicitly confirmed by the service. A normal game or payment question does not automatically require an identity document.

Data Minimisation

Screenshots

Crop the image to the useful message. Hide unrelated e-mail addresses, wallet addresses, QR codes and account data when they are not needed for the case.

Shared Devices and Recovery

Use Logout on shared devices, protect recovery e-mail and connected Google or Telegram accounts, and avoid saved credentials in a browser that other people can access.

France and GDPR Context

BC.GAME’s current Privacy Policy states that personal data is processed under applicable privacy frameworks including GDPR where relevant. Formal privacy requests can require a different identity-verification process from ordinary game or support cases.

Payment Cases Usually Need a Small Data Set

TxID, asset, network, amount and approximate time are often enough to start a payment review. Seed phrase and private key add control risk without helping identify the transaction.

Sportsbook Cases Should Be Ticket-Specific

A single Ticket ID is generally more useful than a screenshot showing the whole My Bets page. It identifies one accepted record and avoids exposing unrelated bets.

Casino Cases Benefit from Round ID

Round ID, game title and approximate time isolate a game event without requiring the full Casino History. Precision reduces oversharing and usually speeds up review.

Promotion Support Uses Different Data

Campaign name, claim time, Rollover and the exact message are more relevant to a reward issue than payment information. Use the reference created by the product you were actually using.

Shared Devices Need Real Logout

Closing a tab may leave the session active. On a shared computer, use Logout and avoid browser autofill for account credentials. Device privacy is part of account privacy.

Connected Login Providers Expand the Security Surface

If Google or Telegram is used for Login, protect that account with strong recovery and 2FA. The BC.GAME password is not the only access point when a connected provider is involved.

Recovery Codes Are Not Evidence

Recovery codes and live 2FA codes are access credentials. They do not prove that a payment, game round or sports ticket exists, so they should never be sent as support evidence.

Official Channels Matter More Than Speed

Sending a sensitive document quickly through the wrong channel is worse than taking an extra minute to open the official verification or privacy route. Sensitive data should always have a clear destination and purpose.

Account Deletion Is Separate from Local Cleanup

Deleting an app, clearing cookies or logging out changes local access. It does not automatically begin a formal account-deletion process or erase server-side histories. Those actions should not be confused with each other.

Notifications and Browser Permissions Are Local Settings

Turning off notifications, camera permission or other browser permissions does not delete account-side data. These settings change how the device interacts with the service, while Wallet, My Bets and Bonus records remain tied to the profile.

A Good Support Message Protects Privacy by Being Structured

Problem, approximate time, the relevant reference and the exact message are often enough to begin. A structured request reduces the temptation to attach full screenshots or unrelated personal data just to make the case look more complete.

Share the Smallest Useful Set of Data

Use TxID for a transfer, Ticket ID for a sportsbook ticket, Round ID for a game round and campaign details for a reward issue. A precise reference usually avoids the need to expose unrelated account history.

Keep Control Credentials Out of Support Messages

Password, seed phrase, private key, recovery codes and live 2FA belong only to you. They do not prove a payment, game result or promotion claim and should never be used as ordinary support evidence.

Protect Recovery as Carefully as Login

If your account uses a recovery e-mail, Google or Telegram, protect that route with its own strong password and 2FA where available. A well-protected BC Game password is not enough if a connected account can be recovered or accessed too easily.

Use Official Channels for Sensitive Documents

Verification documents belong only in the official Verification flow or another secure route explicitly confirmed by the service. Do not send identity files through public forums, social replies or unrelated support conversations.

Privacy FAQ