Reference

How We Handle Your Data

We collect and protect the information you share when you open your account, deposit through bKash or Nagad, and use our lobby. This policy sets out what we gather, why we need it, and how you control it.

Account data protectionWallet information securityContact preferencesData request optionsRegion-based access
bdj How We Handle Your Data
PRIVACY CONTACT

Reach Us About Your Data

If you want to see what information we hold, update incorrect details, or delete your account, contact our support team through any of these channels. We respond to data requests within a reasonable timeframe and explain what we can provide under the laws that apply to your region.

Team online

Live Chat

Open the chat icon in the bottom-right corner and ask to speak with a data-privacy agent. We handle requests during support hours and log your conversation for follow-up if needed.

Email

Send your request to our support email address. Include your registered mobile number so we can verify your identity before sharing any account information with you.

Account Settings

Log in, head to your profile page, and use the privacy-preferences panel to adjust marketing permissions, session cookies and data-sharing options for analytics providers.

DATA PRACTICE

How We Protect and Retain Information

We encrypt your password and wallet details at rest and in transit. Session data and game history stay on secure servers, accessible only to authorized staff who need them to investigate disputes or fraud reports. We review access logs regularly to ensure no unauthorized queries are run against your records.

Encryption Standards

All payment data — bKash numbers, Nagad wallet IDs, Rocket accounts — is encrypted using industry-standard protocols before it reaches our database, so even internal logs show only masked identifiers.

Retention Period

We keep your account data for as long as your account remains active, plus a further period required by financial and regulatory record-keeping rules. Closed accounts are archived, then purged after that retention window expires.

Cookie Use

We place session cookies to keep you logged in and analytics cookies to measure page performance. You can disable non-essential cookies in your browser, though some features like auto-login will stop working.

Third-Party Sharing

Payment processors see your wallet number to complete deposits and withdrawals. Game studios receive a session token to load live tables and slots. We do not share your contact details with marketing partners outside our platform.

Privacy Policy Answers

We ask for your mobile number, a password, and your preferred payment method — bKash, Nagad or Rocket. If you deposit, we log the wallet account number so we can match incoming transfers and process withdrawals back to the same wallet.

Yes. Contact support through live chat or email with your registered mobile number, and we will send you a summary of your profile details, payment history, session logs and any support tickets you have opened.

Log in, go to account settings, and submit a closure request. We will process it within a few days. Some financial records stay archived for the period required by law, then we purge them from our systems.

We share payment details with bKash, Nagad and Rocket processors to clear deposits and withdrawals. Game providers receive a session token to load the tables and slots you play. We do not sell your information to advertisers or data brokers.

We set session cookies to keep you logged in and analytics cookies to track page performance. You can disable non-essential cookies in your browser settings, but features like auto-login and personalized game suggestions will stop working.

Closed accounts remain archived for the retention period required by financial regulations in the jurisdictions where we operate. After that window expires, we delete your profile, payment history and session logs from our active and backup systems.
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.