Reference

Your Data, Explained in Plain Words

Your account runs on your mobile number, your wallet details and a short login trail — this page sets out exactly what we hold and what we never see.

bKash and Nagad recordsOTP login trailCookie choicesCorrection requests

Explore the Lobby Read FAQ

ACCOUNT HELP DESK

Reaching the Team That Holds Your Records

Privacy requests reach the same people who handle wallet verification, so you are not passed around. Open the app, go to Support, pick Privacy request and say what you need — a copy of your records, a correction to the name on your account, or the closure of the account itself. Add your registered mobile number so we can match you without asking for a password. If the issue touches a bKash, Nagad or Rocket payment, keep the transaction ID ready.

Team online

In-app privacy request

Open Support inside the app, choose Privacy request, and send the details from your registered number. We reply on the same thread, so you do not need to repeat your case to a new agent.

Account data copy

Ask for a copy of what we hold and we confirm your identity with a one-time code first, then send the record tied to your mobile number. Names, wallet references and login history come together.

Payment record trace

If a bKash, Nagad or Rocket transfer looks wrong, share the transaction ID and the amount in BDT. We match it against the deposit record and tell you what our side shows.

SECURITY AND RETENTION

How We Protect and Clear Account Data

Every login runs through a one-time code sent to your registered number, and a new handset has to clear that code before the account opens. Passwords are stored hashed, so nobody on our side reads them. Cookies do a small, visible job: one keeps you signed in while you move between the wallet and a table, another remembers the device you verified, and the rest only count page loads. Retention is deliberate — login logs are cleared quickly, while payment records stay as long as partner and tax rules require.

Login and device checks

One-time codes go to your registered number, and a fresh handset must clear that code before the lobby opens. If a login looks foreign to your usual device, we ask again rather than let it through.

Cookies on mobile

A session cookie keeps you signed in while you move between the wallet and a table. A second one remembers the device you verified. Clear them in your browser settings any time; you re-enter the code.

Retention windows

Transaction records stay while payment partners and tax rules ask for them, then go. Login logs and device flags are held briefly for security checks. Account details are removed once the closure request clears your verification.

Changes and corrections

Spotted a wrong name or an old number on your profile? Send the correction through the app and we update the record once your identity is confirmed. Ask what we hold in the same request.

How We Collect, Store and Share Data

54bd Service availability depends on eligible regions and local law. Users should check local rules before opening an account.

We collect three kinds of data. First, what you type in: your mobile number, the name on your wallet and the password you set when you open an account. Second, what a payment creates — when you cash in or out through bKash, Nagad or Rocket

1
we keep the transaction reference, the amount in BDT and the wallet number on either side, because that record is what lets support trace a deposit that has not landed. Third, device data: handset model, browser or app build, and the IP address on a login,
2
which we use to spot a session that does not look like yours and to send the one-time code when you sign in from a new phone. We never store your wallet PIN, your bKash or Nagad balance or a full card number, and we do
3
not sell account data. Sharing stays with the parties who keep the service running: the payment rails moving your money, the studios whose titles you open, and anyone we must answer by law. Transaction records stay as long as payment-partner and tax rules ask; login logs
4
are kept short and then removed. Whether you can hold an account at all depends on your local law and eligible regions, so confirm that before you register.

Service availability depends on eligible regions and local law. Users should check local rules before opening an account.

Questions About Your Account Data

Most privacy messages we get ask the same four things: what is stored, who sees it, how long it stays, and how to get it removed. The answers sit below in plain words. If yours is not there, the Support tab inside the app reaches the team that actually holds the records, not a call centre reading from a script. Keep your message short; we will ask for anything else we need.

Your mobile number, the name on your wallet and a hashed password. After that come deposit and cash-out references from bKash, Nagad or Rocket, plus the device and IP attached to each login.

No. You enter the PIN inside the wallet app on your own phone, never on our page. We receive only the confirmation that a transfer cleared, with its reference and amount in BDT.

Open the app, tap Support, then Privacy request. Confirm the one-time code we send to your registered number and we compile the record held against it, then reply on the same thread.

Yes. Request closure through Support and we verify you first, then shut the account and clear the profile. Payment references stay while tax and partner rules require them, and we tell you what remains.

No. A studio gets an account ID and the session needed to run its title, like Pragmatic Play or PG Soft tables in the lobby. Wallet numbers and payment references never leave our side.

Clearing browser data wipes the cookie that remembers your verified device, so we ask again. Say yes and the session holds across the wallet and the lobby; say no and you re-enter the code on arrival.

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.

InfoLegal Info54Bd Banking InfoBlackjack PlayZone

Your Data, Explained in Plain Words

Reaching the Team That Holds Your Records

In-app privacy request

Account data copy

Payment record trace

How We Protect and Clear Account Data

Login and device checks

Cookies on mobile

Retention windows

Changes and corrections

Questions About Your Account Data

01 What details does 54bd keep after I open an account?

02 Do you ever see my bKash or Nagad PIN?

03 How do I ask for a copy of my account data?

04 Can I close my account and have the records removed?

05 Do game studios see my wallet number?

06 Why does 54bd ask about cookies each time I clear my browser?

Privacy Policy

Related pages

Related pages