Reference

cb4444 Privacy Policy in Short

cb4444 keeps this page short on purpose: it says what we collect when you open an account and pay with bKash, Nagad or Rocket, and how you ask us to change or delete that record.

Details you type inbKash, Nagad, Rocket trailLogin and device recordsAsk us to correct or delete
cb4444 cb4444 Privacy Policy in Short
HOW WE HANDLE IT

How We Keep Your Data Safe

Cookies on cb4444 do one narrow job: they hold your session while you move between the browser on your phone and the desktop you switch to later. Clear them and the lobby forgets you, which is your call to make. Sign-in is guarded by a one-time password sent to your registered number, and every login is written to a list, so a device you do not recognise can be flagged and cut off. Inside our team, only staff who need your file to answer a question can open it, and each time they do, that access is recorded.

Cookies that hold your session

A session cookie keeps you logged in while you switch between phone and desktop. Clear it and you sign in again with a one-time password. We do not use cookies to build ad profiles.

One-time password at login

Your mobile number receives a fresh code whenever you log in from a new device. The code expires quickly, so a forwarded message is not a spare key to your wallet.

Retention with a reason

Sign-in logs stay only while we need them to keep accounts safe. Deposit records for bKash, Nagad and Rocket stay while your account is live, then through the bookkeeping window local rules set.

Asking for a copy

You can request a copy of what we hold on you, or ask us to fix something wrong. We reply from the support desk and tell you plainly when a record has to stay.

HOW TO REACH US

Reaching Us About Your Data

Privacy requests land in one queue and a person reads them, not a bot. Write from the email or mobile number already on your account, so we can match the request to your file without asking for a password. If a bKash transfer made from Dhaka is still showing as pending while you sort a data question, paste the reference into the same message and we will trace it with the wallet side. Keep the ask specific: name the detail you want corrected or removed, and we will say what we can act on and what local record-keeping rules require us to hold.

Account email or chat Write from the email or mobile number saved on your account. That one match lets us open your file without asking for your password or your wallet PIN.
Wallet reference trail Copy the transaction reference out of your bKash, Nagad or Rocket history into the message. It links your data question to the exact deposit record we hold.
Change or delete request State the field you want corrected or removed. We confirm what we can act on and explain any record our bookkeeping has to retain under local rules.

Questions You Ask About Privacy

The same handful of questions come up at the desk, so here they are answered straight. If yours is not listed, message support from the email or mobile number on your account and you will get a reply about your own file, not a generic page.

The details you type in: name, mobile number, email if you add one, and the wallet number you use for bKash, Nagad or Rocket. We also log device, browser and login events.

No. We never hold your wallet PIN and nobody at the desk will ask for it. We store only the transaction reference, the amount and the status of a transfer.

Yes, you can ask, and we act on whatever local rules allow us to remove. Deposit and sign-in records tied to bookkeeping duties usually have to stay for the set period.

Only staff who need it to answer your question or check a payment. Access is logged, so a look at your file leaves a trace. We do not sell details to outside lists.

It can, when our record process or local rules shift. The version on this page is the one that applies to your account, so re-read it after any notice we send.

Message the desk with the time and the device shown in your login list. We cut off that session and send a fresh one-time password so you can secure the account.
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.