Reference

Terms Conditions That Govern Your luckbet Account

Our Terms & Conditions set out what you agree to when you open an account with us — from how your wallet handles bKash, Nagad and Rocket deposits to what we expect from each other while your account is active.

Account rules in one placeEligibility by local lawWallet and payment termsSupport when wording is unclearCricket markets included
luckbet Terms Conditions That Govern Your luckbet Account
DATA AND ACCESS

How We Handle Your Data and Account Security

Running a member account means holding a small amount of personal detail, and these conditions explain what we keep and why. Your login is protected by a one-time code sent to your registered number, so keep that number current — a stale number locks you out of your own wallet. Passwords, session cookies and device records exist to keep you signed in safely, not to be shared, and you can request a copy of what we hold or ask us to correct it through support.

One-time code sign-in

Each login needs a code sent to your registered mobile number. If you change numbers, update it in account settings before you sign out, or you will need support to restore access.

Cookies and sessions

Session cookies keep you signed in between visits and remember your device. Clearing them signs you out, which is normal. Persistent cookies only support features like language and wallet preferences.

Retention after closure

Transaction records tied to bKash, Nagad and Rocket transfers are kept after an account closes because payment and audit rules require it. Ask support for the retention period that applies to your records.

Requesting changes

You can ask for a correction to your stored details, or for a copy of your data, by contacting support from the email on your account. Requests tied to a clause are answered in writing.

GET CLARITY FAST

Where to Ask About a Clause

If a line in these conditions does not make sense for your situation, ask us before you act on it. Our Bangladesh support team reads terms questions the same way it reads wallet questions, and you can reach them on live chat from inside your account — the fastest route because the agent can see your account state. Email works for anything longer, such as a dispute over a deposit or a request tied to a specific clause.

Team online

Live chat inside your account

Open your account, tap the support bubble and a Bangladesh agent picks up the conversation. Have your account number ready so they can read your wallet history alongside the clause you are asking about.

Email for written requests

Send longer questions or a clause-related dispute to our support inbox. Written replies are useful when you need a record of what was agreed, and you can attach a bKash, Nagad or Rocket transaction reference.

Account notification panel

Policy updates and account notices land in the notification panel of your dashboard. Check it after any change notification so you are reading the current version of the conditions, not an older copy.

Questions About Our Terms & Conditions

These are the questions our support team fields most often about the conditions themselves — acceptance, changes, payments, closure and where to complain. If your situation is not covered here, ask us directly rather than guessing at the wording.

At registration, when you tick the box before creating your account. Using the lobby, wallet or sportsbook afterwards confirms that acceptance, so read the conditions before you tick rather than after your first bKash deposit.

Yes. We update the wording when the wallet, lobby or payment flow changes. The revised version appears on this page with its effective date, and account-affecting changes are flagged in your notification panel.

They do. Payment clauses explain how a deposit is credited, what to do when a Nagad or Rocket transfer does not show in your wallet, and how a withdrawal request is verified before it is released.

Outcomes depend on the clause involved. Some issues are resolved by a request for documents or a corrected payment reference; serious breaches, such as using another person's account, can lead to suspension while we review.

Ask support in writing from your registered email. We confirm any pending withdrawal first, then close the account. Payment records are kept after closure because audit and payment rules require it.

Send it to support with the clause reference and any transaction ID. We reply in writing, and if you disagree with the outcome you can escalate within the same channel rather than opening a second account.
Reference

Terms & Conditions

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

Access may be available only where local law permits.