Reference

What Our Privacy Policy Covers

Your account runs on one mobile number and a wallet, and this page sets out what we keep beside that — device data, cashier references, your cookie choice — and how you get any of it removed.

Phone-number sign-upCookie choicesAccess and deletionWallet referencesSupport contact path
bbajie What Our Privacy Policy Covers
DATA PRACTICE

Cookies, Security and Record Keeping

Sign-in security and data handling sit in one place, because most leaks start with a borrowed session rather than a broken server. We hash your password, ask for a fresh code when a new handset appears, and keep the payment trail narrow — a reference number, the taka amount, the time it cleared. Cookies do the boring work: holding you signed in between lobby and cashier, remembering your language and last table. Retention follows what a record is for, not habit, so logs that no longer help us spot a stolen session get dropped.

Hashed credentials

Your password is stored as a one-way hash, so nobody on our side reads it back. Login from a new handset asks for the code sent to your number before the wallet opens.

Cookies we set

A session cookie keeps you signed in between pages; a preference cookie remembers your language and last game. You can clear both in your browser without losing your account balance.

Retention windows

Payment records stay while local accounting rules require them. Login logs and device identifiers are dropped once they stop helping us catch a stolen session, and stale marketing lists go with them.

Your request path

Ask for a copy, a correction or a deletion and we confirm the number first, then act. Some payment records have to stay, and we name which ones and why.

CONTACT PATHS

Where to Send a Privacy Question

Privacy questions land with the same team that handles your wallet, so there is no second queue to chase. Open your account, head to Support and pick the privacy topic — the thread already carries your number, which saves the back-and-forth of proving who you are. If a payment reference from bKash, Nagad or Rocket is part of the question, paste the transaction ID. We never ask for your PIN or the code sent to your handset.

In-app support chat Open your account, tap Support, and pick the privacy topic. The thread stays linked to your number, so you never need to repeat an old case.
Signed-in request Ask for a copy, correction or deletion of your account data from the same screen. We reply inside the thread once we confirm the number is yours.
Wallet queries Questions about a bKash, Nagad or Rocket reference sit with the same team. Send the taka amount and the transaction ID so we can match it, without sharing your PIN.

Questions About Your Data

These are the privacy questions that come up most in our support threads, answered the way we would answer them there. If yours is not listed, send it through the in-app channel with your account number attached and we will take it from the top.

A mobile number, a password and the wallet you plan to use. Nothing else is needed to sign in; extra details like a full name appear only when a payment partner asks for them.

Yes. Raise deletion from the in-app support thread. We close the account and remove profile data, but a bKash, Nagad or Rocket payment record may be held longer where local accounting rules require it.

Only to the payment processor handling your transfer and the hosting provider that runs our servers, both under written terms. We do not sell contact lists or hand your number to outside advertisers.

Cookies keep you signed in as you move between the lobby and the cashier. Clear them and you simply log in again with the code sent to your number; your balance and game history stay untouched.

Your local law has the final word. Access depends on the rules of your region, and if a clause here conflicts with a statutory right you hold, that right applies in place of the clause.

A short window only. Device and login entries are dropped once they stop helping us spot a stolen session, while payment records follow whatever retention period your local accounting rules set.
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.