Reference

Your Privacy Policy, Written to Be Read

Here is exactly what we record when you open an account, send a bKash, Nagad or Rocket deposit, and play from your phone — plus the short path to have anything corrected or removed. One read and you know where you stand.

Mobile-number sign-inCookie controlDeletion on requestCorrections in one thread
333w Your Privacy Policy, Written to Be Read
ASK, WE ANSWER

Getting a Data Request Answered Fast

Data questions do not need a long letter. Send yours from the mobile number attached to your account so we can match it without asking you to prove who you are twice. The chat icon inside your wallet screen reaches the support desk directly, and the contact form on this site works if you are reading on a borrowed phone. Say what you want changed — a name, a number, a record removed — and keep the reply thread. We answer in the same thread so nothing gets lost.

Chat inside your wallet Open the chat icon on your account wallet screen and type the request. It reaches the support desk with your mobile number already attached, which saves the back-and-forth of proving who you are.
Contact form on this site Fill the form with the number on your account and the detail you want changed. If the request is about a deposit, add the wallet name and the transfer reference so we can trace it.
Reply thread from before Already raised something? Answer in the same thread. Your earlier messages, the number used and any attachment sit in one place, so whoever picks it up sees the whole story without you repeating it.
KEEPING DATA SAFE

How We Hold and Clear Your Account Data

Every account step leaves a trail we can follow, and that is deliberate. Sign-in needs the one-time code sent to your number, so a borrowed handset cannot open your wallet. Payment records stay attached to the reference your bKash, Nagad or Rocket transfer generates, which is how we trace a deposit that has not landed. Cookies are limited to holding your session and remembering the device you signed in from. When a record is no longer needed for a payment dispute or a legal duty, we clear it on a schedule rather than keeping it lying around.

Data we hold Mobile number, wallet name, sign-in history and payment lines. That is the working set. We keep it tight so a request to check or correct something can be handled in one pass.
Cookies and device memory Two cookies do the work: one holds your session, one remembers the handset you signed in from. Neither follows you to other sites, and clearing them from your browser means a fresh one-time code next time.
Sign-in and wallet security Every sign-in asks for a one-time code sent to your number, and a new device runs the same check before the wallet opens. Got a code you never requested? Report it in the account chat.
Keeping records, then clearing them Payment lines stay while a dispute or legal duty needs them, then we clear them on a set schedule. Ask what we still hold and we will walk through the entries tied to your number.

Privacy Questions You Might Be Asking

Six questions reach our inbox more than any others, so they sit here with plain answers. If yours is not one of them, the support desk takes it directly from the chat inside your wallet or the contact form on this site. Give us the mobile number on the account and the detail you think is wrong, and we will trace it from the sign-in log.

Your mobile number, the wallet name on your account, sign-in history, and the transaction lines for deposits and withdrawals. We never look inside your bKash or Nagad app; we only receive what the payment rail confirms.

Yes. Write from the number tied to your account, we confirm what we hold, then erase whatever the law lets us erase. Payment records tied to audit rules may stay for their set period.

No. Your wallet number and transfer reference go only to the payment partner that has to complete the movement. Game studios see a player ID, never your bKash, Nagad or Rocket details.

Open the chat from your wallet screen and ask. We will check the new number against your wallet name before switching it, then send a one-time code to the new number to close the change.

We set a session cookie and a device cookie so you stay signed in and returning visits skip the code step. Clear them in your browser settings and the next sign-in asks for a one-time code.

Use the contact form on this site or the chat inside your account. Tell us the mobile number and which detail looks wrong, and the support desk will correct it and reply in the same thread.
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.