Reference

Privacy Policy for Your luckbet Account

Your data belongs to a real person in Bangladesh, and this page tells you plainly what we keep and why. Read it once before you link bKash, Nagad or Rocket, then open an account knowing exactly how those details travel.

Phone number sign-inWallet PIN never storedCode on new devicesCookie control in browser
luckbet Privacy Policy for Your luckbet Account
PRIVACY CONTACT

Where to Send a Privacy Request

Every privacy request starts in one place: your own signed-in account. We do not take data requests from a third party, and we will not discuss an account with someone who cannot get into it. That rule protects you more than it inconveniences anyone trying to pose as you. Pick the channel that fits the question, and keep your registered number nearby, because we confirm the account before changing anything.

Team online

Live chat after sign-in

Open chat from your signed-in account and describe the request. We confirm your registered number first, then route it to the team holding those records. Never send a wallet PIN.

Email the privacy desk

For a copy of your records or a correction, write in from the email saved on the account. A signed-in chat is quicker when your question is about a transfer still in progress.

Wallet and payment queries

If a bKash, Nagad or Rocket transfer looks wrong, send the transaction reference from your wallet app. We match that reference against the account record before we answer.

ACCOUNT DATA CARE

Data Handling, Cookies and Account Security

Handling your data is routine here, not a one-time promise. Sessions close when you sign out or when the app has sat idle long enough, and payments are matched against the wallet reference rather than anything you type into a form. Cookies carry language and sign-in state, nothing that follows you to other sites. Retention is set by local rules and reviewed as they change. When you send a request, it goes to the team that owns that record — payments for a transfer, support for the rest — and we answer on the number or email already verified on your account.

One-time code on new devices

A new phone or browser needs the code sent to your registered number before the wallet becomes visible. Sign out of shared devices. Treat that code the way you treat cash.

Cookies with a narrow job

The web lobby sets cookies for language, sign-in state and fraud checks. Nothing is sold on to anyone. Clear them in your browser settings and the account record stays exactly as it was.

Retention tied to local rules

Records linked to payments are held for the period local rules set, then removed. Ordinary profile data goes when the account closes, subject to those same rules applying.

Requests we can action

Ask for a copy, a correction or closure from Account, then Data & Privacy. Replies go to the registered number or email only, never to an address you have not verified with us.

Privacy Questions We Get Asked

These are the ones that come up most from account holders around Dhaka and beyond, answered the way we answer them in chat. If your case is not covered, message us from a signed-in account so we can look at the actual record instead of guessing.

Your phone number, the name used for wallet matching, the wallet you link (bKash, Nagad or Rocket), and the device details needed to protect the session. That is the base record behind your account.

No. Your PIN stays inside your own wallet app. We only see the transaction reference your provider returns after a transfer, and support will never ask you to type a PIN into chat.

Yes. Send the request from your signed-in account through support, and we confirm the account on your registered number before releasing anything. Some payment records need that check first.

You can close the account whenever you choose. Records tied to payments stay for the period local rules require, then they are removed. Deletion rights depend on where you live and local law.

Only the teams that need them to run your account: payments, for matching a cashout, and support, when you raise a request. Access is limited by role and each lookup is logged.

Update it before you lose access. Sign in, open Account, then Data & Privacy, and follow the verification step. The new number must pass a one-time code before it replaces the old one.
Reference

Privacy Policy

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.