BC Game Saint Martin Privacy Policy

Information connected with the profile

Privacy-related information can include registration, Security, payments, Casino, Sportsbook, promotions and Support communication.

Registration can include email, phone number, username, country code or a connected login method. Recheck the Security controls on BC Game Saint Martin whenever you replace a device or linked login.

Security records can include IP address, browser, device, session and 2FA status.

Wallet and payment records

Payment information can include Deposit method, crypto address, Transaction status, Withdraw request and payment verification.

TxID identifies a blockchain transaction. Seed phrases and private keys control wallets and are not required for a normal Support review.

Rollover can exist alongside Transaction when a promotional balance has wagering conditions.

Casino and Sportsbook histories

Casino creates game and round records. Sportsbook creates tickets and settlement history under My Bets.

Keeping those histories separate lets a specific outcome be reviewed without treating the whole profile as one record.

It also distinguishes gaming results from money movement in Wallet.

Promotion data

Promotion records can include claimed offers, Bonuscode use, VIP status, wagering progress and expiry.

Those records determine which reward is active and which rules apply to it.

Promotion history and financial Transaction history can affect the same balance while serving different purposes.

Cookies and technical information

Cookies can support site performance, language preference, login stability, fraud prevention, security checks and technical analytics.

Browser settings can manage them. Clearing cookies can sign the session out without deleting the BC Game profile.

The current Privacy Policy and Terms remain the source when technical procedures change.

Account security

Use a unique password and enable 2FA when you want an additional account-protection layer.

Check the site address before entering credentials, especially after opening a promotion link.

Before sending crypto, confirm network, wallet address and amount.

Verification documents

Identity documents should be submitted only through the verification flow displayed inside the profile.

Support does not need a seed phrase, private key or current Authenticator code to review an ordinary payment or promotion question.

An unusual request can be confirmed through official Support before documents are sent.

Connected login methods

When Google or Telegram is used for login, the security of that provider also affects access to BC Game.

BC Game 2FA adds another layer but does not replace security on the connected provider account.

Recovery information should remain current.

Mobile and shared devices

Mobile opens the same Wallet as desktop, making device access part of profile security.

On a shared device, avoid saving credentials and end the session when finished.

Screen lock, verification and 2FA can work together as separate protection layers.

Responsible and lawful use

Before real-money play, review current Terms, age requirements, restricted-country information, verification rules and Responsible Gaming tools.

The Anjouan international licence should remain separate from local availability or legal questions in Saint Martin.

Responsible Gaming controls remain available alongside Casino, Sportsbook and Wallet.

Information categories

Support communication can contain account data

A Support case can include UID, TxID, ticket ID, round ID or verification context when those details are relevant.

Starting with the exact record keeps unrelated profile information out of the conversation.

Secrets that control the account or wallet, including current 2FA codes, seed phrases and private keys, are not needed for normal review.

Promotion records are a separate privacy category

Bonuscodes, VIP rewards and Rollover create promotion information that is different from ordinary payment history.

Those records can show which campaign was claimed, what wagering remains and when the reward expires.

Wallet can reflect the financial result while Rollover preserves the campaign logic behind it.

Current Terms complement the Privacy Policy

Verification procedures, payment checks, cookie behavior and access requirements can evolve.

The current Privacy Policy and Terms are therefore the appropriate reference when a live requirement differs from an older instruction.

The same principle applies to location restrictions and Responsible Gaming tools.

Technical data can support session continuity

Browser, device, IP and session information can help the platform maintain login state, apply security checks and identify unusual access patterns.

Cookies can also store preferences such as language or presentation behavior.

Those technical records do not replace the player's password or 2FA; they support the way the session operates.

Connected providers create another access relationship

When Google or Telegram is used to sign in, that provider becomes part of the route into BC Game.

BC Game 2FA adds another layer after the connected login, but the external provider account should remain protected as well.

Keeping recovery information current supports access if the normal route later needs to be restored.

Payment data and gaming data serve different purposes

Deposit and Withdraw records describe movement of funds, while Casino rounds and Sportsbook tickets describe gaming outcomes.

Separating them helps the platform review a payment without treating it as a game result, or review a ticket without exposing unrelated Wallet activity.

That distinction is one of the practical reasons privacy information is organized by category.

Cookies, session state and preferences

Cookies can support language preference, presentation choices and continuity of login. Clearing them can require a new sign-in without removing the BC Game profile or Wallet.

Those browser-level settings are separate from Casino history, My Bets and Transaction records, which remain part of the account.

Session access and privacy

A signed-in browser or connected Google/Telegram account can provide a route back into the same BC Game profile. Session access is therefore part of account privacy as well as convenience.

Password security, 2FA and recovery information work together to keep that access under the account holder's control.

Privacy FAQ