Casino / Live
vb808 collects only the account and transaction data needed to run your wallet, process bKash or Upay activity, and keep your account secure. This policy sets out exactly what we collect, why we hold it, and what choices you have — access depends on your local law and eligible regions.
When you open an account with us, we collect the details you enter during registration — your name, contact address, and the payment method you choose to link, such as bKash or Upay. We also record transaction references each time a deposit or withdrawal is processed through your wallet. This is not optional: without it, we cannot match your account to the correct payment rail or resolve a query if something goes wrong. Beyond registration, we log standard browsing data — page paths, session duration, and the device type you use to reach the site. This helps us understand how the account area performs on mobile, which is where most activity happens. We do not sell this data to third parties, and we do not share your bKash or Upay reference numbers with any outside commercial partner. Cookies are placed when you land on the site. Some are essential for login sessions to persist; others are analytical. You can manage non-essential cookies through your browser settings at any time. Retention periods vary by data category and are governed by the applicable rules in your jurisdiction.
This policy applies to information processed through your vb808 account. It covers your account login activity, wallet transactions, and the data you submit through support channels. It does not extend to third-party services you access from external links, nor does it cover how payment processors such as bKash handle data on their own platforms — those services operate under their own separate policies.
Any data you submit when creating or managing your vb808 account — including registration fields, login events and account preference changes — falls within this policy's scope. We hold only what is needed to operate the account correctly.
Transaction references created when you use bKash, Upay or other linked payment methods are recorded within your account history. We retain these references for the period required under applicable local and regional rules.
Browsing data collected as you move through the site — page views, session logs, device type — is covered here. Cookie behaviour is detailed in the details section above, and you may adjust non-essential cookies through your browser at any time.
Links to external payment platforms, game content providers or promotional partners lead outside our policy boundary. We cannot control how those services handle your data. Review each third party's own policy before submitting any personal details there.
Your account gives you practical ways to review and manage the data we hold. Log into the account area and navigate to your profile settings to see the registration details currently on record. If something is wrong — a misspelled name, an outdated contact address — you can submit a correction request through the support channel, and we will update the record after verifying your identity. You can also ask what data categories we hold against your account and request that we clarify the retention period for any specific category. These rights apply where local law and eligible regional rules permit. If you believe a data handling step has not followed this policy, reach out directly through the published contact route listed in the support section below — we will acknowledge the query and respond through the same channel.
Open your account profile to see the registration and contact details currently stored. The account area shows the fields we hold; anything outside those fields is not part of your standard record.
If any detail is incorrect, contact support with the corrected information. We verify your identity before making changes to ensure no unauthorised edits are applied to your account.
You can ask which categories of data we hold against your account — registration info, transaction references, session logs — and how long each category is retained under applicable local rules.
Use the published support route to send a data-related question. We respond through the same channel and do not redirect data queries to unrelated departments or third-party forms.
If you have a question about how your data is handled, the fastest route is through the account-linked support channel. All three paths below are published on the site; we do not accept data-related queries through unverified channels. Access to support may depend on your local law and the eligible regions in which your account operates.
Open the live chat widget from any page while logged in. State that your query relates to this privacy policy and your account data. The chat thread is logged and forms part of your support record.
Send your data query to the support email address published in the site's contact section. Include your registered account name so the team can locate your record without asking for additional verification steps.
The help centre within your logged-in account area contains published articles on data rights, cookie settings and account record management. Start here if you want to understand a specific policy point before contacting the team.
We apply access controls to your account data so that only authorised processes and account-level requests can read or modify it. Your bKash and Upay transaction references are stored separately from browsing logs, which limits the data exposed if any single layer is queried. Retention periods are reviewed against applicable regional requirements, not held indefinitely. If this policy changes in a material way, we will update the page and note the revision date at the top of the document so you can see exactly what changed.
Account data is accessible only through authenticated sessions. We do not expose registration or transaction records to unauthenticated requests, and account changes require identity verification before they are applied.
bKash and Upay transaction references are stored in a separate layer from general browsing logs. This means a query against session data does not automatically expose your payment history, and vice versa.
We do not hold data beyond the period required under the rules applicable to your region. When a retention period ends, data is deleted or anonymised. You can ask about the specific period for your account category through support.
When we update this policy, the revised version is published at this page path with a clearly noted update date. We do not notify by push message alone — the authoritative record is always this page.
These questions cover what we get asked most often about how account data is collected, held and managed at vb808. If your question is not answered here, use the support routes listed above.
We collect the details you submit during registration — name, contact information and the payment method you link, such as bKash or Upay. We also record transaction references and standard session logs. We collect only what is needed to run your account correctly.
We do not sell or share your bKash or Upay transaction references with outside commercial partners. Data is processed internally for account and wallet management only. Third-party payment processors handle their portion of the transaction under their own published policies.
Retention periods depend on the data category and the rules applicable in your region. Registration data, transaction references and session logs each have different timelines. You can ask the support team about the specific period that applies to your account type.
Yes. Log into your account and open the profile section to see the registration fields currently on record. For a broader list of data categories, submit a request through live chat or the support email. We respond through the same channel you contacted us on.
Contact support via live chat or email with the corrected details. We verify your identity before making any change to ensure the update is authorised. The corrected record is then visible in your account profile area once the update is applied.
Access to vb808 and the data rights described in this policy depend on your local law and the eligible regions applicable to your account. We cannot confirm eligibility for every jurisdiction — check your local legal position before relying on any specific right.