Reference

Terms Conditions, Written Plainly

Your account runs on one set of written rules, and this page is that text in plain English — how a bKash, Nagad or Rocket transfer is treated once it leaves your phone, what we do with a mistaken payment, and which clauses you…

Clauses in plain EnglishWallet rules for bKash, Nagad, RocketEligibility set by local lawAsk the desk to explain any clause

See The Lobby Read FAQ

ACCOUNT HELP DESK

Reaching Us About a Clause

If a clause reads wrong or you think we applied it unfairly, message our Bangladesh support desk and quote the section number from this page. The same team handles wallet verification questions, so a bKash or Nagad reference you cannot trace goes to one place, not three. Tell us your registered number and the last four digits of the transaction ID — with those two details we can pull the case up without asking you to repeat yourself. Answer times stretch during the payday and post-Eid rush.

Clause questions Message the desk from your signed-in account and quote the section number you want explained. Wallet questions, eligibility questions and clause disputes all land in the same queue, so nothing is bounced between teams.

Wallet reference checks Send the bKash, Nagad or Rocket transaction ID and the number you paid from. We match it against your account wallet and tell you what the record shows, including transfers that never arrived.

Corrections and closures Ask for a profile fix or an account closure from your registered number. We confirm the request back to you, then apply it and explain what happens to any balance sitting in the wallet.

Where These Terms Apply

tk1671 Service availability depends on eligible regions and local law. Users should check local rules before opening an account.

One clause sits above the rest: what you can use tk1671 for depends on where you live. We publish these Terms & Conditions for readers in Bangladesh, but the law in your own area decides whether an account is open to you, and we may have

1
to restrict or close an account in a region that is not eligible. Nothing on this page overrides that. The rest reads like a sign at a shop counter — short clauses, no fine print hidden on a sub-page. Your wallet comes first: when you send
2
money through bKash, Nagad or Rocket, the amount credits against the account number and reference you entered, and a transfer sent to a number you typed wrong is not something we can pull back. Gameplay clauses come next: where a round shows a clear technical fault,
3
the round can be voided and your stake returned. Then the expectations we place on you — one account per person, a wallet in your own name, no shared logins. We amend these Terms when a payment rail changes or a rule shifts, and the date
4
line above moves with each amendment. Where a clause reads badly, contact the desk before you act on it, not after. Wallet funding through bKash, Nagad and Rocket stays subject to local law and eligible regions.

Service availability depends on eligible regions and local law. Users should check local rules before opening an account.

DATA AND RECORDS

How tk1671 Handles Your Records

We keep the records that let us answer a dispute later: your account profile, the wallet references attached to bKash, Nagad and Rocket transfers, and the session log from your sign-in. Sign-in runs on a one-time code sent to your registered number, so a stolen password alone will not open the lobby. Cookies on this site hold your language choice and keep you signed in; clear them and you will be logged out. Ask us to correct a wrong detail on your profile and we will show you what we hold before we change it.

Account records

Your profile, the wallet references attached to bKash, Nagad and Rocket transfers, and sign-in logs stay on file so a dispute months later can be checked against what actually happened.

Cookies we set

This site uses cookies to hold your language choice and your signed-in session. Clear them and you will be logged out and asked for a fresh code on the next visit.

Code-based sign-in

Every sign-in sends a one-time code to your registered number. If a code arrives when you did not try to log in, change your password and tell the desk straight away.

Changing your details

Request a correction from your registered number and we show you the stored value first. Name and wallet changes are checked before they are applied, which keeps the account out of someone else's hands.

What You Ask About These Terms

These are the questions our desk fields most often about this page, answered the way we answer them on chat. If yours is not here, quote the section number and ask — a wrong guess about a wallet clause costs more than a two-minute message before you send money.

Yes. Ticking the box at sign-up means you accept what is written on this page, including the wallet clauses for bKash, Nagad and Rocket. Read it before you confirm.

We check the eligibility line whenever local law shifts and move the date above with it. If your region stops being eligible, we contact you and wind the account down instead of leaving it open.

Ask the desk first. Quote the section number and we will answer in plain words rather than repeat the clause back at you. Doing this before a bKash transfer saves you a dispute later.

The Terms treat a payment sent to a number you typed yourself as outside our control, so check the reference twice before confirming. Send the transaction ID anyway; we will see what can be traced.

Message the desk from your registered number and ask for closure. Clear any wallet balance to your own bKash, Nagad or Rocket account first; then the profile closes and messages stop.

A change carries a new date and a short summary of what moved. Where a change affects money in your wallet, we contact you before it takes effect, not after.

Reference