BC Game Denmark Privacy Policy

BC Game Denmark uses different categories of account information because login, Wallet, Casino, Sportsbook, promotions and Support serve different purposes.

Profile and login information

• Email or phone
• Username and country code
• Connected Google or Telegram login
• Verification status

These details support registration, login, recovery and account management. The same account remains connected to BC Game Denmark.

Security and technical information

IP address, browser, device, session details and 2FA status can be part of the security context.

This information can help protect access, maintain sessions and detect unusual account activity.

Wallet and payment records

Financial records can include Deposit method, crypto address, network, Transaction status and Withdraw request.

A TxID identifies a blockchain transfer. A seed phrase or private key controls an external wallet and is not needed for routine BC Game review.

Casino and Sportsbook histories

Casino keeps games and rounds, while My Bets keeps accepted Sportsbook tickets and settlement.

Keeping those records separate makes it easier to investigate one round or one ticket without mixing unrelated activity.

Promotion information

Bonuscode claims, VIP status, Rollover, Free Spins, vouchers and expiry can form part of campaign history.

This data describes the reward state rather than a blockchain payment.

Cookies and local browser data

Cookies can support language, session continuity, Security and technical analytics.

Clearing cookies can sign the user out or reset local preferences, but it does not delete the Wallet or My Bets history attached to the profile.

Verification documents

Identity documents should only be provided through the verification flow displayed by BC Game or through a route confirmed by official Support.

For routine cases, a TxID, ticket ID or round ID often gives enough context without broad document sharing.

Connected login providers

When Google or Telegram is used for sign-in, security on that external account also affects access to BC Game.

Google Authenticator adds another layer but does not replace protection of the connected provider.

Shared devices

• Use a screen lock.
• Sign out when the device is shared.
• Keep recovery access available.
• Protect connected Google or Telegram accounts.
• Maintain 2FA when enabled.

Support should use identifiers rather than secrets

UID, TxID, ticket ID, round ID and the exact error message can identify a case.

Passwords, current authenticator codes, seed phrases and private keys are control credentials, not routine Support references.

Responsible Gaming records remain account-side

Self-exclusion and related controls can remain associated with the account across devices.

Changing browser or phone does not remove those records.

Different products create different kinds of records

A Casino round is not the same as a sports ticket, and neither is the same as a blockchain transfer.

Keeping those records separated makes both privacy handling and Support review more precise.

Profile data is primarily about access

Email, phone and connected login providers help identify or recover the account.

They should not be confused with the histories created after the user starts playing, betting or moving funds.

Wallet identifiers and wallet secrets are very different

A TxID helps locate a transfer without granting control over the external wallet.

A private key or seed phrase can grant control and should not be treated as evidence for a routine Support case.

Promotion data can change without money moving

A Bonuscode claim, VIP update or Rollover change can alter the profile without creating a blockchain transaction.

That is why campaign history and Transaction history remain separate.

Cookies are local; the account is not

Clearing browser data can remove a local session or preference.

It does not erase account-side Wallet records, tickets or bonus history when the same profile is opened again.

Connected login providers create their own security responsibility

Someone using Google or Telegram should protect that account as well as BC Game.

2FA adds another layer, but it cannot compensate for losing control of the connected provider.

Shared devices need simple session discipline

Signing out and using a device lock matter even when the password itself remains secret.

An already authenticated browser can expose the account without anyone ever learning the password.

Use the smallest useful data set for Support

A precise identifier often removes the need for broad screenshots or unrelated account information.

This keeps the request easier to understand and reduces unnecessary data sharing.

Privacy becomes practical when each record has a clear purpose

A transfer review should start with payment data, a sports review with ticket data and a Casino review with round data.

That keeps the information shared proportional to the question.

Deleting a shortcut is not the same as deleting account data

Home Screen icons and cookies are local access tools.

Wallet balances, tickets and promotion history remain associated with the profile after those local items are removed.

Security data and gameplay data should not be treated as one category

Login and device information protect access, while rounds and tickets describe product activity.

Keeping those purposes distinct makes both privacy explanations and Support requests clearer.

The safest routine is to share only what identifies the case

An exact ticket, round or transaction reference is often enough to start.

More sensitive information should only be provided when the official verification process genuinely requires it.

Privacy information should remain readable

Users should be able to understand why a piece of data exists without reading legalistic explanations for every field.

Clear categories make the policy more practical.

BC Game privacy should stay connected to real account actions

Registration, payments, tickets, game rounds and Support each create different records, so the policy is clearer when those purposes remain separated.

Privacy FAQ