BC Game Australia Privacy and Account Data

BC.GAME handles different data because Registration, Wallet, Casino, Sportsbook, promotions and Support perform different jobs. Privacy is easiest to understand when each data category is connected to the action that created it.

Profile and Login Data

E-mail, phone, username, country or region, connected login provider and verification status can belong to the profile layer.

Security and Technical Data

IP address, browser, device, session information and 2FA status can form part of account security and fraud-prevention context.

Connected Login Providers

If Google or Telegram is used for Login, protecting that external account is part of protecting BC.GAME access.

Wallet and Payment Data

Deposit method, crypto address, network, transaction status and withdrawal request belong to the financial record. TxID can identify a blockchain transfer without giving wallet control.

Seed Phrase and Private Key

Seed phrase and private key can control an external wallet. They are not routine support data and should remain private.

Casino History

Casino activity creates game and round records. Round ID is the strongest first reference when one specific game result needs to be checked.

Sportsbook History

Sportsbook creates ticket and settlement data. Ticket ID identifies the accepted bet more precisely than a screenshot of a changing event page.

Promotion Data

Promo Code claims, VIP status, Rollover, Free Spins, vouchers and expiry form a different record type from payment history.

Cookies and Local Browser Data

Cookies can store language, session and local preferences. Clearing them can sign the user out but does not automatically erase server-side Wallet, My Bets or Bonus history.

Device Changes

A new phone or browser changes the local access point. Correct Login should restore account-side records.

Verification Documents

Identity documents should be uploaded only through the official verification process or another secure route explicitly confirmed by Support.

Data Minimisation in Support

A precise reference usually gives Support more useful context than a full account screenshot.

Screenshots

Review screenshots before sending them. Hide unrelated e-mail addresses, wallet addresses, QR codes or identity details. Never expose seed phrase, private key or live authentication codes.

Shared Devices

Closing a tab is not always the same as signing out. Use Logout on shared devices and avoid saving credentials where other people have access.

Account Recovery

Recovery e-mail and connected social logins deserve the same protection as the main password. Losing control of them can affect account access.

Australian Privacy Context

BC.GAME's international privacy policy states that Twocent Technology Limited processes personal information under applicable privacy frameworks. That does not replace any Australian legal rights or obligations that may apply to a service offered in Australia.

Local Data vs Account Deletion

Deleting an app, Home Screen shortcut, cache or cookies changes local device state. Formal account deletion or privacy requests are separate account-side processes.

Use the Smallest Useful Data Set

For a Sportsbook case, start with Ticket ID. For Casino, start with Round ID. For crypto, use TxID, asset, network and amount. This usually provides better context than a broad screenshot.

Public Blockchain Data and Wallet Secrets Are Different

A TxID or public address can be visible on a blockchain. A seed phrase or private key can control the wallet. Support needs references, not control credentials.

Formal Privacy Requests Can Need Extra Verification

A formal data-access or deletion request may require stronger identity checks than an ordinary gameplay question because the service needs to confirm the requester is the account holder.

Recovery Accounts Need Protection Too

An e-mail, Google or Telegram account linked to Login can become a recovery route. Protect it with strong credentials and its own security controls.

Device Security Supports Account Privacy

A device lock, current software and proper Logout reduce the risk of an active session being used by someone else. Privacy is not only about what the service stores; it is also about who can reach the open account.

Promotion Support Uses a Different Data Set

A bonus case usually starts with campaign name, claim time and exact message. Wallet secrets and unrelated identity documents are not the first-line evidence for a promotion issue.

Browser Permissions Are Local

Notification permission, saved login state and Home Screen shortcuts belong to the device. Turning them off changes convenience, not the underlying server-side account history.

Data Requests and Game Support Are Different Processes

A formal privacy request can require stronger identity verification because it concerns access to personal data. A routine game, bet or transaction question should begin with the narrow event reference instead.

A Shared Device Needs a Real Logout

Closing the browser is not always enough. On a shared computer or phone, use Logout and avoid saving credentials if other people can access the device.

Round ID and Ticket ID Reduce Oversharing

These references let Support locate one event without requiring you to expose an entire account screen. Precision is useful for both privacy and troubleshooting.

Keep Recovery Information Separate From Support Evidence

Recovery codes, backup methods and account-control credentials are designed to restore access, not to prove a particular bet or transaction. Keep them private and use event references for ordinary support.

Privacy Is Also About Context

Sharing the right identifier with the right team is often safer than sharing more information. A narrow, well-labelled support request reduces unnecessary exposure and makes the record easier to review.

Use Official Routes for Sensitive Data

If identity or account documents are genuinely required, upload them only through the official verification route or a secure channel confirmed by Support, not through a public message or forum.

Precision Protects Privacy

A short request with the correct reference usually exposes less unrelated information and gives Support a clearer route to the record that actually needs review.

Privacy FAQ