Reference

Privacy Policy: What We Keep and Why

Our privacy policy spells out what we record when you open an account and how your bKash, Nagad or Rocket transfers get logged.

What we recordCookie controlsWallet dataYour requests
7c7776 Privacy Policy: What We Keep and Why
REACH THE DESK

Talk to Us About Your Data

Two routes reach the people who handle data requests. Write to support from the email or mobile number on your account with 'privacy' in the subject line — that flag routes the ticket past general lobby chat to the desk that can pull a record. Or start live chat from inside your account wallet and ask the agent to raise a data ticket for you. Either way you get a reference number, so when you follow up about a bKash, Nagad or Rocket record nobody makes you explain it twice.

Team online

Privacy ticket by email

Write from the email registered on your account with 'privacy' in the subject so it routes past lobby chat to the team that can pull a record. You get a reference number back.

Live chat inside the wallet

Open live chat from your account wallet and ask the agent to raise a data ticket. Quote the bKash, Nagad or Rocket number on the account so the record is found quickly.

Wrong wallet or name

If a wallet number or a name on your record is wrong, tell the agent what it should read. We check the change against the payment trail before saving it.

HOW WE HANDLE DATA

Cookies, Retention and Account Security

Security here is mostly small mechanics, not slogans. Your password is stored hashed, the login code goes to the number you registered, and a new device has to pass that code before the wallet opens. Cookies do the boring work: they keep your session alive and remember the language you picked. We keep payment references for as long as a partner or a regulator can ask to see them, and we clear the device logs we no longer need.

Login codes and passwords

Your password is stored in hashed form, never as plain text. Each login from a new device needs the code we send to your registered number, and the session expires when you sign out.

Cookies we set

Session cookies keep you signed in between pages. A preference cookie remembers your language. Analytics cookies stay off until you accept them, and you can clear all three from your browser at any time.

Payment record retention

Each bKash, Nagad, Rocket or Upay transfer leaves a reference we keep while a payment partner or regulator may still ask for it. After that window closes, the reference is purged from our systems.

Who opens your record

Only staff handling a ticket or a manual deposit match can open your account record, and every access leaves a trace. Your number never goes to third-party advertisers.

Questions About Your Privacy

These are the questions our desk gets most often about the policy itself. If yours is not here, send it in — the answer usually depends on how you paid and what your local rules allow, and we would rather explain it once than have you guess.

Your mobile number, the wallet you register, your device and browser details, and a record of every bKash, Nagad or Rocket transfer on the account. Documents are only requested when a payment needs manual matching.

Yes. Raise a ticket and ask for a copy of your record. If your wallet number or name is wrong, tell us what it should read and we will fix it after checking the payment trail.

Only where it has to travel: the payment operator that confirms your bKash, Nagad or Rocket transfer, and a regulator or court if a lawful request arrives. Advertisers never receive your number or wallet details.

Some of it, for a while. Payment references for bKash, Nagad or Rocket transfers stay until a partner or regulator no longer needs them, while login logs are cleared sooner. Ask us to delete the rest.

You can load the public pages, but the wallet needs a session cookie to keep you signed in. With cookies off, a bKash deposit form will not hold before you reach the next screen.

Message our support desk straight away and say the account may be compromised. We sign it out on every device, hold wallet activity, and send a fresh login code to the number on file.
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.