Reference

Privacy Policy, Written in Plain Words

This page explains what 9b9999 records when you open an account, log in from your phone, or move money through bKash, Nagad, Rocket or Upay.

Account data onlyWallet details kept separateCookie choices explainedChange requests accepted
9b9999 Privacy Policy, Written in Plain Words
HOW WE HANDLE IT

Security, Cookies and Keeping Records Short

Privacy is mostly about what happens after the data arrives. Here is how we treat it day to day.

Account security steps

Login uses a one-time code sent to your mobile number, and we flag a new device before it can reach the wallet. Change your password after sharing a phone and tell support if a code arrives when you did not ask for one.

Cookie control

Session cookies keep you signed in between screens. Analytics cookies show us which pages stall on mobile data. Block either from your browser and the account still opens — some screens may ask you to sign in again.

Retention of records

Payment references tied to bKash, Nagad, Rocket or Upay stay with the account so disputes can be traced. When a retention period ends, the record is removed. Ask support for the position that applies to your account.

Requesting a change

Send a correction or deletion request by email from your registered address. We confirm receipt, check your identity against the account, then update the record and reply with what changed.

ASK ABOUT PRIVACY

Where to Send a Privacy Question

You do not need a long explanation. Send us the mobile number on your account and the specific request — a copy of your data, a correction, or a deletion — and we route it to the team that handles it. Requests about wallet records are easier to trace when you include the bKash, Nagad or Rocket transaction reference from your payment history.

Live chat from your account Open the chat panel after you log in and choose the privacy topic. It reaches our support team directly, so we can pull your account details without asking you to repeat them.
Email for written requests Data copy, correction and deletion requests are best sent by email. Write from the address linked to your account so we can verify the request before we act on it.
Wallet reference check If your question is about a bKash, Nagad, Rocket or Upay record, add the transaction ID. That lets support match the entry to your account faster and answer with the exact detail.

Privacy Questions We Get Asked

Short answers to the things people actually message us about. If your case is not covered, the support section above tells you where to send it.

Your mobile number, registered name, login and device history, and the transaction references from bKash, Nagad, Rocket, Upay or bank transfers. We do not keep your wallet PIN, and we do not read your messages or contacts.

No. Your PIN is entered inside the wallet app, not on our pages. If anyone asks for your PIN and says they are from us, stop and report it to support — no genuine team member will ask for it.

Yes. Email us from the address or number registered on the account and ask for a data copy. We verify the request against your account details, then send the record in a readable format.

Send a deletion request by email from your registered address. We confirm identity first, then remove what the rules allow. Records tied to a payment dispute may be held until that matter closes.

Only where a service has to run — payment confirmation through your wallet provider, or fraud checks on a new device. We do not sell account data, and we do not pass your number to outside advertisers.

Access depends on your local law and eligible regions. If a feature is not available for your account, we do not collect the data that feature would need, and support will explain which parts apply to you.
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.