Reference

Privacy Policy: What We Hold and Why

We collect what a working account actually needs — your wallet reference, your sign-in device, the details that let us match a bKash, Nagad or Rocket transfer to you.

What we hold and whyWallet references traced, not sharedCookie choices you controlCopy, correction or deletion on request
betjini Privacy Policy: What We Hold and Why
DATA KEPT TIDY

How We Handle Your Account Data

Data handling runs on a small set of habits. We ask for the fields the account needs, keep wallet references because that is how a transfer gets traced, and watch sign-in devices so a new phone does not slip past us. Cookies do one job: hold the session and remember your screen preferences. Retention follows the local financial rules for payment records, and anything past that period is deleted or anonymised. Want something corrected or removed? The request goes to the privacy desk and returns with a ticket number you can follow.

What you give us We hold your name, date of birth, mobile number, email if you add one, and the references for your bKash, Nagad, Rocket, Upay or bank transfers. Nothing beyond what the account and its payment checks need.
Cookies and device storage The site stores a session cookie so you stay signed in, plus a preference file for language and screen size. You can clear both in your browser settings; logging out ends the session cookie.
Login checks on a new phone A fresh handset triggers a one-time code to your mobile number before the account opens, and we keep the sign-in record. That log is what lets us act if you tell us someone else got in.
How long records stay Payment records are held as long as the local rules require and no longer, then deleted or anonymised. Ask us to remove what is no longer needed and we tell you what must stay, and why.
ASK US DIRECTLY

How to Reach Us About Your Data

If something about your data needs fixing, come to us first. Write from the email or mobile number on your account — that is what lets us confirm it is you before we open the file. Tell us what you want: a copy, a correction, a deletion, or an answer about a payment record. We reply in plain English, say what we can do and what we cannot, and give you a ticket number so a follow-up lands with the same person.

Email the privacy desk Send a message from the address saved on your account so we can match it without extra checks. Say plainly what you need: a copy, a fix, a deletion, or a question about a payment record.
Account help in the app Account help handles privacy requests on the same screen where you check wallet history. Open the payment entry you are asking about and quote its reference, so the agent reads the right record first time.
Payment record questions For a bKash, Nagad, Rocket or Upay transfer you want explained, keep the transaction ID and the amount ready. We trace that reference against your account wallet and tell you what was stored, and why.

Questions About Your Data and Rights

The six questions below are the ones our privacy desk answers most often. They deal with how to see your record, how to close an account, what happens on a new handset, and where a complaint goes. If yours is not here, write to us and we will answer it the same way we answer these. Your data rights do not change with the season — the same steps apply tonight as next month.

Message the privacy desk from your registered email or mobile number. We confirm it is you, then send the record we keep: account details, payment references, login history and any support tickets you have raised.

Yes. Ask from inside your account or by email, and we close it and delete what we are allowed to delete. Payment records tied to local financial rules stay for the period those rules set.

Only with the payment and platform partners who need it to clear a transfer or keep the account working. They act under contract, on our instruction, and cannot use your number for their own marketing.

The new handset gets a one-time code before you sign in. We add that device to your login history, so an old phone can be removed and a sign-in you do not recognise gets flagged.

Two kinds. A session cookie keeps you signed in while you move between the lobby and your wallet, and a preference file remembers your language and screen layout. Both clear from your browser whenever you want.

To the same privacy desk, marked as a complaint, and quote your ticket number if you have one. If our answer does not settle it, raise the matter with the data authority for your area.
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.