Reference

Privacy Policy in Plain Words

Here is what we collect, why we hold it, and how you get it changed — written the way a cashier would explain it across the counter.

bKash, Nagad, Rocket referencesAccount wallet ledgerCookie choicesChange or removal requests
mcwbd88 Privacy Policy in Plain Words
HOW WE PROTECT IT

Safeguards Behind Your Account Record

Access to your record is limited to the people who need it for a payment check or a support reply, and each lookup is logged. Passwords are stored hashed. Signing in on a new phone asks for a one-time code sent to your mobile number, and swapping the wallet tied to the account needs that same code. Retention follows a set schedule: payment records stay while a dispute is still possible, then are cleared.

Data handling

Your name, mobile number and wallet references sit in one account record. Only cashier and support staff working your case open it, and every lookup is written down.

Cookies and device data

Session cookies keep you signed in; analytics cookies show which pages load slowly on mobile data. Refuse the second kind in your browser and the lobby still works.

Account security

A new phone triggers a one-time code to your mobile number. Changing the wallet tied to your account needs that code as well, so a borrowed SIM cannot redirect a payout.

Retention and removal

Payment records are held while a dispute could still arise, then cleared. Ask for earlier removal and we tell you plainly what your local law allows.

ASK US DIRECTLY

Where to Send Data Requests

Privacy questions come through the help desk inside your account, the same place you raise a deposit that has not landed. Quote the wallet you used — bKash, Nagad or Rocket — plus the reference number, and the reply comes back attached to that transaction instead of a generic answer. Want a detail corrected or removed? Say it in the same conversation so the request sits in one record with your ledger.

Help desk in your account Open your account wallet and pick the help option. Your ledger, wallet history and earlier replies sit on the same screen, so you never retype a payment reference.
Report a wallet mismatch Sent a bKash or Nagad amount that never reached your balance? Attach the reference and the time. We match it against the cashier log before replying.
Ask for a change or removal Want a field corrected or a record taken out? Name it. We reply with what we can do under your local law and eligible regions.

Privacy Questions We Get Often

These are the ones our support desk answers most about the privacy policy, gathered from real account queries rather than written once and left alone.

Your name, mobile number, date of birth and password, plus the bKash, Nagad or Rocket reference each time you fund the wallet. We do not receive your wallet PIN.

Yes. Ask from the help desk inside your account and we return what we hold: profile fields, wallet history and the support messages tied to your case. Some payment records we must keep.

Only where it is needed to run your account — the payment channel that processed your transfer, or a service keeping the site online. We do not sell your details to anyone.

Send the correction from the help desk inside your account, naming the field. If your name no longer matches the bKash or Nagad wallet on file, we ask you to confirm from the wallet app.

You can close it through support. Profile and cookie data go; payment records stay for as long as your local law requires, and we tell you that stretch when you ask.

No. Session cookies expire when you sign out or shut the browser. Analytics cookies record page behaviour on our own pages only, and your browser settings can block them.
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.