Sports / App
tk688im handles your information with a straightforward rule: we collect only what your session requires, we keep it only as long as your account is active or as required by applicable rules, and we do not sell it. Access to this platform and the protections described here depend on your local law and eligible regions.
When you open an account with us, we collect the details you enter during registration — your email address, the mobile number linked to your wallet, and the payment method you use to fund your account. For transactions processed through Nagad, Upay or Bank Transfer, we retain a record of each deposit and withdrawal reference so your account wallet history stays accurate and auditable. We do not store your full payment credentials on our servers; what we hold is the transaction reference generated by the payment rail itself. Your device type and browser session data are logged to support account continuity across mobile and desktop — if you switch from your phone to a browser, your session state carries over because of this log. We use this information to operate your account, respond to account queries and meet any reporting obligations that apply based on your jurisdiction. Where local law in Bangladesh or another eligible region requires us to hold or disclose data, we follow that requirement. We do not use your information for third-party advertising profiles. If you have questions about a specific record — such as a Nagad deposit reference or a Bank Transfer withdrawal entry — you can raise it through our account support channel.
This policy covers data generated when you interact directly with tk688im — your account registration fields, your login sessions, your transaction history and the support messages you send us. It does not extend to third-party services you reach from our pages, and it does not govern data held by payment processors such as Nagad or your bank. Each of those services operates under its own terms. Understanding the boundary helps you know exactly who holds which record.
Any data you enter when creating or updating your account — email, mobile number, password hash — falls inside this policy. We control how that data is stored and who on our team can access it.
Deposit and withdrawal references tied to Nagad, Upay or Bank Transfer are logged in your account wallet. We hold the reference number; the payment processor holds the underlying financial record under its own policy.
Game session logs — which titles you opened, how long a session ran — are retained for account integrity and dispute resolution. This covers activity across all lobby areas including slots, live tables and crash games.
Links or embedded tools that point outside tk688im are not covered here. If you follow a link to a payment provider's own page or a game studio portal, that provider's policy applies from that point forward.
You have real, usable choices about the data we hold on you. The most direct path is your account dashboard: the transaction history section shows every deposit and withdrawal reference we have logged, including Nagad and Upay entries. If something looks wrong — a duplicate record, an incorrect amount, a session you do not recognise — you can raise it with account support and we will check the log against the source record. You can also ask us to correct personal details such as your registered email or mobile number by submitting a request through the support channel. If you decide to close your account, we will confirm what data we are required to keep under applicable rules and what we will delete. We aim to respond to data queries within a reasonable time, though we do not publish a fixed response window because it depends on the complexity of the request and the documentation you provide. Access to these rights depends on your local law and the eligible region from which you are using the platform.
Open the transaction history section of your account to see every logged deposit and withdrawal reference. Nagad and Upay entries appear there with their reference codes exactly as the payment rail returned them.
If your registered email or mobile number is outdated, contact account support with your request. We will verify your identity against the account before making any changes.
If you spot a session record or transaction entry that does not match your activity, send us a support message describing the discrepancy. We check the source log and reply with our findings.
You can ask us to close your account at any time. We will confirm which records we must retain under applicable rules and handle the rest according to this policy.
If you have a specific question about the data we hold — whether it concerns a Nagad deposit reference, a login session log or a request to correct your registered mobile number — use the support routes published on this site. We do not handle data queries through social media comments or third-party forums. Use the routes below so your request reaches the right team and creates a traceable record.
Open the support chat from your signed-in account page. Describe your data query clearly and include the transaction reference number if your question involves a payment record.
Send a written request to the support email address listed on the Contact page of this site. Written requests create a clear record and are useful when you need to attach documentation.
The Help Centre on this site covers common account and data questions. Check there first — if the answer is not there, escalate to chat or email for a personalised response.
Data protection at tk688im is a set of specific operational practices, not a broad promise. Your account password is stored as a hash — we do not hold the plaintext version. Session tokens expire after a period of inactivity, which means a device left unattended on the lobby screen will require you to log in again before any action can be taken. Cookie settings control how your browser carries session state between visits; you can manage these through your browser settings at any time. For payment-related records, we hold only the reference data returned by the Nagad, Upay or Bank Transfer rail — never your full account credentials with those providers.
We use session cookies to keep you logged in across page loads on the same device. We do not use tracking cookies to build advertising profiles. You can clear or block cookies through your mobile browser settings without losing your account data.
Password hashing and session-token expiry are active on every account. If you notice a login you do not recognise in your session log, contact support immediately with the session timestamp so we can investigate.
We keep your account data for as long as your account is open and for whatever period applicable rules in your jurisdiction require after closure. Data not covered by a retention requirement is deleted when the account is closed.
To request a correction, deletion or copy of your data, contact us through the account support chat or the support email address on the Contact page. We verify your identity before processing any change to your account record.
Below are the questions we receive most often about how tk688im handles account and payment data. If your question is not here, reach out through account support chat or the email address on the Contact page.
We collect the email address and mobile number you enter during registration, plus the device and browser session data needed to keep your account consistent across mobile and desktop. We do not collect payment credentials — only the transaction references returned by Nagad, Upay or Bank Transfer.
We do not sell your data or share it with advertisers. We may share reference data with a payment processor when you make a deposit or withdrawal, but only the information that processor needs to complete the transaction. Any disclosure required by applicable law in your jurisdiction is handled separately.
Log in and open the transaction history section of your account dashboard. Every deposit and withdrawal reference we have logged — including Nagad and Upay entries — appears there with its reference code. If a record looks wrong, contact support with the reference number.
Yes. Contact us through account support chat or the support email address on the Contact page to request account closure and data deletion. We will confirm which records we are required to retain under applicable rules and delete the rest according to this policy.
Access to the platform and the data rights described in this policy depend on your local law and eligible region. If you are accessing from Bangladesh, check that your use is consistent with applicable local law. The policy applies to your account data regardless of which supported payment method — Nagad, Upay or Bank Transfer — you use.
We will publish an updated version of this policy on this page when material changes are made. Continuing to use your account after a policy update means you have had the opportunity to review the new terms. For significant changes, we may also notify you through your registered email address.