Reference

What Our Privacy Policy Actually Covers

This page sets out what we collect when you open a bdg222 account, why we keep it, and how you can ask us to change or delete it.

Account detailsPayment recordsDevice and login dataCookie choicesDeletion requests
bdg222 What Our Privacy Policy Actually Covers
HOW WE HANDLE IT

Data Handling, Cookies and Account Security

Your login is protected by a one-time code sent to the mobile number you registered — no code, no entry, even if someone has your password. Sessions expire on shared devices, which matters if you check your wallet balance on a tea-stall phone. Cookies are split into two jobs: the ones that keep you signed in, and optional analytics you can refuse without losing access.

One-time code at login

Every sign-in needs a code sent to your registered number. If the code never arrives, check the SIM is in the handset before trying again.

Cookie control

Session cookies keep you signed in and cannot be switched off. Analytics cookies are optional, and refusing them changes nothing about your access.

Retention window

Transaction records stay while money-movement law requires them. Profile data goes once an erasure request clears the checks.

Correction requests

Spotted a wrong name or a stale mobile number? Ask in writing and we verify it against your ID before editing the record.

ASK THE DESK

Who to Contact About Your Data

A privacy question is not the same as a payment complaint, so we route it to a separate desk that reads and answers in writing. Send the mobile number on your account and the specific right you are exercising — a copy, a correction, or erasure. If your concern is a wallet transfer that failed, use live chat instead and the payments team will pull the reference.

Team online

Written privacy request

Email the desk with your registered mobile number and what you want changed. You get a written reply so there is a record both sides can point to later.

Live chat for account issues

For a stuck deposit or a locked login, chat is quicker than email. An agent can see the bKash, Nagad or Rocket reference on your account and act on it.

Data deletion route

Ask in writing and we close the account, then strip personal fields while keeping the transaction trail the law requires us to hold.

Privacy Questions We Get Asked

These are the questions that reach our desk most often, answered the way we would answer them in chat rather than in legal wording.

Your registration details, your wallet reference for bKash, Nagad or Rocket payments, and login records showing device and time. We do not store your wallet PIN or any card number.

Yes. Write to the privacy desk from the mobile number on your account and we compile what we hold, then send it to you in writing.

Only with the payment providers that process your transfers, and with a regulator or court where Bangladesh law compels it. We do not sell data.

Send a written erasure request. We close the account and remove personal fields, though transaction records stay for the period the law demands.

Only the session cookies that keep you signed in. Analytics cookies are optional, and refusing them does not block the lobby, the wallet or a cash-out.

Tell the desk immediately so we can lock the login and review recent wallet activity. Change your password and your one-time code starts again from scratch.
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.