App / Sports
km6 is clear about what data we collect, why we collect it, and how you can review or update it. Access to our platform depends on your local law and eligible regions — and this policy explains what applies when you use your account.
When you open an account with km6, we collect the information needed to run it — your registration details, device identifiers, session activity and any payment records linked to your wallet transactions, including Nagad and Rocket deposits or withdrawals. We hold this data to keep your account functional, process your transactions accurately and respond to support requests you raise through published channels. We do not sell your personal data to third parties. Data shared with payment processors — such as Nagad or Rocket — is limited to what those services require to complete a transaction and is governed by their own published terms. We may retain account and transaction records for a period consistent with our operational and legal obligations; the exact retention window depends on the applicable rules in your eligible region. Cookies and similar identifiers help us recognise your device across sessions so you can return to the lobby without re-entering your details every time. You can adjust cookie settings in your browser at any point. If you access km6 from Bangladesh, your use of this platform is subject to whether such access is permitted under local law and your eligible region's rules. Nothing in this policy overrides those requirements.
This policy applies to data collected through your km6 account — registration, login activity, payment records and support interactions. It does not extend to third-party sites linked from our pages or to payment providers' own data practices. Understanding the boundary helps you know which questions to direct to us and which to raise with the relevant third party.
Data tied to your account login — email, device identifiers and session activity — falls fully within this policy. We control how this data is stored and for how long, and you can request a review through our published support route.
When you use Nagad or Rocket to deposit or withdraw, we record the transaction reference in your account history. The payment provider processes the transfer under its own terms — our policy covers only the record we hold on our side.
We use cookies to keep your session active and to understand which sections of the site you visit. These are first-party identifiers. You can clear or block them via your browser settings; doing so may affect how your account loads on return visits.
Links to external services, game studios or payment gateways lead outside km6. Once you leave our domain, this policy no longer applies. We encourage you to read the privacy terms of any third-party service before you share data with them.
You have real choices over how your data is held by km6. If you want to see what information we have on your account, raise a data access request through our support channel and we will point you to the relevant records — including transaction history linked to Nagad or Rocket payments. If a detail is wrong — a name, a contact address or a payment reference — contact support and we will walk you through the correction steps shown in your account settings. You can also ask us to delete data we no longer need for operational purposes; we will review the request against our retention obligations and confirm the outcome in writing. Where your concern is about how a specific piece of data was collected or used, put the question to our support team with the account reference and the date of the event. We will respond through the channel you used to contact us. Eligibility to exercise these rights may depend on your local law and eligible region.
Submit a data access request via the published support route. We will identify the account records we hold — including payment history — and confirm what is available for your review.
If your registered name, contact details or linked wallet information is incorrect, reach out to support with the right information. The correction path is shown inside your account settings once you are logged in.
For questions about how a specific data point was collected or shared, include your account reference and the approximate date. We respond through the same channel you used so the thread stays in one place.
Where you want data deleted and we have no legal or operational obligation to keep it, submit the request in writing. We will confirm whether the removal can proceed and give you a clear outcome, not a vague acknowledgement.
If this policy raises a question you cannot answer by reading it, or if you need to act on your account data, use one of the contact routes below. We do not publish operating hours we cannot confirm, and we do not invent response timelines — use the channel that is visible and active in your account area.
Open the chat widget visible in your logged-in account area. Describe your privacy question and include your account reference so the agent can locate your records without delay.
Send your request to the support email address published on the contact page. Include the nature of your data question and the account details needed to identify your records.
The help section inside your account lists published steps for common privacy actions — reviewing records, updating details and managing cookie preferences — without needing to contact support directly.
km6 keeps your account data behind access controls that limit which internal processes can read or write to your records. Payment references from Nagad and Rocket transactions are stored separately from browsing session data so that a cookie issue cannot expose financial records. We review our data practices when operational requirements change and update this policy accordingly — the version shown on this page is the current one.
We use session cookies to keep you logged in and analytics identifiers to see which pages load most on mobile. You control both through your browser settings. Blocking cookies may slow down your return-to-lobby flow on repeat visits.
Login credentials are not stored in plain text. If you believe your account has been accessed without your knowledge, contact support immediately using the live chat route and follow the steps shown in the account security section.
We keep account and transaction records for as long as our operational and regional legal obligations require. Once that period ends, records are removed or anonymised. The exact window depends on the rules applicable in your eligible region.
When this policy changes in a material way, we post the updated version here with a revised effective date at the top of the page. Continuing to use your account after an update means you have read the current version.
These are the questions we hear most often from people reading this policy for the first time. If your question is not here, use the live chat or email route shown in the contact section above.
We collect the details you enter at registration — name, contact information and device identifiers — plus session activity and payment transaction references from services like Nagad and Rocket. We collect only what we need to run your account and process your requests.
We do not sell your data. We share limited information with payment processors such as Nagad or Rocket only to complete a transaction. Each processor operates under its own published terms. We do not pass your data to advertisers or data brokers.
Raise a data access request through our live chat or the published email address. Include your account reference so we can locate your records. We will confirm what is held and walk you through how to view the relevant sections of your account history.
Yes. Contact support with the specific detail you want corrected or the data you want removed. We will check whether a retention obligation applies and confirm the outcome clearly. Corrections to payment-linked details may require identity verification before we process the change.
We use cookies to keep your session active and to understand how pages load on mobile devices. You can clear or block cookies in your browser settings at any time. Some account features — such as staying logged in between visits — depend on session cookies to work correctly.
This policy applies to data collected through your km6 account. Whether you can access the platform at all depends on your local law and eligible region. If access is permitted where you are, this policy governs how we handle the data generated by your account activity.