Reference

How bd33bd Handles Your Account Information

This page sets out what we collect when you open an account with bd33bd, how bKash, Nagad and Rocket transactions are recorded, and how your device and login details are kept secure.

Account dataWallet recordsDevice sessionsSupport access
bd33bd How bd33bd Handles Your Account Information
REACH OUR TEAM

Who To Contact About Your Data

Team online

Live chat

Message our support desk from inside your account for questions about what data we hold or how a bKash, Nagad or Rocket transaction reference was logged.

Account support

If you spot a login from a device you don't recognise, contact support directly from the account page so we can review your session history with you.

Data requests

Ask for a summary of your stored account details or request removal where local law allows it; we'll confirm your identity through your registered mobile number first.

SECURITY IN PRACTICE

Cookies, Retention And Account Security

Cookies

We use cookies to keep you logged in between the app and browser and to remember your language and lobby preferences, not to track you across other sites.

Retention

Transaction references from bKash, Nagad and Rocket are kept only as long as needed for account and payment records, in line with applicable local law.

Account security

Your login is tied to your registered mobile number and device; unusual sign-in attempts from a new device trigger an extra verification step before access is granted.

Requesting changes

You can ask us to correct or update account details like your registered mobile number through support; identity checks apply before any change is made.

Privacy Policy Questions From Our Users

No. Your PIN is entered and confirmed inside your bKash, Nagad or Rocket app itself; we only receive the transaction reference once payment clears.

You can request removal of stored account details through support, subject to identity verification and to what your local law permits us to delete.

Your transaction records are visible to you on your account and to our internal support team when handling a query; we don't share this with outside marketers.

We match your session to your registered mobile number and device; signing in from an unrecognised device may prompt an extra verification step.

No. Your account history stays linked through your registered mobile number, so moving from the app to browser or back doesn't create separate records.

Data handling details can vary by your local law and eligible region; contact our support channel if you need clarification specific to where you're accessing bd33bd from.
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.