Reference

What Our Privacy Policy Covers

Your account details, your bKash or Nagad transaction history and your session data all sit under one privacy policy, written in plain English instead of legal fog. What applies to you depends on your local law and eligible regions.

Plain-English policyWallet records explainedCookie controlsDeletion requests
bk33org What Our Privacy Policy Covers
SECURITY AND RETENTION

How bk33org Protects Account Data

How your data is held matters more than how the policy reads. Whether you sign in from Chattogram or Dhaka, the steps are the same: mobile number, one-time code, then the account, with each session checked against the device that opened it. Cookies are yours to clear. Retention follows what the record is actually for. And if you want something corrected or removed, the request runs through the same account-care desk that answers your wallet questions.

Sign-In Checks

Each login uses a one-time code sent to your registered number. A session opened from an unrecognised device is flagged before it gets anywhere near your wallet balance.

Cookie Choices

Session cookies keep you signed in and carry your language setting. Analytics cookies are optional. Clear them in browser settings and the account area will simply ask you to sign in again.

Retention Rules

Transaction records stay while the account is open, plus the accounting period that follows. Login logs are held for a shorter stretch. We tell you which applies when you ask.

Change Requests

Ask for a correction, a copy of your records, or closure of the account. We confirm what can be changed and what must be kept under accounting rules before anything is removed.

REACHING OUR TEAM

Where to Send Privacy Requests

One page is useless if you can't reach a person about it. Privacy requests come through three routes, and each one leaves a ticket you can follow. Write from the mobile number or email already linked to your account — that is how we match a request to the right record without asking you to send ID twice. If the question is about a wallet transfer, quote the bKash, Nagad or Rocket reference number and we can trace it.

Account Care Chat Sign in, open the help panel and pick the privacy topic. The agent already sees your account history, so you won't repeat the same details twice.
Data Request Email Send your correction or copy request from the email on your account. Include your registered mobile number so the team can locate the right profile without a back-and-forth.
Wallet Reference Line For anything tied to a transfer, quote the bKash, Nagad or Rocket reference. It lets us pull the matching transaction record while you are still in the chat.

Privacy Questions You Send Us

These are the questions our account-care desk hears most about data, so we've answered them without the legal padding. If yours isn't here, write in with your registered number and the topic — a correction, a copy, a closure — and we'll reply on the same thread. Nothing here changes how your wallet behaves: bKash, Nagad and Rocket transfers still follow their own app rules, and access to the lobby depends on where you are and what your local law allows.

Your registration details, the wallet you register with, transaction references, login logs, device type and IP address. Bet and game records are stored too. We never hold your wallet PIN or your Rocket password.

Only with the wallet operator or bank that has to clear the transfer, and with staff handling your account checks. We don't sell payment records and we don't pass them to advertisers.

Write from the email or mobile number linked to your account and ask for a copy. We confirm the request first, then send the record once it has been matched to your profile.

You can ask us to close the account at any time. Transaction records stay for the accounting period that follows closure; other data is removed once that obligation ends.

An idle account keeps its transaction history until the retention period ends. Sign-in logs are cleared sooner. You can request closure instead of leaving the account dormant for years.

Session cookies are needed to stay signed in and move between the lobby and your wallet. Clear them and you'll be asked to sign in again. Analytics cookies remain optional.
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.