Reference

How We Handle Your Account Information

We collect what we need to run your wallet, verify bKash and Nagad deposits, and keep your account secure. This policy explains what we gather, how long we keep it, and who can request changes.

Account verificationPayment recordsDevice access logsContact dataSession cookies
8999 to taka How We Handle Your Account Information
DATA PRACTICE

How We Secure and Store Your Information

We encrypt your password with bcrypt before storing it, and we transmit all payment data over TLS so your bKash PIN and Nagad account number are never visible in plain text. Session cookies expire after twenty-four hours of inactivity, and we delete archived support tickets after six months unless a dispute is still open.

Encryption standard

Account passwords use bcrypt hashing, and all traffic between your device and our servers runs over TLS.

Cookie usage

We set a session cookie to keep you logged in, an analytics cookie to count page views, and a device-fingerprint cookie to flag unusual login locations.

Retention period

Active account records stay live as long as your account is open. After you close your account, we archive transaction logs for six months to handle any late dispute, then delete them unless financial regulations require longer retention.

Third-party sharing

We share your transaction amount and reference code with bKash, Nagad and Rocket to verify deposits. We share session and bet totals with game providers to reconcile fairness audits.

PRIVACY CONTACT

How to Reach Us About Your Data

If you want to see what we have on file, correct a mistake in your account record, or ask us to delete your information, contact our privacy team through any of the channels below. We aim to respond within three business days.

Email inquiry Send your request to our support address with your registered mobile number so we can verify your identity before sharing account data. Attach a screenshot if you are reporting an error in your transaction history.
Live chat request Open the chat widget in your account dashboard, tell the agent you want to discuss privacy or data access, and they will escalate your request to the privacy team within the same session.
Account settings Log in and visit the privacy tab under account settings to download a summary of your deposit records, login history, and contact details we hold. Deletion requests still require email or chat verification.

Common Questions About Your Data

Below are the questions Bangladesh account holders ask most often about how we collect, use and protect their information. If your question is not covered here, contact support through the channels above.

We collect your mobile number, a password you create, your device fingerprint from the first login, and your IP address. If you deposit via bKash, Nagad or Rocket, we also log the transaction ID and amount for wallet reconciliation.

We pass your transaction reference to the payment provider to verify the deposit, but we never see or store your wallet PIN. Game studios receive only session totals and bet history, not your payment details or mobile number.

We archive deposit and withdrawal logs for six months after account closure to resolve any late dispute or chargeback claim. After that period we delete the records unless financial regulations require us to retain them longer.

Yes. Log in, go to account settings and open the privacy tab, then click download data report. You will receive a file with your deposit history, login timestamps, device list and contact details within a few minutes.

We use a session cookie to keep you logged in, an analytics cookie to count visits, and a device-fingerprint cookie to detect unusual login patterns. You can block analytics and fingerprint cookies in your browser; the session cookie is required.

Email our support address or open a live chat session with your registered mobile number. Tell us what needs correction or deletion, and we will process the request within three business days after verifying your identity.
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.