Live / Slots
cab666 is clear about what data we collect, why we collect it, and how you can control it. This policy covers every interaction your account has with our platform — from wallet transactions using bKash or Upay to session activity across mobile and desktop. Access to our platform depends on your local law and eligible regions.
This policy applies to all data cab666 processes when you create an account, log in, browse the lobby, or carry out a wallet transaction. When you use bKash or Upay to fund your account, the transaction reference and amount are recorded against your account record — the payment processor handles the transfer itself under its own terms. We collect your registration details (name, contact information, preferred payment method), session data (device type, browser, IP region), and any correspondence you send through our support channels. We do not sell your personal data to third parties. Data shared with payment providers like bKash or Upay is limited to what those services require to process your transaction. We retain account records for as long as your account remains active and for any further period required under applicable regulations. You can request a copy of what we hold, ask us to correct inaccurate details, or raise a deletion request — each of those paths is described in the rights section below. Use of this platform is subject to your local law and the eligible regions we serve.
Not every part of your online activity falls under this policy. Understanding the boundary helps you know where cab666 is accountable and where a third party's own terms govern. The four areas below draw that line clearly so you can make informed choices about the data you share.
Creating an account, logging in and managing your profile are fully within scope. We control these flows and the data they generate. Any detail you enter during registration or account recovery is processed under this policy and kept in your account record.
When you initiate a deposit or withdrawal using bKash or Upay, cab666 records the transaction reference and status. The actual transfer is processed by the payment provider under its own privacy terms. We hold the outcome record; the provider holds the transfer detail.
Your browsing behaviour inside the lobby — which game rooms you open, how long a session runs, which categories you visit — is collected as session data under this policy. We use it to keep the lobby functional across your devices, not to profile you for external advertising.
Links or services that take you outside cab666 — including payment apps, external identity checks or studio provider portals — operate under their own privacy policies. We are not responsible for data practices that happen off our platform. Check those providers' terms directly.
You have concrete options under this policy — not just abstract entitlements. You can request a copy of the personal data we hold on your account at any time by contacting our support team through the published channel. If any detail is wrong — a name spelling, a contact number, a linked payment method — you can ask us to correct it, and we will update the record once we verify the change. If you want to close your account and request deletion of your data, you can submit that request through support; we will confirm what can be removed and what must be retained under applicable regulations. We aim to acknowledge data-related requests within a reasonable period. Access to these rights may depend on local law and your eligible region. The steps below outline the four main actions available to you.
Contact support and request a summary of the personal data linked to your account. We will confirm what categories of data we hold and provide a copy where permitted by applicable regulations.
If your registered name, contact address or linked payment method is recorded incorrectly, raise a correction request through our support channel. We verify the change before updating the account record.
If any part of this policy is unclear — how session data is used, what gets shared with bKash or Upay, how long we keep records — send your question through the published support route and we will answer it directly.
You can request closure and ask what data can be removed. We process deletion requests in line with applicable retention rules and confirm the outcome to you through the same support channel you used to raise the request.
If you have a question about how your data is handled, want to exercise a right described in this policy, or need to report a concern, use one of the contact routes below. We only list channels that are visibly available on the site. We do not promise specific response times, but every request is logged and handled in the order it is received.
Open the chat widget from any page on cab666 to send a data or privacy question directly to our support team. This is the quickest way to reach us for account-related data queries.
Send a written request to the support email address listed in your account area. Use this route for formal data requests, correction notices or account closure inquiries where a written record is useful.
The help section of the site carries published policy documents and account guides. Check there first for answers about data categories, cookie use and wallet record-keeping before raising a direct support ticket.
We apply standard technical measures to protect the data held against your account — covering login credentials, session records and transaction history. Cookies are used to keep you logged in across mobile and desktop, to remember lobby preferences, and to measure which parts of the site are used most. You can manage cookie preferences through your browser settings; disabling certain cookies may affect how the lobby functions on your device. Data retention periods vary by record type: active account data is kept while your account is open, and transaction records are held for any period required under applicable rules. For changes to this policy, we publish an updated version on this page. Continued use of the platform after a policy update indicates acceptance of the revised terms.
Cookies keep your session active and remember lobby preferences across your phone and desktop. You can adjust cookie behaviour in your browser settings at any time. Some functional cookies are needed for the account login flow to work correctly.
Login credentials and wallet-linked details are stored under standard access controls. If you notice any unauthorised activity on your account — unusual session locations or unexpected bKash or Upay transaction references — contact support immediately through the published channel.
We keep active account data for as long as your account is open. Transaction records linked to bKash or Upay payments are retained for any period required by applicable regulations. Closed-account data is handled in line with the deletion terms confirmed at the time of closure.
When this policy changes, the updated version replaces the previous one on this page. We do not notify every account individually for minor clarifications. For significant changes that affect how your data is used, we aim to communicate through the account area.
These are the questions we receive most often about how cab666 handles your data. Each answer is specific to this policy — not a general platform description. If your question is not covered here, use the support channel to ask directly.
We share data only where it is necessary to process your account activity. Payment providers like bKash and Upay receive the minimum detail needed to handle your transaction. We do not sell your data or pass it to advertisers. Third-party studios providing game content do not receive your personal details.
Send a data access request through our live chat or email support channel. We will confirm the categories of information held against your account and provide a copy where regulations allow. Your request is logged and handled in the order it arrives.
Yes. You can request deletion when you close your account. We will confirm what can be removed and what must be kept under applicable retention rules. The outcome is communicated to you through the same support channel you used to raise the request.
Transaction references and status records linked to bKash or Upay payments are stored in your account history. The actual transfer detail is held by the payment provider under its own terms. We keep our side of the transaction record for any period required under applicable rules.
This policy applies to your use of the cab666 platform. Access to the platform itself depends on your local law and your eligible region. If local regulations in your location restrict online account activity, those rules take precedence. Check your local legal position before using the platform.
Cookies keep your session active and store lobby preferences on whichever device you use. If you clear cookies between sessions, you will need to log in again. Adjusting cookie settings in your mobile browser may affect how the lobby loads on that device specifically.