Your information, transaction records through Nagad, Rocket, or Upay, and browsing activity on kbbet are handled according to this policy — written plainly so you know exactly what we hold, how we use it, and what choices you have. Access to this platform depends on your local law and eligible regions.
Account data transparency
Nagad, Rocket, Upay context
Your right to review records
Clear contact route
POLICY SCOPE DETAIL
How kbbet Handles Your Personal Information
When you open an account, we collect the details you submit: your name, contact information, and the payment method you choose — whether that is Nagad, Rocket, or Upay. We use this data to verify your account, process wallet transactions, and respond to support requests. We do not sell your personal data to third parties for marketing purposes. We may share information with payment processors and identity-verification services strictly to complete the service you have requested. Data shared with these processors is limited to what is necessary for that task only. We retain your account records for as long as your account remains active and for any further period required by applicable law in your eligible region. If you close your account, we will retain only the records we are legally required to keep, and we will delete the rest within a reasonable period. Cookies and session data collected when you browse the site are used to keep your session active and to remember your account preferences — not to build advertising profiles. The current state of your cookie preferences is shown in your account dashboard after login. Any questions about specific data items we hold can be directed to our support channel, details of which appear in the contact section below.
Nagad
Payment data passed to Nagad is limited to the transaction amount and your account reference. We do not store your Nagad PIN or wallet credentials on our servers.
Rocket
Rocket transactions are processed through the provider's own gateway. Your Rocket wallet number is held only to match deposits and withdrawals to your account record.
Upay
Upay payment details follow the same data-minimisation approach. Only the fields needed to complete and reconcile the transaction are passed to the Upay gateway.
INSIDE AND OUTSIDE
What This Policy Covers and What It Does Not
This policy applies to data collected directly through kbbet — your account registration, wallet activity, and support interactions. It does not extend to third-party services you reach by following a link away from this site. Understanding the boundary helps you know who to contact when you have a question about a specific record.
Account Access
Data you submit when opening or updating your kbbet account — name, contact detail, and login credentials — is covered in full by this policy. You can review and correct this data by raising a request through our support channel.
Wallet Transactions
Records of deposits and withdrawals made through Nagad, Rocket, or Upay are covered here to the extent they sit within our system. The payment provider's own privacy terms govern data held on their side.
Site Content and Cookies
Browsing behaviour on kbbet pages, session cookies, and preference data stored in your account are within this policy's scope. You can manage cookie settings through the preference control shown in your account dashboard.
Third-Party Services
Links to external sites, game studios such as PG Soft or Pragmatic Play, and any service outside the kbbet domain operate under their own privacy terms. We are not responsible for how those services handle your data.
YOUR PRACTICAL CHOICES
Actions You Can Take Under This Policy
You have concrete options when it comes to the data we hold on your account. Reviewing your own records is the first step: log in and open the account section to see the profile details and transaction history we have stored. If anything looks incorrect — a name spelling, a contact number, or a payment reference — you can request a correction through our support team without closing your account. Where you believe data is held without a valid reason, you can raise a formal question and we will respond with the basis on which we hold it. If our answer does not satisfy you, you have the right to escalate to the relevant authority in your eligible region, depending on local law. We aim to respond to all data-related requests within a reasonable period; the exact timeframe depends on the complexity of the request. Starting with the account dashboard gives you the fastest route for straightforward corrections.
Review Your Records
Log in and navigate to your account profile. Your stored details, linked payment methods such as Nagad or Rocket, and transaction history are all visible there without needing to contact support first.
Correct Account Details
If a name, contact detail, or wallet reference is wrong, open a support request and describe the correction needed. We verify the change against your account before updating the record.
Raise a Data Question
If you are unsure why we hold a particular piece of information, write to us using the contact details in the support section. We will identify the data, state the reason we hold it, and outline your options.
Request Deletion
You may ask us to delete data we are not legally required to retain. Submit the request through the support channel; we will confirm which records can be removed and which must be kept under applicable law.
REACH OUR TEAM
How to Contact Us About This Policy
Privacy questions deserve a direct answer, not a general support queue. The routes below connect you to the team handling data and account queries. For wallet-related data questions involving Nagad, Rocket, or Upay transactions, include your account reference and the approximate date of the transaction so we can locate the record quickly.
Live Chat
Open the chat widget from any page after logging in. For policy and data questions, describe the specific record you are asking about so the agent can route it to the right team without delay.
Email Support
Send a written request to our support email address shown in the Contact section of your account dashboard. Include your registered contact detail and a clear description of the data request.
Account Dashboard
Many record-review and correction steps start directly in your account settings. Log in, open the account section, and follow the fields shown there before raising a formal support request.
HOW WE PROTECT DATA
Our Data Handling and Account Security Practices
Keeping your account data accurate and secure is part of how we run the platform, not an afterthought. We apply access controls so that only the staff or systems with a defined need can view your personal records. Payment data linked to Nagad, Rocket, and Upay transactions passes through encrypted connections. We do not store full wallet credentials on our servers. Cookie data is used to maintain your session and remember account preferences — you can review the current state of those settings in your account dashboard after login. We review our data-handling practices periodically and update this policy when our processes change; the current version is always the one published at this address.
Encrypted Connections
All data exchanged between your device and our platform travels over an encrypted connection. This applies to login, account updates, and payment steps through Nagad, Rocket, or Upay equally.
Access Controls
Internal access to personal account records is restricted by role. A staff member handling a game query does not have access to your payment history; each access level is scoped to the task it supports.
Data Retention Limits
We keep your data for as long as your account is active and for the period required by law in your eligible region. Records no longer needed under those terms are removed on a defined schedule.
Policy Update Notice
When we update this policy, the revised version replaces this page. We aim to notify active account holders of material changes through the contact detail registered on their account.
POLICY QUESTIONS ANSWERED
Common Questions About Your Privacy on kbbet
The questions below cover what visitors ask most often about how we handle personal data, what rights you have, and how to act on them. If your question is not answered here, the support routes in the section above will connect you to someone who can help.
What personal data does kbbet collect when I open an account?
We collect the details you enter during registration — name, contact information, and the payment method you add, such as Nagad or Rocket. We also record your login activity and transaction history so that your account stays accurate and disputes can be resolved.
Does kbbet share my data with third parties?
We share data only with the services needed to run your account: payment processors for Nagad, Rocket, or Upay transactions, and identity-verification services where required. We do not sell or rent your personal data to advertising networks or unrelated third parties.
How can I see what data kbbet holds about me?
Log in and open your account profile. Your registered details, linked payment methods, and transaction records are visible there. For a full data export or a list of records held outside your visible dashboard, submit a request through our email or live chat support.
Can I ask kbbet to delete my account data?
Yes. Contact us through the support channel and state clearly that you want data removed. We will identify what can be deleted and what must be retained under applicable law in your eligible region, then carry out the deletion for the records that qualify.
How does kbbet handle cookies on the site?
We use cookies to keep your session active and to store your account preferences between visits. We do not use cookies to build advertising profiles. Your current cookie preference state is shown in your account dashboard settings after login; you can adjust it there.
Who do I contact if I have a complaint about how my data is handled?
Start with our support team via live chat or email — details are in the support section of this page. If you are not satisfied with our response, you may escalate to the data-protection authority relevant to your eligible region, depending on the law that applies to you locally.