Reference

What Our Privacy Policy Covers

Your name, mobile number and every bKash, Nagad or Rocket deposit reference sit in one account record, and this policy sets out exactly who sees that record and why. You can read the whole thing before you open an account, not after.

Copies on requestCorrections by ticketCookie controlsbKash, Nagad, Rocket records
hb7777 What Our Privacy Policy Covers
REACH THE DESK

Where to Send a Data Request

Privacy requests go through the same desk that handles your wallet, which keeps things simple. Sign in, open the support tab and say what you need — a copy of your record, a correction, or an explanation of a decision about your account. Quote the mobile number registered with us. We check that number before we open anything, because a policy is only worth the verification behind it. If chat queues are busy, send the request in writing and keep the thread; it stays linked to your account.

Support Tab Signed in? Open the support tab in your account wallet and send the request from your registered number. The thread stays attached to your own record instead of a shared inbox.
Live Chat The chat window sits on the same screen as your wallet balance, so you can raise a data question while a bKash, Nagad or Rocket deposit detail is still in front of you.
Written Request If you want a trail in writing, put the request down and quote the mobile number registered on the account. We match that number before opening any record.
HOW WE HANDLE IT

Cookies, OTP and Record Keeping

Security around this policy is practical, not decorative. Sign-in runs on a one-time code sent to your registered mobile, so a stolen password alone does not open your wallet history. Deposit references from bKash, Nagad and Rocket are stored against your account so a payment can be traced from our side. Cookies do a narrow job — keeping you signed in and remembering display choices — and you can clear them whenever you like. Records are held only as long as local rules ask, and corrections run through the support tab.

Login and OTP Every sign-in sends a one-time code to the mobile number on your account. That code is what keeps someone holding only your password away from your wallet history and saved payout details.
Cookie Behaviour Session cookies hold your sign-in; preference cookies remember language and layout. Neither carries your balance, and clearing them simply signs you out and resets the display.
Wallet References Each bKash, Nagad or Rocket transfer leaves a reference number that we store against your account, so a deposit can be traced if a payment is ever queried at the desk.
Retention and Corrections Records stay while your account is open, plus the period local rules set. Ask for a correction or deletion through the support tab and we tell you what we can act on and what must stay.

What You Ask hb7777 About Data

These are the questions our desk fields most often on this policy. If yours is not here, send it through the support tab and we will answer it against your own account rather than in general terms.

Yes. Ask from the support tab inside your account wallet and we compile a copy of your profile details, wallet records and login history. We confirm the request against your registered mobile number first.

No. We only need the wallet number you pay from and the transaction reference your bKash, Nagad or Rocket app generates. Anyone asking for your PIN or an OTP is not speaking for us.

Send the correction through the support tab and attach the wallet number already linked. We change the record once the details match, then confirm the update on the contact address you have on file.

Account and payment records stay while your account is open, then for the period local rules require us to hold them. After that they are deleted or anonymised, and we tell you which applies to you.

Some processing sits with payment partners and identity-check providers that may operate outside Bangladesh. We pass only what a check needs, and that transfer is covered by the agreement we hold with the provider.

Two kinds: a session cookie that keeps you signed in, and preference cookies that remember language and display settings. You can block the second kind in your browser without losing access to the lobby.
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.