Live / Slots
cb668 collects only what it needs to run your account and process activity through your chosen payment method — whether that is Nagad, Rocket or bKash. This policy explains what we collect, why we hold it, and what you can do about it. Access to our platform 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 wallet identifiers linked to payment methods such as Nagad, Rocket or bKash. We also record transaction references generated when you move funds between your account wallet and those payment rails. On top of that, we log standard browsing signals — device type, session timestamps and page interaction data — so we can keep the account experience consistent across your visits. We do not sell your personal details to third parties for marketing purposes. Data shared with payment processors is limited to what those processors need to complete or verify a transaction. Where third-party service providers handle data on our behalf, we require them to treat it under terms at least as protective as those described here. Retention periods vary by data type. Transaction records are held for the period required to resolve disputes and meet our operational obligations. Account profile data is held while your account remains open and for a defined period after closure. You can ask us to clarify how long a specific data type is held by raising a query through the support route published on the site. Availability of this service depends on your local law and the eligible regions we operate in.
Wallet identifiers linked to Nagad are shared only with the Nagad payment processor to complete your transaction. No additional profile data is passed.
Rocket transaction references are logged against your account for dispute resolution. They are not used for marketing or passed to unrelated third parties.
bKash payment data is processed through the relevant payment rail. We retain only the reference needed to confirm the transaction completed correctly.
This policy covers what happens inside your cb668 account and on the pages you reach through our domain. It does not extend to third-party sites you navigate to from our content, and it does not govern how external payment processors handle data on their own systems. Understanding the boundary helps you know where to direct a question about your data.
Any data you submit when logging in — credentials, device fingerprint, session token — falls inside this policy. We hold it to authenticate your session and detect unusual access patterns on your account.
Payment references generated through Nagad, Rocket or bKash during deposits or withdrawals are covered here up to the point they reach the payment processor. The processor's own policy governs what happens on their side.
Interaction data collected as you browse game lobbies or sports markets — scroll depth, clicks, session length — is covered by this policy and used only for internal product and account experience purposes.
Links to external platforms, affiliate pages or provider support portals fall outside this policy once you leave our domain. We have no visibility into how those destinations collect or use your data.
You have several concrete actions available to you under this policy, and none of them require specialist knowledge to use. Start with your account settings page — that is where most profile corrections can be made directly without contacting us. If something is not editable from within your account, our support route is the correct path. We aim to respond to data queries through the channels we have published; we do not operate undisclosed back-channels or invite requests by post. Every action listed below maps to a real process inside your account or our support flow. Eligibility to exercise these rights may depend on your local law and the region from which you access the platform.
Open the account history section to view transaction references, session logs and the profile data we hold against your account. This is available to you at any time while your account is active.
If your contact details, wallet identifiers or profile information are out of date, edit them directly in account settings. Fields that cannot be self-edited require a support request with identity confirmation.
Submit a data query through the support channel published on our contact page. Describe which data type or record you are asking about so we can route it to the right team quickly.
If you want your account closed and your stored data handled according to retention rules, contact support with a closure request. We will confirm the steps and timeline through the same channel.
If you have a question about how your data is handled, the contact routes below are the ones we actually monitor. We do not list channels we cannot staff. If your query involves a wallet transaction reference — such as a Nagad or Rocket payment record — include the reference number when you write to us so we can locate the record without unnecessary back-and-forth.
Open the chat widget from any page on the site. For data queries, state clearly in your opening message that your question is about your account data or this privacy policy so the agent can route it correctly.
Send your data or privacy question to the email address shown on our Contact page. Include your registered account username and a description of the data record you are asking about.
Your account's Help section contains a direct link to submit a support ticket. Select the Privacy or Data category when prompted so your request is flagged to the right team from the start.
Data handling at cb668 follows a set of defined practices around collection, storage, access and retention. These are not abstract commitments — they shape what actually happens when you use your account, make a payment through bKash or Rocket, or browse game lobbies on a mobile device. The items below describe the specific areas we manage and how you can verify or act on each one.
We use cookies to maintain your session, remember account preferences and measure how the site is used. You can manage cookie settings through your browser. Blocking certain cookies may affect how account pages load or navigate.
Your login credentials are stored in hashed form. We do not store plain-text passwords. If you suspect unauthorised access to your account, change your password immediately and notify us through live chat or email.
Transaction records are kept for the period needed to handle disputes and meet operational requirements. Profile data is held while your account is open. After closure, we retain only what our obligations require and delete the rest on schedule.
When we update this policy in a material way, we will post a notice in the account notification area before the change takes effect. Continuing to use your account after that date means you have seen and accepted the updated terms.
The questions below come from account holders who wanted to understand how their data is handled before or after opening an account. If your question is not covered here, use the support contact route described in the section above.
We collect the name, contact details and wallet identifiers you enter during registration. If you link a Nagad, Rocket or bKash account, the wallet identifier associated with that payment method is recorded against your profile for transaction purposes.
We share data only with payment processors — such as those handling Nagad, Rocket or bKash transactions — and only to the extent needed to complete your payment. We do not sell your data to advertisers or unrelated third parties.
Transaction references and identity records are kept for the period our operational obligations require. After that window closes, we delete them. You can ask us for specifics on a data type by submitting a support ticket through the Help section of your account.
Most profile fields — contact details, linked wallet identifiers — are editable directly from your account settings page. Fields locked for security or verification reasons require a support request with identity confirmation before we can update them.
Submit a deletion request through the email address or live chat route shown on our Contact page. Include your account username and specify what you are asking us to delete. We will confirm what can be removed and what we are obliged to retain.
Yes. Whether you access your account through a mobile browser or a dedicated app, the same policy applies. Session and device data collected during a mobile visit is handled under the same retention and access rules as desktop session data.
Yes. Your ability to open an account and exercise the data rights described in this policy depends on your local law and whether you are accessing the platform from an eligible region. Check the terms page for region-specific eligibility details.