Reference

Privacy Policy for Your azurebet Account

Open your account and the first thing we ask for is a mobile number — that is the whole sign-up. This page sets out what happens to your details after that: what we store, who sees it, and how you get it changed or…

Mobile number sign-inbKash, Nagad, Rocket paymentsCopy on requestCorrection on request
azurebet Privacy Policy for Your azurebet Account
DATA REQUESTS DESK

Where to Send a Data Request

Data questions reach us on live chat, where the team replies in Bangla or English, and by email if you would rather keep a written thread. Both routes land with the same people who handle wallet checks, so you are not passed between desks. Have your registered mobile number ready — that is how we find your account before we touch anything on it.

Team online

Live chat

Open chat from the help bubble on any screen and ask for your data. The team answers in Bangla or English and gives you a ticket number before closing.

Email request

Send from the address linked to your account and put the request in the subject line. We reply in the same thread so you keep a record of what changed.

Wallet check

If the request touches a bKash, Nagad or Rocket transfer, we may ask for the transaction ID from your wallet app before we amend or release a receipt.

BEHIND THE LOGIN

Cookies, Retention and Account Security

Cookies do a small, specific job here: keeping you signed in, remembering your language, and showing us which lobby tiles people actually tap. You can clear them in your phone browser and the account still works — you will just sign in again. Retention follows the money. Deposit and withdrawal records stay while the wallet needs them, and marketing preferences go the moment you switch them off.

Cookies

Session cookies keep your login alive and remember the last table you opened. Clearing them in your phone browser signs you out, but changes nothing about your balance.

Account security

Every sign-in from a new device gets a one-time code on your registered number. If a code arrives when you did not log in, change your password and tell support.

Retention

Transaction records tied to bKash, Nagad, Rocket and Upay stay on file while a payment can still be disputed. Profile details are removed when you close the account.

Changes and contact

Ask for a correction, a copy or a deletion from the mobile number we have on file. We action it from your account, not from a separate copy of the data.

Questions About Your Personal Data

The six questions below come up most often on chat when someone wants to know what sits behind their login. Each answer points to the step we actually take, not a general statement about privacy. If yours is not here, send it to support and we will walk through the account with you.

Your mobile number, the name on your wallet, your transaction history and basic device logs from sign-in. We do not keep card numbers — payments run through bKash, Nagad, Rocket or Upay.

Yes. Ask from the number linked to your account and we compile what we hold — profile details, wallet history and login records — then send it to you as a readable file.

Send the correction from your registered number with the right spelling or the new number. If it touches a wallet name, we check it against the payment record before changing it.

Only what a payment needs: the amount, the reference and the wallet number used. Studios see game rounds, not your wallet details. We do not sell data to advertisers.

As long as the transfer can still be queried, plus whatever period local rules require. Wallet receipts are the last thing we remove, and never before the account is settled.

Profile details go, and wallet history is kept only while those payments can be disputed. Ask us to confirm in writing once the deletion is done on our side.
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.