What We Hold and Why We Hold It
We collect only what the account actually needs to run. That starts with what you type in yourself: name, date of birth, mobile number and the wallet number behind your bKash, Nagad or Rocket transfers. Verification records come next — the reference ID or screenshot tied
-
1
to a wallet payment — because a transfer has to be matched to a person before it clears. Device data is the third layer: handset model, app version and the IP address a session starts from, which is how we flag a login that doesn't look
-
2
like yours. We do not sell your data. It is shared only where the job requires it: a payment partner confirming a Rocket transfer, a studio platform loading your game session, or a lawful request from an authority with jurisdiction over us. Everything else stays inside
-
3
our own systems, and staff access is limited to the account care and payment teams who need it. Retention follows the same logic. Verification records and transaction history stay while your account is open, plus the period accounting rules require afterwards. Marketing preference data goes the
-
4
moment you switch it off. Cookies split the same way: the ones holding your session are essential, while analytics and preference cookies follow what you set in your browser or the cookie banner. Rules differ by country, so read this as our standing practice rather than
-
5
a promise that every clause applies identically everywhere. Platform availability, and the data duties that come with it, depends on your local law and eligible regions.
Service availability depends on eligible regions and local law. Users should check local rules before opening an account.