App / Slots
Your ti9999 account holds wallet references, sign-in details and lobby activity, and this policy sets out what we keep, why we keep it and what you can change. Read it before you open an account, and come back whenever you want a straight answer about your data.
Privacy rules are not the same in every country, so what we can collect, keep and share moves with the law where you live. We run accounts for Bangladesh and other eligible regions, and we open one only where local law allows it. If your region is not covered, the sign-up steps will simply not complete — that is a legal limit, not a fault on your handset. The wallet side is where most questions start. When you send money with bKash, Nagad, Rocket, Upay or a bank transfer, the provider handles its own part of the journey under its own terms. We receive the transaction reference our side needs to credit your account wallet; we do not see your wallet PIN and we never ask for it by message or email. Anything you type on a wallet screen belongs to that provider. Inside the lobby, we record what your account does: sign-ins, device type, browser version, session length and the game pages you open, such as Cricket WicketBets or Sylhet Roulette Room. That record lets you pick up where you left off on a different handset, and it lets our support team answer a question with facts instead of guesses. You decide how much you share. Read this policy in full, ask us to explain any heading, ask to see the account record we hold, and ask us to correct a detail that is wrong. Where your local law gives you a stronger right, that right applies and we will tell you how to use it.
Privacy policies often fail because nobody says where one ends and the next begins. Here is our line. Everything you do while signed in to a ti9999 account — sign-in, wallet moves, game sessions, support messages — sits inside this policy. Everything you do before you have an account, or after you tap out to another company's pages, sits outside it. One practical example. You open the lobby on a mid-range Android handset, tap a slot, then switch to the sportsbook for a cricket match. Every one of those taps becomes part of your account record. Now you tap through to your wallet app to approve a Nagad or Rocket transfer. From that point the wallet screen follows the wallet's rules, not ours. The four cards below mark the boundary: account access, transactions, site content and third-party services. If you are ever unsure whose policy applies to a screen, ask our support team before you type anything into it. That one habit prevents most privacy confusion.
This policy covers the sign-in steps you complete on a phone or a computer, the email or number you register with, and the device and browser details our systems record when you open the lobby. It also covers the session history that lets you return to the same account on another handset.
Wallet activity sits inside this policy on our side only. When you move money with bKash, Nagad, Rocket or Upay, the provider runs its own checks under its own terms. We hold the reference and amount needed to credit your account wallet, not your wallet PIN or the full provider record.
Lobby content is in scope because you browse it while signed in. That means the game pages you open, including titles from studios such as Pragmatic Play, CQ9, Bigtime Gaming and PlayStar, and the live table or sportsbook sections you visit, form part of the activity record linked to your account.
Not everything you tap belongs to us. A wallet screen, a payment page opened inside your bank app or a link that leaves our pages is governed by that other provider's own privacy terms. Read those separately, because we cannot answer for how another company handles your details.
You are not stuck with whatever record we hold. Start inside your account: the profile and wallet pages show the details we keep to run it, and any field you can edit there can be corrected straight away. If something looks wrong and you cannot change it yourself, copy the page name and send it to support rather than guessing. Beyond corrections, you can question any part of this policy and expect a plain answer. You can ask what we hold, why we hold it, and who inside the team can see it. Where your local law gives you a stronger right — a copy of your record, deletion, or an objection to a particular use — that right applies, and we will tell you how to use it. Keep requests specific. Name the account, the heading from this policy you are asking about and the outcome you want. Short, clear requests are easier for us to act on than long ones.
Open your account profile and wallet pages to see the details linked to your sign-in. If you want a fuller copy of the record, ask support and say clearly which part you need. We will explain what we can provide and what the law where you live lets us share.
Typing errors happen. If your name, contact email or phone number is wrong, change it in the editable fields first. Anything you cannot edit yourself is a support request — send the old value, the new value, and the page where you saw it.
You can question any line in this policy. Quote the heading, describe what you expected, and ask us to explain the practice in plain words. We answer these the same way we answer a wallet or sign-in question, through the support route published on the site.
Requesting deletion, a restriction on a particular use or a copy of your record is a written request. Tell us which right you are using and where you are based, because the answer depends on your local law and the regions we are able to serve.
When a privacy question is about your own account, the shortest path is the one that already knows who you are. Sign in, open the help option in your account area and describe the issue — the page you were on, the heading in this policy, and what you expected to happen. If you cannot sign in, the contact form published on the site still reaches us; give the email address on the account so we can match the message. Never send wallet PINs, one-time codes or full card numbers through any support message, whichever route you use. If your request is a formal one — a copy of your record, a correction, or deletion — label it clearly as a privacy request so it is routed to the right person. Here is what helps us most. Tell us which part of the journey the question belongs to: sign-in, wallet activity, or lobby sessions. Name the wallet you used — bKash, Nagad, Rocket or Upay — if the question involves a transaction reference. And say which section of this policy you are asking about, so the reply can quote the same words you read.
The help option inside your signed-in account area is the route our team watches for privacy questions. Start there, because a signed-in request lets us match your message to the right account record without asking you to prove who you are all over again.
If you cannot sign in, the contact form published on our pages still works. Give the email address registered on the account, the section of this policy you are asking about, and a short description of the problem. Do not paste wallet PINs or full card numbers into any message.
For a copy of your record, a correction you cannot make yourself, or a deletion request, use the same support route and label the message as a privacy request. We will confirm what we can act on under the law that applies where you live and in the regions we serve.
Promises about privacy are only worth the practice behind them, so here is ours in plain terms. Account records exist to run your account, answer your questions and meet the record-keeping duties that apply where you live — nothing more creative than that. Access inside our team is limited to the people who need it for the work in hand. Cookies do a narrow job: they keep you signed in and remember small lobby choices. On a phone, you control them through your browser settings, and clearing stored site data will sign you out. You can ask about any record we hold, ask for a correction, or ask for deletion, and we will tell you what the law where you live allows us to do. If something about your account looks unusual — a sign-in you do not recognise, a wallet reference you cannot match — report it through support straight away rather than waiting. We would much rather answer a question early than correct a record later.
We hold the details an account needs: sign-in credentials, wallet transaction references, device and browser data, and the sessions you run. We use them to run the account, answer your support questions and meet the record-keeping duties that apply where you live. We do not sell account details to outside list brokers.
Cookies and similar storage keep you signed in and remember small lobby choices, like the last section you opened. On a phone you control them through your browser settings, where you can clear stored site data or block cookies. Blocking all of them may sign you out or reset parts of the lobby.
Only the team that handles accounts and support can open an account record, and access is limited to the work in hand. Keep your own side locked too: use a sign-in you do not reuse anywhere else, and sign out on a shared handset rather than leaving the session open.
We keep account records while the account is active and for the period the law where you live requires after that. Once nothing requires us to hold them, we remove or anonymise them. To ask about the record we hold, use the support route shown on this site.
Most privacy questions arrive in two shapes: what do you hold about me, and what can I do about it. The six below cover both, and they are the ones our support team answers most often. Each reply states the limit honestly — what we can do depends on the law where you live and the regions we serve — because a promise we cannot keep in your country is worth nothing to you. If your situation is not covered here, send the question through the support route shown on the site. Tell us which heading of this policy you are asking about, and we will answer against your own account record. Your record is yours to inspect, and we would rather explain it now than explain a mistake later. Start with the account pages you already have, then use support for anything you cannot see or fix yourself.
Your sign-in details, the email or number you registered with, wallet transaction references from bKash, Nagad, Rocket or Upay, the device and browser you use, and the sessions and game pages you open while signed in. That set is what runs the account and what support reads back to you.
Yes — start with your own profile and wallet pages, which show the details that run the account. For a fuller copy, send a request through the support route on the site and say which period you want. What we can hand over depends on the law where you live.
We share only what a task needs: a wallet provider sees the transaction it is processing, and a service that keeps our site running may touch technical logs. We do not sell account details. Anything you do inside another company's app follows that company's own terms.
Cookies keep you signed in and remember small choices, so you do not start from zero every time you open the lobby. You can clear or block them in your mobile browser settings. If you block everything, expect to sign in again and to lose saved lobby preferences.
The account record stays while the account is open and for the period local law requires afterwards. If you want it removed sooner, send a deletion request through support. We will tell you what we can remove and what we are required to keep.
No. Your wallet is a separate service with its own terms. We receive the transaction reference needed to credit your account wallet, but the wallet app, its screens and its records sit under the provider's privacy terms. Read those as well, since they cover a different part of the journey.