Reference

What We Hold About Your Account

Our privacy policy covers one thing: the account and payment data that keeps your bdbajie wallet working, and what we do with it. Every category we store, every partner who sees it and the route to change or remove it sits on this page.

Account detailsbKash recordsNagad transfersCookie choices
bdbajie What We Hold About Your Account
HOW WE HOLD IT

Security, Cookies And Retention

A session cookie keeps you signed in; clear your browser and you are signed out, which is exactly what you want on a shared phone passed around a shop counter. Sign-in from a new device triggers a one-time code to your registered mobile number, and we never ask for that code or your wallet PIN in a message. Cookies that measure page behaviour are separate and can be blocked without losing the lobby. Records are cut back when their purpose ends: payment references go once the dispute window closes, and a closed account keeps only what local law and payment rules still require.

Sign-in security Your password plus a one-time code sent to the registered mobile number. A new device forces that check again, and no member of the team will ever ask you to read the code out.
Cookie choices The session cookie is required for sign-in. Measurement cookies are optional, and blocking them in your browser settings leaves the lobby and your account wallet fully usable.
Retention windows Wallet references and transaction rows stay while a payment can still be queried or reversed. Sign-in logs are kept shorter. Nothing is held past the point it serves a purpose.
Changes and closure Ask for a correction, a copy of your records, or closure of the account. Once identity is confirmed you get the outcome in writing, and marketing contact stops the same day.
ASK US DIRECTLY

How To Reach The Team

Two channels carry every privacy request: the help chat inside your signed-in account and the support email address on our contact page. Both land with the same team. Write from the mobile number registered to your account, say what you want changed, and expect us to confirm your identity before anything moves — that check protects your balance as much as your records. Queues follow Bangladesh time, and a message sent from a phone in Dhaka reaches the same people as one from a browser elsewhere. If a request touches a payment, paste the bKash, Nagad or Rocket transaction ID in the first message so we match the record on the first pass.

Team online

In-account help chat

Signed-in chat is the shortest route. Open your account, tap help, and the message carries your account ID automatically, so we skip the back-and-forth about who you are.

Support email

Write from the address saved on your profile and attach the wallet transaction ID for any payment question. We reply to that address only, so an email change needs identity confirmation first.

Payment records help

If a bKash, Nagad or Rocket transfer shows on your wallet but not on your account, send the reference and the amount. We trace it against our ledger and answer in writing.

Questions About Your Data

The six questions our help chat answers most often about this policy, written out plainly. If yours is not here, the same team handles it by chat or email.

The name, mobile number and date of birth you enter at sign-up, your sign-in and device records, and the wallet reference for each bKash, Nagad, Rocket or Upay payment you make.

No. A wallet PIN stays inside your own bKash, Nagad or Rocket app. We see the reference number and the amount, which is enough to match a transfer without touching your login.

Yes. Ask through the help chat or from your registered email, confirm your identity, and we send a written copy of your account and payment records to the address on file.

Switch off offers in your account settings, or tell the team and we stop them. Account messages still arrive, because a payment alert or sign-in alert is not a promotion.

One is. The session cookie keeps you signed in, so the lobby cannot run without it. Cookies that measure page behaviour are optional and can be blocked in your browser settings.

The account stops opening and marketing contact ends. Wallet references stay for the dispute window while a payment can still be queried, then go, except what local law still requires us to keep.
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.