Reference

Privacy Policy at bg1111, Explained Plainly

We keep the privacy side simple: what you hand over when you open an account — your mobile number, your bKash, Nagad or Rocket reference, your device ID — is used to run your account, verify wallet payments and keep login safe.

OTP loginWallet references onlyCookie controlsRequests by email
bg1111 Privacy Policy at bg1111, Explained Plainly
DATA HANDLING RULES

Cookies, Security and Record Keeping

Four things decide how your data sits with us: what we hold, which cookies run, how a login is checked, and how long records stay. Each one has a fixed rule we follow, and each one is something you can ask us about by email. We do not add extra fields for marketing, and we do not move account data into a third-party list. Here is how the four pieces work in practice.

Data we hold

Your mobile number, wallet name and the bKash, Nagad or Rocket reference you send us — that is the core. We never ask for your wallet PIN or bank password, and you should not send them to anyone.

Cookies

Two kinds run here: a session cookie that keeps you signed in, and a preference cookie that remembers your language and last room. Clear them in your browser whenever you want; the next login needs a fresh OTP.

Login checks

Every login runs through an OTP to your registered mobile number. A new device triggers the code again. Change that number only from inside a signed-in session, so nobody else can redirect your codes.

Keeping records

Account records stay while your account is open, and for a set period after closure where local record-keeping rules apply. Once that period ends, the records are deleted or stripped of anything that identifies you.

POLICY CONTACT DESK

Where to Send a Privacy Request

Reach us on the policy side the same way you reach account help. Email works for anything written — a copy of your records, a correction, a deletion request — and a signed-in request from account settings is logged with a reference number you can quote later. Whichever you pick, send it from the mobile number registered on your account. That is how we confirm the request is really yours before we touch anything.

Privacy email Email our privacy desk with the mobile number on your account and what you need changed. Correction, copy of records, deletion request — say which one. We reply to the number or address you registered with.
Signed-in request Open account settings and use the data request option. The form asks for your registered mobile number and the type of request, then logs a reference you can quote back to us later.
Cookie questions Ask us which cookies run on the lobby and why. Borderline case with a device you share? Tell us and we will explain what the session cookie stores and what clearing it removes.

Privacy Questions You Send Us Most

The six questions below come up most often in account help chats, and most of them are shorter to answer than people expect. If yours is not here, email is the simplest route — quote your registered mobile number so we can pull the right account. Access to the site itself still depends on your local law and eligible regions, and that applies to data requests too.

Your mobile number, your name as it appears on your bKash, Nagad or Rocket wallet, and the reference for any transfer you send. Device data such as browser and IP address is recorded automatically when you sign in.

No. We share account data with payment partners and service providers only where a transfer, a login check or a legal duty needs it, and only as far as that single check goes.

Yes. Email the privacy desk from your registered number and ask for a copy of your account records. We confirm it is you first, then send the file to that same number or address.

Send a deletion request by email or from account settings. We close the account, then remove or anonymise the records once the local record-keeping period for that data has run out.

Yes, and it needs to be. That reference is what ties your transfer to your account wallet, so it stays attached while the account is open and through the record-keeping period that follows.

Clear them in your browser settings, or block third-party cookies there. The session cookie that keeps you signed in will drop too, so expect a fresh OTP at your next login.
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.