Where Local Law Sets the Line
Your privacy on tk688one comes down to one plain rule: we collect what an account and a wallet need, and little beyond it. When you open the account you give us a phone number and a password; at payout stage you add the details tied to
-
1
your bKash, Nagad or Rocket wallet. When you deposit, the record shows an amount, a reference and a time. We keep that entry so a dispute can be traced, not so we can watch what you do afterwards. What if you are somewhere we cannot serve?
-
2
Access depends on your local law and eligible regions, and that rule reaches privacy too. If play is not permitted where you are, tell us and we close the account and clear what we are not required to keep. Cookies are the other piece people ask
-
3
about. A small set keeps you signed in, remembers your language, and shows which lobby areas get opened. Clear or block them in your mobile browser and the site still works; you will simply sign in again each visit. Loading a cricket market or a live
-
4
table does not depend on a tracking cookie. Retention is deliberate rather than endless. Payment references, deposit logs and account-opening records stay for the period our finance and legal duties require, then they go. Marketing preferences sit outside that rule: switch them off any time and
-
5
the change lands at once. Nothing here reads the same in every country, because data rules differ. Your local law sets the floor and we follow the stricter reading where the two disagree. Payment rails we can support differ just as much, which is why the
-
6
chip row above covers bKash, Nagad, Rocket, Upay and bank transfer rather than one fixed option.
Service availability depends on eligible regions and local law. Users should check local rules before opening an account.