Casino / Mobile
ku9b takes a direct approach to data privacy — what we collect, why we collect it, and how you can review or correct it is set out here in plain terms. Access to our platform depends on your local law and eligible regions, and this policy applies to all account activity conducted through ku9b.
When you create an account with ku9b, we collect the information needed to operate that account: your registration details, login activity, and the transaction records tied to deposits and withdrawals made through Nagad or Upay. We do not collect more than is necessary, and we do not sell your personal data to unrelated third parties. Data we hold is used to process your account actions, verify identity where required, respond to support requests, and meet any obligations that apply under the law of the jurisdiction governing your use of this platform. Cookies and similar browser signals help us keep your session stable and identify account access patterns that might indicate unauthorised use. You have the right to ask what data we hold about you, to request corrections, and to raise a concern through our published support channel. Retention periods follow the requirements of applicable law; when data is no longer needed for those purposes, we remove it from active systems. If you have questions about how a specific piece of information is used — including a Nagad or Upay payment record — the account support route is the right place to start.
This policy applies to information collected through the ku9b platform. Four distinct areas define what falls inside and outside its scope — understanding the boundary helps you know where to direct a data question and where a different set of rules applies.
Covers login credentials, session history and any identity verification steps completed inside your ku9b account. We handle this data under the terms here; if you have a question about access records, contact support directly.
Deposit and withdrawal records processed through Nagad or Upay are stored against your account. These records are visible in your transaction history and subject to the retention rules described in this policy.
Game interaction data — which titles you open, session length, device type — is collected to maintain platform performance. This data does not identify you by name but is linked to your account ID.
Links or tools operated by third parties, including payment processors and game content providers, follow their own privacy terms. ku9b does not control third-party data practices; check those providers' published policies separately.
Your rights under this policy are practical ones — not abstract promises. You can request a copy of the personal data we hold on your account at any time through the support channel. If any detail is wrong — a name, a contact number, an address — you can ask us to correct it and we will action that request as quickly as the verification process allows. If you believe data has been held longer than the retention period requires, you can raise that directly with us and we will check. For payment-related records, the transaction history inside your account is the first place to look; Nagad and Upay entries are timestamped and tied to your account wallet, giving you a clear, readable paper trail. You do not need to file a formal complaint to ask a simple data question — a support message is enough to start the conversation.
Open your account transaction history to see all Nagad and Upay entries. If a record looks wrong, note the date and amount before contacting support — it speeds up the check.
Send a support message with the specific field you want corrected. We will verify the request against your account before making any change to personal information.
Any question about what data we hold, how long we keep it, or why a specific piece was collected can be directed to our support route. We aim to respond with a clear, specific answer.
Where applicable law gives you the right to request deletion of personal data, you can submit that request through support. We will confirm which data can be removed and which must be retained under legal obligation.
If something in this policy raises a question or you need to act on a data right, the support routes below are the direct paths. We do not route privacy questions through automated systems; a real person reviews account and data requests.
Send your data or privacy question through the support message form inside your account. Include your account ID and a brief description of the data point in question so we can locate the relevant record quickly.
The live chat route on the ku9b site connects you to the support team for real-time questions. Use this channel if you need to clarify a transaction record or ask about a specific policy point before submitting a formal request.
For written, formal data requests — including requests to access, correct or remove personal information — you can reach us by the email address published on the Contact page of the ku9b site. Keep a copy of your sent message for your records.
Privacy on ku9b is not a passive statement — it shapes how the account system is built and how support requests are handled. The points below describe the specific practices that apply to your data from collection through to removal.
We use session cookies to keep you logged in and to detect unusual access patterns. You can adjust cookie settings through your browser; disabling certain cookies may affect account navigation. We do not use advertising tracking cookies tied to third-party ad networks.
Account access is protected through login credentials you set. If you suspect unauthorised access, change your password immediately and contact support. We do not ask for your password in any support communication — any message requesting it should be reported.
We keep account and transaction data for as long as applicable law requires. Once that period ends, data is removed from active systems. Nagad and Upay payment records follow the same retention schedule as all other account transaction data.
When this policy changes in a material way, we publish the updated version on this page with a revised effective date. Continuing to use your account after a policy update means you have had the opportunity to review the new terms.
These are the questions we hear most often about data, privacy and account records on ku9b. If your question is not here, contact support directly through the message form in your account.
We collect the registration details you provide — name, contact information and any verification documents required. We also record login activity, device type and transaction history for deposits and withdrawals processed through Nagad or Upay. We collect only what is needed to operate your account.
Yes. You can request a summary of the personal data held on your account by contacting support through the message form inside your account. Include your account ID in the message. We will confirm the data we hold and the purpose for which it is kept.
Transaction records — including all Nagad and Upay entries — are retained for the period required under applicable law. After that period ends, records are removed from active systems. Your account transaction history reflects the records currently held against your account.
We do not sell your personal data. We share information only with the service providers necessary to operate the platform — for example, payment processors handling your Nagad or Upay transactions — and only to the extent required. Third-party processors operate under their own privacy terms.
Send a support message specifying the field you want corrected and the correct value. We verify the request against your account before making any change. For contact details and name corrections, identity verification may be required before the update is applied.
This policy governs your use of the ku9b platform wherever you access it. However, the availability of specific account features and your rights under data law depend on your local law and eligible regions. Where local law grants additional rights, those apply alongside this policy.