Sports / Mobile
v6bet is clear about what data we collect, why we collect it, and how you can review or correct it at any point. Access to our platform and the rights described here depend on your local law and eligible regions.
This privacy policy sets out the categories of information v6bet collects when you create an account, access the lobby, or complete a transaction through a supported payment method. When you use bKash, Nagad, or Rocket to fund your account wallet, we receive transaction reference data — not your full wallet credentials — solely to match the payment against your account record. We collect device and session data so your account state persists correctly whether you switch from a mobile browser to a different handset or return after a break. Account registration data includes the identifiers you enter during sign-up: your contact detail, a chosen login credential, and any verification steps shown in the account form at the time. We retain this data for as long as your account remains active and for a further period as required by the applicable rules in your eligible region. Deletion or correction requests are handled through the support routes listed in this policy. We do not sell your personal data to third parties for their own marketing purposes. Where we share data with service partners — for example, payment processors handling bKash or Nagad transfers — those partners receive only what is necessary to complete the function they perform.
Not every service connected to your v6bet experience falls under this policy. Understanding the boundary helps you know where to direct a data question — and where you need to look at a third party's own terms instead.
Login activity, session history and account-level settings are covered fully by this policy. Any data generated when you sign in, switch devices, or update your account details sits within our scope and can be reviewed through the support routes described below.
Transaction reference data processed through bKash, Nagad or Rocket is covered here in respect of how we store and use it on our side. The payment provider's own handling of your wallet credentials is governed by their separate policy, not ours.
Browsing behaviour within the lobby — which game categories you open, how long a session lasts — is collected as usage data covered by this policy. We use it to keep your session state intact across devices, not for external advertising.
Links or embedded tools that take you outside v6bet — such as a payment gateway interface or an external verification service — are outside this policy's scope. Those services operate under their own data terms, which we encourage you to read before proceeding.
You have concrete options when it comes to the data we hold on your account. First, you can review your account record directly by signing in and opening the account detail section — what you entered at registration is visible there, and you can see the contact information linked to your login. If something is incorrect, the account settings page shows the fields you can update yourself; for changes that require verification, the process is described in the form that appears when you request the edit. Raising a question about how we use your data is handled through our support routes — the live chat and email paths listed in the contact section of this policy are the right place to start. If you want to request deletion of your account data, that request goes to the same support channel; we will confirm receipt and outline the steps that follow, including any retention obligations that apply in your eligible region under local rules.
Sign in and open your account detail page. Your registration data — contact detail, login identifier and any verification entries — is displayed there. What you see is the data we hold for your active account at that point in time.
Fields that you can edit directly are available in account settings. For corrections that need identity verification first, the account page shows the required steps. Follow the instructions shown in the form rather than contacting support for those routine updates.
Send your question through live chat or email — both routes are listed in the support section below. Include your account identifier so we can locate the right record. We aim to respond through the same channel you used to contact us.
A deletion request is submitted through the support channel. We confirm receipt, explain any retention period that local rules require us to observe, and then process the removal of data we are permitted to delete once those obligations are satisfied.
If your question is specifically about how we handle, store or process your data, these are the routes to use. Choose the one that works best for your situation — each path reaches the same team.
Open the live chat widget on the v6bet site while signed in. Identify your query as a privacy or data question so it reaches the right team member. This is the fastest route for account-specific questions.
Send your data or privacy question to our published support email address. Include your account identifier in the message. Email is suitable for detailed requests, such as a deletion request or a question about retention periods in your eligible region.
The account help section on the site carries answers to common data and settings questions. Check there first for information about what fields you can update yourself, and when a support request is needed instead.
We apply practical, account-level measures to keep your data accurate, limited and accessible only to the functions that need it.
We use cookies to keep your session active and your account state consistent as you move between the lobby, your wallet and account settings. Cookies do not store your payment credentials. You can manage cookie preferences through your browser settings at any time, though disabling certain cookies may affect how the site functions on your device.
Access to your account record is protected by the login credential you set during registration. We do not display full payment reference numbers in your account history — only partial identifiers are shown, so a bKash or Nagad reference appears in a masked format that confirms the match without exposing the full string.
We keep account data for as long as your account is active. After an account closes, we retain only what applicable rules in your eligible region require us to hold. Retention periods vary depending on the type of data — transaction references typically have a longer minimum retention period than browsing session logs.
When this policy changes in a material way, we publish the updated version on this page and note the revision. If you have questions about what changed, or if a change affects a right you previously exercised, reach out through the support routes above and we will clarify the difference.
These are the questions we hear most often about how we handle account data, what your rights are, and how to act on them.
At registration, we collect the contact detail and login credential you enter in the account form, plus any verification information shown as required at that stage. We also collect device and session data so your account state stays consistent when you return from a different handset or browser.
We receive a transaction reference when you fund your account through bKash, Nagad or Rocket — enough to match the payment to your account record. We do not store your full wallet credentials. Your wallet password and PIN remain entirely on the payment provider's side.
Sign in and open your account detail page — your registration data is visible there. For a more complete picture of what we hold, send a request through live chat or email, include your account identifier, and we will confirm the categories of data linked to your record.
Yes. Submit a deletion request through our support channel — live chat or email both work. We confirm receipt, explain any retention period that local rules in your eligible region require us to observe, and then process the removal of data we are permitted to delete once those obligations are met.
Yes. The policy covers your account regardless of whether you access it through a mobile browser or any other supported route. Session cookies and account-state data are collected the same way on mobile. Managing cookies through your mobile browser settings works in the same way as on desktop.
Use live chat on the site or send an email to our support address — both routes are listed in the contact section above. Identify your query as a privacy or data matter so it reaches the right team. For complex requests, email gives you space to explain the detail clearly.