Casino / App
kb668 collects only the account and transaction data needed to keep your wallet working and your sessions secure. This policy explains exactly what we collect, why we collect it, and how you can review or correct it — access to this platform depends on your local law and eligible regions.
When you open an account with us, we collect the details you provide during registration — your mobile number, email address and the payment method you choose for funding. For Bangladesh members using bKash, Rocket or Upay, we record the wallet reference tied to each deposit or withdrawal request so your transaction history stays accurate and traceable. We also collect device and session data — browser type, IP address and navigation events — to maintain account security and detect access anomalies. We do not sell this data to third parties. We do not share your payment references or wallet identifiers with advertisers. Data is retained for as long as your account remains active and for a further period required by any applicable compliance obligation in the region where you access this service. You may request a summary of what we hold at any time through our support route. This policy may be updated when our data practices change, and the revised version will be posted on this page. Continued use of your account after an update means you have read the current version. Availability of this service depends on local law and eligible regions.
Not every part of your experience with kb668 falls under this policy. Some areas are covered directly; others involve third-party services that operate under their own terms. Understanding that boundary helps you know who to contact when you have a data question.
Your login credentials, session tokens and account activity are fully within the scope of this policy. We control how this data is stored and who can access it internally. If you want to review what is held, the support route on this page is the right starting point.
Deposits and withdrawals routed through bKash, Rocket or Upay involve both our records and those of the payment provider. We hold the transaction reference on our side; the wallet provider holds its own record. Queries about wallet-side data go to that provider directly.
Pages you browse on kb668, the games you open and the session cookies we set are covered here. We use session and functional cookies to keep you logged in and to remember your wallet preference. You can clear cookies through your browser, though this will end your active session.
Links or embedded tools that point outside kb668 — for instance, a payment gateway interface or a game studio's own help page — are not governed by this policy. Once you leave our domain, the external site's own privacy terms apply.
You are not a passive subject of this policy — there are concrete steps available to you. If you want to see the personal data we hold on your account, you can request a data summary through our support contact. We will confirm receipt and work through the request in a reasonable time. If any detail is wrong — your registered mobile number, email address or linked wallet identifier — you can ask us to correct it; the same support route applies. Where data is no longer needed for account operation or compliance, you can ask about removal. We will tell you if a retention obligation prevents deletion and explain the reason. For any question about how your bKash, Rocket or Upay transaction records are stored, our account support team is the right point of contact. We do not require you to use a formal legal process to start any of these conversations — a clear message through the available channel is enough to open a review.
Request a summary of the personal data stored on your account. We will confirm the request and respond through the contact channel you used to reach us.
If your registered mobile number, email or wallet ID is wrong, let us know. We will update the record and confirm the change once it is processed on our side.
If you believe data is no longer needed, ask us about deletion. We will explain whether a compliance obligation requires us to keep it and for how long.
Any question about how we handle your data — cookies, session logs, wallet references — can be raised through our support contact. You do not need a formal process to start.
If you have a specific question about your account data, a correction request, or a concern about how your bKash, Rocket or Upay wallet reference is stored, reach out through one of the contact routes below. We respond through the same channel you use to contact us. All privacy-related messages are handled by the account support team.
The live chat window is accessible from your account dashboard. Use it to raise a data question or start a correction request directly.
Send a written request or data query to the support email address listed in your account settings. Describe your question clearly and include your registered mobile number.
The help section inside your account area contains a contact form specifically for account and data queries. Fill in the subject line and your message will reach the right team.
Data we collect is stored with access controls that limit who inside our organisation can view your account records. Your wallet transaction references — whether from bKash, Rocket or Upay — are not exposed to any team outside account operations. Session cookies expire when you log out or close the browser, which reduces the window for any unauthorised access. If our data practices change materially, we will update this policy page and note the change at the top of the document.
Your account data is visible only to account operations staff. No marketing or third-party team holds access to your personal record or wallet transaction history. Internal access is reviewed on a routine basis.
We use session and functional cookies only. Advertising or tracking cookies from outside the kb668 domain are not set by us. Clearing your browser cookies ends the current session and removes stored preferences.
We keep your data for as long as your account is active. After account closure, data may be retained where a compliance obligation requires it. We will explain the reason if you ask about deletion.
When this policy is updated, the revised version appears on this page. The date of the last change is noted at the top. Continuing to use your account after an update means you have read the current version.
These are the data and privacy questions we hear most often from account holders. If your question is not covered here, reach us through the support contact routes listed on this page.
We collect your mobile number, email address and the payment method you register — such as bKash, Rocket or Upay. During each session we also record your device type and IP address for security checks. We do not collect data beyond what your account operation requires.
No. Your wallet identifier is stored on our side for transaction reconciliation only. We do not pass it to advertisers, data brokers or any external party outside the payment processor handling the specific transaction you initiated.
Send a request through live chat, the support email in your account settings, or the contact form in the help section. Include your registered mobile number so we can locate your record. We will acknowledge receipt and respond through the same channel.
Yes, you can request deletion. Where no compliance obligation requires us to retain the data, we will remove it. If a retention period applies — for example, to transaction records — we will explain the reason and the expected timeframe before deletion can proceed.
We set session and functional cookies that keep you logged in and remember your wallet preference. We do not set advertising or cross-site tracking cookies. To remove them, clear cookies in your browser settings — note that this will end your active session and remove saved preferences.
This policy covers data collected through your account regardless of where you access the service. However, whether you can legally use the service at all depends on your local law and the eligible regions for this platform. Review the terms of access for your jurisdiction before proceeding.