Reference

Privacy on bk6699, Written Plainly

This page sets out what we hold when you open an account, what we do with it, and how you get it changed.

Mobile number loginbKash, Nagad, Rocket referencesCookie choices you controlCopy or correction on request
bk6699 Privacy on bk6699, Written Plainly
HOW DATA MOVES

How Your Data Moves Through Our Systems

Handling data here is deliberately dull. Your password is stored hashed; a one-time code sent to your phone completes the sign-in; wallet references from bKash, Nagad and Rocket stay attached to the account they belong to, so a mismatch can be checked later. Records tied to money are kept for the period local rules set. Cookies stay narrow: session, language, security. If something in this paragraph surprises you, the support routes above are the place to push back.

What we store

Your mobile number, the name on the account, wallet references from bKash, Nagad or Rocket payments, and the phone, browser and sign-in times behind each session. Nothing beyond that is needed.

Cookies we set

A session cookie keeps you signed in, a language cookie remembers your choice, and a security cookie helps us spot a hijacked session. Clearing them signs you out; your account is untouched.

Keeping the login yours

Your mobile number plus a one-time code is the whole login, so the SIM and the phone lock stay in your hands. Tell us the day a wallet number changes.

Retention and your requests

Transaction records stay for the period the rules in your jurisdiction require, then go. Ask for a copy, a correction or a deletion and we work through it with you.

ASK US DIRECTLY

Where to Send a Privacy Question

Privacy questions should not sit in a general chat queue for a week. Message us from the account you are asking about, so the session, device and wallet details you mention are already in front of the person reading your message. If it touches a bKash, Nagad or Rocket transfer, paste the wallet reference in the same message. For a copy of what we hold, or a correction, put the request in the first line so it reaches the right queue.

Team online

Signed-in chat

Open chat from your profile while signed in. We can see the session, device and wallet reference you are asking about, so you are not asked to prove ownership twice.

Email to support

Write from the number on file and put the wallet reference in the first line if the question touches a bKash, Nagad or Rocket transfer. Replies come back on the same thread.

Formal data request

Ask the agent to log your message as a data request rather than a general query. It reaches the team that handles account records instead of sitting in the general queue.

Questions You Ask About Your Data

The six questions below come up most often in chat, usually from someone who has just changed phones or spotted a wallet number they do not recognise. Read them before you message us — the answer may already be here. If yours is not covered, ask anyway and we will point you to the right record.

Your mobile number, the name you registered with, the wallet references from payments you have made, and basic device and browser details from your sign-ins. That is the working set behind your account.

Yes. Open chat from your signed-in account and ask for a copy. The reply comes on the same channel as a written record, so you have something you can keep or forward.

The sending wallet number and the reference returned with a payment are how a transfer gets matched to your account, and how a payment that fails mid-way gets traced back to the right person.

Say which field is wrong and what it should read. Account details we fix ourselves; a deletion request is checked against the record-keeping rules that apply where you live before we act.

Only after you tick the box for it, and you can untick it whenever you want. Login alerts, wallet changes and security checks always go out, because those keep the account in your hands.

Running an online account means data can pass through systems outside the country. What may be transferred, and on what basis, depends on the law where you live and eligible regions.
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.