See Where Your Data Sits
Open a bb44bd account from Bangladesh and the data trail starts with what you type: name, mobile number, date of birth, and the one-time code we send to confirm the handset. When you move money with bKash, Nagad or Rocket, we keep the transaction ID and
-
1
the amount so the transfer can be matched, checked against the wallet and shown back to you on your account statement. We never see or store your wallet PIN — that stays inside your own bKash, Nagad or Rocket app. Who actually reads this? The payments
-
2
team when a transfer needs matching, and support when you write in about a missing credit. Access is limited by role, and each lookup is logged against the staff account that made it, so a colleague cannot browse your file out of curiosity. Where you are
-
3
matters: what we may collect, how long we can hold it and which requests we can act on all depend on the law that applies in your region, and access to the service itself depends on your local law and eligible regions. Where a rule sets
-
4
a holding period for transaction records, we keep them for that period and then delete. Where it does not apply, records go once your account closes and any open query is settled. Ask for a copy, a correction or a deletion and we tell you plainly
-
5
what we can do, what we cannot, and why. The answer always comes in writing so you have it on record.
Service availability depends on eligible regions and local law. Users should check local rules before opening an account.