BC Game Costa Rica Privacy Policy: Data, Cookies and Security

Privacy across account use

This Privacy Policy overview covers information categories connected with account access, payments, Casino and Sportsbook activity, promotions, support and technical use on BC Game Costa Rica.

Players should also read the current Privacy Policy and Terms inside the official BC.GAME platform because verification rules, payment checks, cookie settings and support procedures can change.

Registration and security information

Registration details can include email, phone number, username, country code or a linked social account. Security details can include IP address, browser, device, login session and two-factor authentication status.

These records support account access and security checks across mobile and desktop.

Payment information

Payment details can include deposit method, cryptocurrency wallet address, transaction status, withdrawal request and payment verification.

TxID/hash identifies a blockchain transaction. A private key or seed phrase controls a wallet and should not be shared with Support.

Casino and Sportsbook records

Casino activity can create round records and game identifiers. Sportsbook creates tickets containing markets, odds, stake and settlement status.

When a question concerns one event, use the relevant identifier rather than sending unrelated account history.

Bonus and promotion data

Promotion information can include claimed offers, wagering progress, Promo Code use, cashback, VIP or loyalty status and expiry.

Rollover provides the account view of promotional wagering and should be kept separate from ordinary cash Transaction history.

Support communications

Support records can include messages, screenshots, account recovery requests and technical reports.

A focused screenshot that shows the relevant error or identifier is generally more useful than a full account screen containing unrelated information.

Cookies and technical data

Cookies can support page performance, language preferences, login stability, fraud prevention, security checks, analytics and content presentation.

Browser settings can be used to manage cookies. Clearing them can log you out without deleting the BC Game account, Wallet or stored tickets.

Security recommendations

Published security guidance focuses on protecting credentials, account access and transaction details.

1. Use a unique password for BC.GAME.

2. Enable two-factor authentication before depositing funds if you want the additional protection.

3. Do not share your password, private key, seed phrase or recovery code.

4. Check the website address before logging in.

5. Confirm the cryptocurrency network, wallet address and amount before sending a transaction.

Mobile privacy

Mobile access opens the same account and Wallet as desktop, so screen lock, saved-password controls and 2FA remain important.

On a shared or borrowed device, avoid saving credentials and use logout when the session ends.

Verification documents

Identity documents should be submitted only through the official verification flow displayed in the BC Game account.

If a request arrives through an unverified channel, confirm it with official Support before sending documents.

Responsible and lawful use

Users should review current operator details, licence information, Costa Rica availability, restricted-country information, age requirements, Responsible Gaming tools, bonus terms, KYC checks and withdrawal conditions before using real-money features.

Current platform Terms and Privacy Policy are the reference when account requirements or procedures change.

Cookie controls in the browser

Cookies can maintain language preferences, login stability and presentation choices. Browser settings allow the user to manage those cookies.

Clearing them can change the local session without removing the account data stored by BC Game.

Data minimization in Support cases

A support screenshot should focus on the relevant error, identifier or status. Unrelated balances, tickets or addresses do not need to be included unless they are part of the question.

Verification documents follow the same principle: submit them only through the official flow when the platform requests them.

Current terms and responsible access

Privacy and security should be read together with the current Terms, restricted-country information, age requirements, KYC checks, bonus rules and Responsible Gaming tools.

The official BC.GAME Privacy Policy and Terms remain the reference for account use in Costa Rica and for any requirements that may be updated.

Privacy across multiple browsers

Different browsers can keep separate cookies and authenticated sessions on the same device. Logging out in one browser does not necessarily close another.

Review the browsers you actually use and avoid leaving saved credentials on shared or borrowed hardware.

Support communication can be kept case-specific

A support message should include the identifier and context needed for the issue at hand. There is no benefit in attaching unrelated betting or payment history.

If more evidence is necessary, Support can request it within the same case.

Verification and account documents

Identity documents should stay inside the official verification flow shown by BC Game. A request received through an unverified route should be confirmed before documents are sent.

This keeps account verification connected to the platform process rather than to an external message.

Browser state and account state are different

Cookies, saved sessions and local preferences affect how the browser behaves, while the account records remain on BC Game. Clearing a local session can require another login without removing Wallet, My Bets or Transaction history.

Keep support evidence relevant to the issue

If a case concerns one transfer, ticket or round, start with that identifier and the surrounding facts. Support can request additional evidence if the initial information is not enough.

Privacy also applies to promotional information

Bonus and VIP records can reveal wagering progress, campaign history and account status. When Support only needs one promotion reviewed, share the campaign and relevant Rollover details rather than unrelated reward history.

Privacy FAQ