Reference

Your Privacy Policy in Plain English

Your account details, your bKash, Nagad and Rocket payment records and your device sign-in history all sit under one privacy policy we keep short on purpose.

Account details you sharebKash, Nagad, Rocket receiptsCookie and session recordsRequests for copies or deletion
2777bet Your Privacy Policy in Plain English
TALK TO US

Reaching the Privacy Desk

Questions about your data should not disappear into a general inbox. Message our Bangladesh support team from the Help section once you are signed in, and the chat thread carries your account number automatically, so you do not have to retype it. Ask for a copy of your data, a correction to your name or number, or an explanation of a cookie you saw on the site. Requests that touch payment records may need the matching bKash, Nagad or Rocket transaction ID before we can act.

Signed-in chat This is the quickest route. Your account number and recent wallet activity attach to the thread, so the agent can see what you are asking about without screenshots.
Support email Write from the address linked to your account, using the support email listed in the Help section, and mark the subject as Privacy Request. We reply to that same address only.
Closing your account Ask us to close the account and delete details we no longer need. Records tied to completed payments stay with our payment partners for as long as local rules require.
HOW WE HANDLE IT

Data Handling, Cookies and Sign-In Safety

We keep your details on servers we control, and staff reach them through role-based access rather than an open database. Sign-in runs on a one-time code sent to your mobile number, so nobody gets in without your phone. Cookies hold the session together between browser tabs and the mobile site; block them and you will simply be asked for a new code each visit. Retention follows the purpose behind each record — a closed account keeps very little beyond what payment rules require us to hold.

Narrow payment records

A wallet payment leaves us a reference number, the sending number and the amount. Your bKash, Nagad or Rocket PIN never reaches us, and we store no card data we do not need.

Cookies you control

Session cookies keep you signed in. Others remember language and measure page speed on mobile networks. Clear them from your browser settings whenever you like and the site still works.

One-time code login

Every sign-in asks for a fresh code on your registered number. If a code arrives when you did not try to sign in, do not share it and tell support so we can lock the session.

Retention and deletion

We hold account details while the account is open. After closure we delete what we can and keep only the payment and audit records that local rules require us to hold.

Privacy Questions We Get Asked

These are the data questions that land in our chat most often, answered the way we would answer them there. If your situation turns on local law, say where you are and we will tell you plainly what applies to your account and what does not.

Your name, mobile number, date of birth and the wallet numbers used for bKash, Nagad or Rocket payments, plus login and device records that keep the account secure.

No. The PIN stays inside your wallet app. We only receive the transaction ID, the amount and the sending number so your payment can be matched to the account wallet.

Yes. Ask from signed-in chat or email us from your registered address. Once we confirm you hold the account, we send the details we store in a readable format.

Send a closure request from the account itself. We remove what is no longer needed and keep only the payment records that local rules require us to hold for a set period.

Not for browsing. You can block or clear them, but the site will ask for an OTP each time you return and any saved language setting will reset to default.

Our Bangladesh support team through signed-in chat first. If you cannot sign in, use the support email in the Help section and mark your message as Privacy Request.
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.