Reference

How We Handle Your Information

We collect what we need to run your account, process your bKash, Nagad and Rocket deposits, and keep the lobby accessible. This policy explains what we gather, how we use it, and the choices you have.

Account dataPayment recordsDevice access logsCookie preferencesWithdrawal verification
bad 22 How We Handle Your Information
POLICY QUESTIONS

Contact Us About Your Privacy

If you want to review the information we hold, request deletion after closing your account, or ask how a specific piece of data is used, reach us through any of these channels. We respond to privacy enquiries within a few business days, faster for urgent access requests.

Live chat Open the chat widget at the bottom right of any page. Tell the agent you have a privacy question and they will route it to the compliance team who handle data requests.
Email support Send your enquiry to the support email listed in the site footer. Include your registered mobile number so we can verify your identity before discussing account data.
Account settings Log in, open Account Settings, then Privacy Controls. You can download a copy of your bet history, payment records and profile details as a CSV file from that screen.
DATA SECURITY

How We Protect Your Information

Your account sits behind SSL encryption and requires an OTP sent to your mobile each time you log in from a new device. Payment records for bKash, Nagad and Rocket are tokenised so the full transaction string never appears in our front-end logs. We review access permissions quarterly and limit data visibility to the staff who process withdrawals and verify accounts.

Encryption standard

Every page on bad 22 runs over HTTPS. Your login credentials, wallet PINs and withdrawal requests are encrypted in transit so they cannot be intercepted on public Wi-Fi or mobile networks.

Cookie controls

We set a session cookie to keep you logged in and a preference cookie to remember your language choice. You can block third-party cookies in your browser without breaking the lobby or payment flow.

Data retention

We keep your account information and transaction history for the duration required by the payment processors we partner with, typically several years after account closure. Inactive marketing data is purged sooner.

Request changes

You can update your registered mobile number, email address and password in Account Settings. To request full data deletion, close your account first, then contact support with your registered details for identity verification.

Common Privacy Questions

We ask for your mobile number, a password, and your date of birth to verify you meet age requirements. When you make your first deposit via bKash, Nagad or Rocket, we log the transaction ID and wallet account name for reconciliation.

We share transaction details with the payment processors that clear your bKash, Nagad and Rocket deposits, and with game providers to load your bet history in slots and live tables. We do not sell your information to advertisers or data brokers.

Yes. Log in, go to Account Settings, then Privacy Controls. Download your account data as a CSV file. It includes your profile details, deposit and withdrawal records, and recent bet history from the sportsbook, slots and live casino.

Close your account in Account Settings. After closure, contact support with your registered mobile number and request data deletion. We will erase personal information once the mandatory financial record retention period has passed.

We set a session cookie to keep you logged in and a language-preference cookie. Both are first-party. Third-party cookies from analytics tools can be blocked in your browser settings without affecting the lobby or payment flow.

We store the transaction ID and the account name that appears on your payment receipt, not your wallet PIN or full account credentials. Your wallet app handles the authentication, and we receive only a confirmation token when the transfer completes.
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.