Live / App
tk100 keeps its legal terms, account rules and data policy on one page so you can read what applies before you touch the lobby or your wallet. Everything below is written for a Bangladesh member on a phone, from eligibility and wallet rules through to the support route you use when a detail needs fixing.
Our terms are written to be read before you act, not after something goes wrong. When you open an account with tk100 you accept the rules on this page, and those rules sit alongside the notices inside your account area, the same notices you meet when you add funds through bKash, Nagad or Rocket. We keep the wording direct because a policy you cannot follow helps nobody. Eligibility is decided by where you are, not by what the lobby shows. Access depends on your local law and eligible regions, so if a game, a wallet route or a cash-out path is not available where you live, it will not appear for you and you should not try to work around it. Confirm that using this site is permitted in your jurisdiction, and keep your login, your device and your wallet under your own control. Money terms follow the same logic. A cash-in or cash-out through a local rail is subject to that rail's rules as well as ours, which is why we show you the fields, limits and verification steps attached to your account before you confirm anything. We do not quote a processing time here, and we will not describe a route as open if it is not configured for your account. We update these terms when the service changes. The current version always sits on this page, and continuing to use your account means the updated text applies to you. If a change touches your wallet, we point you to the section that changed instead of leaving you to hunt for it.
Scope is where most arguments start, so we state ours plainly. This policy covers your account with tk100, the wallet activity that runs through it, and the rules attached to the lobby you see after you sign in. It does not cover the internal rules of bKash, Nagad or Rocket: those wallets set their own terms, and a question about a wallet-side hold belongs with them first. Game content has its own boundary too. Titles such as BPL Night Match or Live Cricket Pitch arrive with published rules from the provider, and where a provider exposes RTP or table limits, those figures are theirs, not ours. Sports markets follow the settlement terms shown at the point of entry. Outside links sit beyond this policy; once you leave our pages, the policy you land on is someone else's. Anything local law requires us to handle differently in your region takes priority over the wording here. If you are unsure which part applies, the notice shown at the point of the action names the rule you are dealing with.
Your sign-in, the details on your profile and the way a session behaves on a phone all sit inside this policy. So does any measure we take when a login does not match what we expect. A locked account or a password reset goes through the support route shown in your account menu.
Cash-in and cash-out activity through bKash, Nagad or Rocket is covered here on our side of the entry: what we record, what you can see, and what we ask you to confirm. The wallet's own rules, holds and reversals stay with that wallet.
Titles and tables you open after signing in come with provider-published rules, and those rules govern how a round resolves. Where a provider exposes RTP or table limits, the figure is theirs. Our part is the access, the record and the route you use if a session ends badly.
Anything you reach by leaving our pages, whether a payment app, a store listing or another site, carries its own terms and its own data practices. We cannot speak for them, and a dispute there sits with that provider. Come back to us only for the part that happened on tk100.
You have real moves here, not just a page to read. Start with your account area: it holds the record of what you did and when, and you can pull up a wallet entry or an account change without asking anyone first. If a detail is wrong, a name typed badly or a phone number that no longer reaches you, correct it through the profile fields so verification and support messages match the same details. Where a field cannot be edited by you, say so in your message and we will tell you what we need. Raising a question works better with specifics. Give the date, the route you used, whether bKash, Nagad or Rocket, and the reference shown on the entry, and the reply comes faster because nobody has to guess which transaction you mean. You can also ask what account data we hold for you and why, and ask for a correction where it is wrong. Where local law gives you a stronger right than this page describes, that right stands.
Open the account area and go through the entries yourself: what was added, what was taken out and when. You do not need permission for that, and having a reference to hand makes any later question easier to answer on both sides of the conversation.
A phone number you no longer use or a name typed wrong can cause a real problem at cash-out. Edit what the profile lets you edit. Where a field is locked after verification, send the correct detail through support and we will tell you what is needed.
Give us the rail, bKash, Nagad or Rocket, the amount you see on the entry and the reference printed beside it. With those three details we can match our record to yours instead of trading messages about which transaction you are looking at.
You can ask what account data we keep, why we keep it and who sees it for the service to run. If something is wrong, you can ask for a correction. Where your local law gives you a wider right, that right applies ahead of anything written here.
Support starts from the screen you land on, not from a number buried somewhere else. Once you are signed in, the help route sits in your account menu, and the same route is linked from the footer of this page so you can reach it without signing in again. Every message you send arrives with the account it came from attached, so you never retype your own details. Say what the problem is in the first line. A wallet question needs the rail, bKash, Nagad or Rocket, the amount shown on your entry and the reference beside it. An access problem needs the device and browser you were using, plus what happened just before the screen changed. Questions about these terms can go the same way, and we will point you to the section that answers them. We do not publish fixed hours on this page, so check the reply notice in the panel for when an answer is coming.
Sign in and the help route sits in your account menu, next to the details it will ask you about. Messages sent from there arrive with your account attached, so you are not retyping a user ID or a phone number into an empty box.
Reading the terms without signing in? The footer of this page carries the same route. Use it for a question about the wording, a correction to a detail or a data request, and name the section you are looking at so the reply lands in the right place.
For anything tied to money, add the payment name, the reference and the amount. A bKash, Nagad or Rocket entry can then be traced against our own record instead of being described again in a second message. A screenshot from the wallet app helps too.
Data handling on tk100 follows the same logic as the terms: collect what the account needs, keep it while it has a job, and tell you what is happening. That means the details you enter at sign-up, the wallet entries behind your history, and the device signals that help us notice a sign-in that does not match. None of it is sold. Cookies play a smaller part than most people assume. They hold your session, your language and your region, and they tell us whether a page rendered properly on your phone; you can clear them whenever you like. Retention is where policy and practice have to agree, so transaction records stay for the period the law sets even after an account closes, while everything else is removed or anonymised once its purpose ends. If you want a copy of what we hold, or want a detail changed, the support panel is the route, and we will tell you plainly what we can amend and what has to stay on the record.
Name, contact details, wallet entries, and the device and browser signals attached to a sign-in. Each piece does a job: opening your session, showing your history or flagging an attempt that looks wrong. We do not sell the record, and nothing is collected for its own sake.
Titles and tables load from provider infrastructure inside our pages. That session carries what is needed for a round to resolve; it does not carry your wallet credentials. If you follow an outside link away from us, that site's own data policy takes over from ours.
Your password stays private to you, and the device you sign in from should be one you control. If a screen behaves oddly, or a session ends without warning, tell the support panel the time and the device rather than waiting for it to happen a second time.
Transaction history stays for the retention period the law sets, even when an account is closed, and other data is deleted or anonymised once its purpose ends. To ask which applies to your own account, name the detail you want checked through the support route.
These are the questions that reach support most often about the policy itself. Each answer tells you where to look or what to send, so you can settle most of it without opening a message. If your situation is not covered here, the help route in your account menu is the next step, and the notice shown at the point of the action usually names the rule that applies to it.
Yes. Access depends on your local law and eligible regions, so some routes, titles or wallet options may not be configured where you are. If something is not shown in your account, it is not available to you, and we ask you not to attempt to work around that restriction.
Two sets. bKash, Nagad and Rocket each run their own process, and our terms cover what happens on our side of the entry once the wallet confirms it. Start with the wallet if the money never left it, then send us the reference so we can trace our own record.
Ask through the support panel and we will tell you what we keep, why we keep it, and who sees it for the service to run. If a detail is wrong, you can correct profile fields yourself or ask us to amend it where the field is locked.
Open your profile in the account area and edit the field. Some fields are fixed after verification, and those need a message to support carrying the correct detail. Keeping your wallet number matched to your account avoids a slow cash-out later on.
The current version stays on this page, and continuing to use your account after a change means the new text applies. Where a change affects your wallet or your access, the notice in your account points to the section that changed so you can read it in context.
Some records stay. Transaction history is held for the period local law requires, even after closure, and other data is removed or anonymised once it no longer serves the purpose it was collected for. Ask support if you want to know which of those applies to you.