App / Live
tk1k collects only the account and transaction data needed to run your wallet, process payments through bKash, Upay, and Bank Transfer, and keep your account secure. This policy tells you exactly what we collect, why we hold it, and what you can do about it — access depends on your local law and eligible regions.
This policy applies to personal information we collect when you create an account on tk1k, make deposits or withdrawals using bKash, Upay, or Bank Transfer, and browse the site's lobby or support pages. The data we collect falls into three categories: identity details you submit at registration (such as your name and contact address), transaction records generated each time a payment moves between your wallet and your account, and technical signals from your device — browser type, session identifiers and approximate region. We hold transaction records because every bKash, Upay, and Bank Transfer deposit creates a reference number that ties your account balance to a real payment event. That record is what lets you confirm a deposit arrived or query a withdrawal. We do not sell your personal data to advertisers. We do not share it with third parties outside what is required to process your payments or meet an obligation under applicable law. Your use of this site and the application of this policy depend on your local law and the eligible regions where tk1k operates. If your jurisdiction does not permit access to this platform, this policy does not create an entitlement to use it.
Not every interaction with tk1k falls under the same data handling rules. The table below separates what this policy directly governs from what sits outside it, so you know where to look if a question comes up about a specific part of your experience.
Registration details, login records and session tokens are covered. We hold this data to authenticate your identity each time you open the account page and to let you reset access if needed.
Deposit and withdrawal records linked to bKash, Upay, and Bank Transfer are within scope. Each transaction generates a reference you can cross-check against your mobile wallet history or bank statement.
Game titles in the lobby — slots, live tables and crash games — and the studio content from Pragmatic Play, Habanero, PlayStar, Microgaming and CQ9 are not personal data. Browsing those pages produces session logs, not identity records.
Payment processors and mobile wallet providers operate under their own privacy terms. Once your transfer leaves this platform toward bKash or your bank, their policy governs that leg of the transaction. We cannot extend our policy to cover their systems.
Your account data is not locked away. If you want to see what we hold, you can raise a data access request through our support channel and we will tell you what categories of information are on file for your account. If something is incorrect — a name spelling, a contact detail entered at registration — you can ask us to correct it. We will update the record once we have confirmed the change against your account. For withdrawal or deposit records tied to bKash, Upay, or Bank Transfer, those transaction logs are read-only by design; corrections to a payment amount or reference follow the payment dispute process, not the standard data-correction path. If you want to close your account and ask us to delete your data, note that some transaction records must be retained for the period required by applicable law before deletion is possible. Write to us via the support route listed on the contact page. We will acknowledge your request and explain the timeline based on what you have asked for.
Submit a data access request through our support channel. We will confirm which data categories we hold for your account, including registration details and payment reference logs.
Contact support with the corrected information and your account identifier. We verify the change against your original registration before updating any stored field.
If something in this policy is unclear — how long we keep a bKash deposit record, for example — write to us directly. We aim to respond with a plain explanation, not a legal form letter.
You can request deletion of your personal data. Some transaction records are subject to retention requirements under applicable law, so we will tell you which records can be deleted immediately and which must be held for a set period.
If you have a question that this policy does not answer clearly, or if you want to act on one of your data rights, the routes below are the published ways to reach us. Use the channel that suits your question — account queries through the account support path, policy questions through the dedicated privacy contact.
Open the support page on tk1k and submit your query through the account help form. Include your registered contact detail so we can locate your record.
For data access, correction or deletion requests, use the privacy contact route published on our contact page. State clearly what you are requesting and the account it relates to.
For questions about a specific bKash, Upay, or Bank Transfer transaction record held on your account, raise a payment query through the cashier support section of the site.
Data handling at tk1k is built around four practical areas: what we store, how long we keep it, what cookies do on your device, and how we secure your account session. Each of those is covered below.
Account registration data is held for as long as your account is active, plus any additional period required by applicable law. Transaction records — bKash, Upay and Bank Transfer logs — are kept for the period needed to support payment queries and legal obligations, then removed.
We use session cookies to keep you logged in while you navigate the lobby and to remember your device for the current visit. Persistent cookies are limited to functional site preferences. We do not deploy advertising trackers tied to your identity across other sites.
Your password is stored in a hashed form — we do not hold it in plain text. If you suspect unauthorised access, change your password immediately through the account settings page and contact support. Do not share your login with anyone.
When we update this policy, the revised version is published at tk1k/privacy-policy/ with the effective date shown at the top of the page. Continued use of the account after a policy update means you have read the revised terms.
These are the questions that come up most often about how tk1k handles personal data, payment records and information. If your question is not here, use the privacy contact route to ask us directly.
At registration we collect the name, contact address and any verification details you submit through the account form. We also log the device and region signals your browser sends. We do not collect more than what is needed to open and maintain your account.
Yes. Each bKash or Upay deposit and withdrawal creates a transaction reference that we store on your account. This is how you can verify a payment arrived or dispute a missing withdrawal. We do not store your full mobile wallet PIN or password.
You can submit a data access request through our support channel. We will then list the categories of information held for your account — registration details, session logs and transaction records — and explain the format in which we can share them.
Payment records tied to bKash, Upay, and Bank Transfer are kept for the period required by applicable law to handle queries and meet legal obligations. Once that period ends, records are removed. The exact retention period depends on the type of transaction and applicable regulations.
We share data only where it is necessary to process your payment — for example, passing a transaction reference to your mobile wallet provider — or where we are required to by law. We do not sell your personal data or share it with advertisers.
Send a deletion request to our privacy contact route on the contact page. We will confirm which data can be deleted immediately and which records must be retained for the period required by law before removal. We will give you a clear timeline in our reply.