Reference

What the bn88vip Privacy Policy Covers

Your account here holds a short list of facts — mobile number, the name on your wallet, and the reference your bKash, Nagad or Rocket deposit returns.

Name, number and wallet reference onlyNo wallet PIN, everCookie choices you controlAsk us to fix or close your file
bn88vip What the bn88vip Privacy Policy Covers
REACH THE DESK

Where to Send Data Requests

Every privacy request moves through the help panel inside your account, so we can match it to the right file before anyone replies. Open your profile, tap Help and pick the data option — the thread stays in your inbox and carries the ticket number you will need if you follow up. If you cannot sign in at all, write to the contact address on our support page from a device you normally use. Telling us which wallet you pay with, bKash, Nagad or Rocket, saves a round of questions.

In-account help panel Open your profile, tap Help and choose the data request option. Your message is logged with a ticket number, so you can follow the same thread until an answer lands.
Support email If sign-in fails, write to the address listed on our support page from a device you usually use. Include the mobile number on the account so we can trace your file.
Wallet verification desk For anything tied to a payment record, the verification desk pulls the transaction ID from your bKash, Nagad or Rocket receipt and matches it against what sits on your account.
SECURITY AND STORAGE

Security, Cookies and Storage

Security around your file is plain on purpose. Sign-in needs the OTP sent to your registered number, and a session from an unfamiliar device is challenged before it can reach your wallet. Passwords are hashed rather than stored as text, and the payments team sees the reference your wallet returns, not your PIN. Cookies do a smaller job: one holds your session, one remembers your language, one measures page load on mobile. Retention follows purpose — transaction records stay while payment rules require them, and a switched-off marketing preference goes straight away.

Account security

Your password is hashed and sign-in confirms through an OTP to the number you registered. A new device or browser is asked to confirm itself before it reaches your wallet.

Data handling

Payment details we keep are limited to the references your wallet returns. Staff see what the task needs and nothing more, and files are not left open on a shared screen.

Cookie control

Session, language and page-speed cookies run on this site. Blocking them in your browser still lets you read these pages, though staying signed in needs the session cookie left on.

Changing your record

Ask us to correct a wrong name or close an unused account and we work it through the same thread. Logs tied to payment rules are kept until that duty ends.

Privacy Questions You Send Us

Most of what reaches our inbox comes back to the same handful of points: what we keep after a deposit, who inside the company can open a file, and how a detail gets corrected. The answers below are the short version. If yours is not here, the help panel inside your account reaches the people who can actually look at your record.

The mobile number on your account, the name registered to your wallet, and the transaction ID bKash returns. We use that reference to match the payment to your wallet and for nothing else.

Only with the partner that has to complete your transfer or verify your identity, and only the detail that task needs. We do not sell your data or hand it to advertisers.

Raise it in the help panel inside your account and we confirm what we hold — registration details, sign-in logs and payment references. If you cannot sign in, use the support address on our support page.

Send the correction through your account help thread with a clear photo of the name on your wallet. Matching your account to the bKash, Nagad or Rocket record is the step that lets us change it.

The account goes dormant and the file closes to staff who do not handle payment records. Transaction logs stay while payment rules require them, then come off our retention schedule.

Not for reading pages, yes for staying signed in. The session cookie is what holds your login between taps; clear it and you simply confirm again with an OTP.
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.