BC Game Costa Rica Privacy Policy

Privacy across BC Game Costa Rica

This Privacy Policy overview covers information categories connected with registration, security, payments, Casino and Sportsbook activity, promotions, support and technical use.

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

Registration and security data

Registration information can include email, phone number, username, country code or a linked social account.

Security information can include IP address, browser, device, login session and two-factor authentication status. These records support access protection across mobile and desktop.

Payment information

BC Game can associate deposit method, cryptocurrency wallet address, transaction status, withdrawal request and payment verification with the account.

TxID/hash identifies a blockchain transaction. Private keys and seed phrases control an external wallet and should not be shared with Support.

Casino and Sportsbook records

Casino can generate round history and game identifiers. Sportsbook generates tickets containing markets, odds, stake and settlement information.

When a question concerns one event, the relevant identifier is more useful than unrelated account history.

Promotion and VIP data

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

Rollover separates promotional wagering from ordinary cash and Transaction history.

Support communications

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

A screenshot focused on the relevant error, ticket, round or transaction can reduce the amount of unrelated personal information shared.

Cookies and technical data

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

Browser settings can manage cookies. Clearing them can log the browser out or reset local preferences without deleting the BC Game account, Wallet or stored tickets.

Security recommendations

BC Game security guidance focuses on protecting credentials, wallet secrets and transaction details.

1. Use a unique password for BC.GAME.

2. Enable two-factor authentication 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 BC Game account as desktop. Screen lock, saved-password controls and 2FA remain relevant on the smaller device.

On a shared or borrowed device, avoid saving credentials and use logout when the session ends. Closing a tab does not necessarily close every authenticated session.

Verification documents

Identity documents should be submitted only through the official verification flow shown inside the BC Game account.

An unusual document request received through an unverified route should be confirmed with official Support before anything is uploaded.

Local copies and cloud backups

Downloads, Photos and cloud backup can retain screenshots or documents used during a support case. Files that are no longer needed can be removed after the case is resolved.

Deleting a local copy does not erase the official account records retained by BC Game.

Responsible and lawful use

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

BC Game can update Terms and policies. The live platform version is the reference when account or payment requirements change.

Cookies, browsers and active BC Game sessions

One device can hold separate authenticated sessions in Chrome, Safari or other browsers. Logging out in one does not always close the others.

On a shared device, review the browsers used and remove saved credentials that are no longer needed.

Data minimization in BC Game Support cases

A crypto case should begin with the transfer, a Sportsbook case with the ticket and a Casino case with the round. Sharing only the relevant record keeps the review focused and limits exposure.

If BC Game Support needs more information, it can request it inside the same case instead of receiving the entire account history in advance.

Privacy of promotion and VIP records

Campaign history, Rollover progress and VIP status are also account activity. A question about one promotion does not require every previous reward to be disclosed.

Campaign name, reward type and the current Rollover state usually provide a suitable starting point.

Local files after a BC Game support case

Downloads, Photos and cloud backups can retain screenshots or verification files after the account issue has been resolved. Copies that are no longer needed can be removed without changing the official records kept by BC Game.

On a device that will be shared, repaired or sold, saved passwords and authenticated browser sessions should also be reviewed.

BC Game account records and purpose limitation

A transaction identifier should be used for the transaction it describes, a ticket ID for the sports bet it describes, and a round ID for the Casino result it describes.

Keeping each identifier tied to its purpose reduces the amount of unrelated account information needed in a support conversation.

Local device data versus BC Game account data

A browser cookie, saved screenshot or downloaded file belongs to the local device, while My Bets, Transaction, Rollover and other account records remain on the BC Game platform. Clearing one does not automatically erase the other.

BC Game Privacy FAQ