Reference

What Our Privacy Policy Covers

This page tells you what we collect when you open an account, top up with bKash or Nagad, and move between phone and laptop. It is written in plain terms so you can see exactly what happens to your details.

Account details you give usWallet and payment recordsDevice and login dataYour rights over your recordHow to reach our support team
donni88 What Our Privacy Policy Covers
HOW WE HANDLE IT

The Controls Behind Your Record

Privacy on a betting account is mostly about small, boring controls working every time. Your session is encrypted in transit, your password is stored hashed rather than in readable form, and a fresh login from an unfamiliar device triggers a one-time code to your registered number before the account opens. On mobile the same rule holds, so switching from your phone browser to a laptop does not quietly skip the check. We keep transaction and login records for as long as your account is open and for the period afterwards that our accounting and dispute handling need; once that window passes, the record is removed.

Cookie and session choices

We use cookies to keep you signed in and to remember your language setting. You can clear them in your browser at any time, though you will need to log in again afterwards.

Account security steps

Password hashing, one-time codes to your registered number and device checks run on every login. If something looks off, the session is held before any wallet action is allowed.

Retention and deletion

We hold your details while the account is open plus the period our accounting and dispute handling require. Ask support to close the record and we tell you what stays and why.

Who sees your data

Only the teams that need it: payments staff checking a bKash or Nagad reference, and support handling your ticket. We do not sell your details to outside list brokers.

ASK US DIRECTLY

How to Reach Us About Your Data

If you want to know what we hold, need a correction, or want your record closed, our support desk is the way in. Message us from inside your logged-in account so we can match the request to the right profile, and quote the ticket number you get back on any follow-up. We will usually ask you to confirm your registered mobile number before we touch anything, because we will not hand account details to someone who cannot prove the account is theirs. Bring your bKash or Nagad transaction reference if the question is about a payment record.

In-account support desk Open the help tab once you are signed in and send a message. Your ticket is tied to your profile, so we can pull the exact record you are asking about without you retyping it.
Registered mobile check For any data request we confirm the mobile number on the account first. This one step is what stops someone else from asking for your details in your name.
Payment reference lookup If your question is about a bKash, Nagad, Rocket or Upay top-up, send the transaction ID from your wallet app so we can trace the record from your side and ours.

Privacy Questions You Might Have

These are the questions our support desk fields most often about personal data, account access and payment records. If yours is not here, message us from inside your account and we will answer it directly. What we can offer still depends on your local law and eligible regions.

The details you enter yourself: name, date of birth, mobile number and password. We add the device and browser you sign in from, plus the transaction records created when you top up through bKash, Nagad, Rocket or Upay.

Yes. Message our support desk from inside your logged-in account and ask for a copy of your record. We confirm your registered mobile number first, then send the details tied to that profile.

No. Your mobile number is used for account verification, login codes and payment matching. We do not pass it to unrelated advertisers or sell your record to outside list brokers.

Transaction records for bKash, Nagad, Rocket and Upay top-ups stay while your account is open and for the period afterwards that our accounting and dispute handling need. After that they are removed.

Ask support to close the record. We tell you plainly which details are removed straight away and which are held back for the accounting and dispute window, so nothing is left vague.

A fresh device triggers a one-time code to your registered number before the account opens. The check runs the same way in a mobile browser and on desktop, so switching devices never skips it.
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.