BC Game Italy: Privacy and Account Data

Profile, Wallet, Casino, Sportsbook, Promotions and Support generate different categories of account data. Share only what is necessary to identify the correct case.

Profile and Login Data

E-mail, phone, username, region and verification status may form part of your account data.

Security and Technical Data

IP address, browser, device, session and 2FA information may be used to protect access and review unusual activity.

Connected Login Providers

Google or Telegram used for Login need their own strong password, 2FA and secure recovery.

Wallet and Payment Data

Address, network, transaction status and withdrawal requests belong to the financial context.

Seed Phrase and Private Key

Never share these control credentials.

Casino History

Round ID identifies a specific game event without exposing the entire history.

Sportsbook History

Ticket ID identifies one sports bet in My Bets.

Promotion Data

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

Cookies and Browser Data

Deleting cookies can end a session, but it does not delete the account.

Device Changes

Changing phone or browser changes the access point, not the server-side records attached to the profile.

Verification Documents

Upload identity documents only through an official Verification flow or another secure channel explicitly confirmed by the service.

Data Minimisation

Screenshots

Crop the image to the relevant error or status. Hide e-mail, addresses, QR codes and unrelated account information.

Shared Devices

Log out, use screen lock and avoid saving credentials in shared browsers.

Account Recovery

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

Public Blockchain Data

A TxID can be visible on-chain, but linking it publicly to your name, e-mail and balance creates additional personal context.

Formal Privacy Requests

A formal data request may require identity verification different from an ordinary technical support issue.

GDPR

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

Support Records

Ticket ID, Round ID and TxID identify events. They are not substitutes for passwords, seed phrases or identity documents.

Payment Cases Start Small

TxID, asset, network, amount and time are usually enough for an initial review. Never send a seed phrase or private key.

Sportsbook Cases Start with Ticket ID

One Ticket ID identifies a single bet more cleanly than a screenshot of the whole My Bets history.

Casino Cases Start with Round ID

Round ID, game title and approximate time isolate the relevant round without exposing unrelated Casino History.

Promotion Cases Use Campaign Data

Campaign name, Claim time, Rollover and exact error are more relevant than Wallet information when the problem concerns a reward.

Connected Login Needs Its Own Protection

Google, Telegram or e-mail used for Login should have strong passwords, 2FA and secure recovery.

Autofill on Shared Devices

A browser that stores credentials can reopen an account automatically. Disable autofill or remove saved credentials on shared hardware.

Verification Documents Need a Clear Purpose

A technical problem does not automatically justify identity documents. Upload them only when the official Verification flow requires them.

Real Logout Matters

Closing a tab can leave the session active. Use Logout on any device other people may access.

Password Manager

A unique password stored in a password manager reduces the risk that a breach elsewhere affects this account.

Recovery Codes

2FA recovery codes are access credentials. Keep them out of Support chats and ordinary screenshots.

Account Deletion Is Not App Deletion

Removing an app, cookies or shortcut changes local access only. It does not automatically create a formal account-deletion request.

Use the Right Channel

Use Support for product issues and the appropriate privacy route for formal data requests. Keeping the channels separate reduces unnecessary sharing.

Connected Login Can Become the Weakest Link

If you sign in through Google or Telegram, weak recovery or poor security on that account can affect BC.GAME access too. Protect the full login chain.

Public Blockchain Does Not Mean Public Profile

A TxID may be visible on-chain, but publishing it next to your name, e-mail and balance creates unnecessary personal context.

Screenshots Should Show Only the Problem

Crop the image to the relevant error or status. Avoid exposing your inbox, full Wallet, unrelated tickets or personal data.

Formal Requests and Support Cases Are Different

A formal data request can require identity verification and a dedicated privacy route. A game or payment issue normally starts from its event ID instead.

Case IDs Reduce Repeated Sharing

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

Do Not Reuse Identity Documents Without a Reason

If a document was already uploaded for Verification, do not send it again in a technical chat unless the official process explicitly asks for it.

Minimal Data Also Makes Support Faster

The more precise the reference, the less extra information is needed. One correct ID often removes the need for broad screenshots or full histories.

Device Permissions Do Not Change Account History

Turning off notifications or camera access changes the local device only. Wallet, My Bets, Bonus and other server-side records remain attached to the profile.

Privacy FAQ