Privacy Rules We Follow for Your 33bd login Account

We delete session logs after twelve months unless they are part of an open dispute or audit request. Transaction records for bKash, Nagad and Rocket deposits stay on file for five years to comply with financial record-keeping rules, but your mobile number and device token are removed within thirty days if you close your account. Marketing consent records are kept indefinitely so

we do not accidentally contact you after you opt out. If you never log in for twenty-four months, we send a reminder SMS to your registered number; if you do not respond within ninety days, we archive your account and delete your session history, keeping only the transaction ledger for regulatory purposes. Game studios like Pragmatic Play and Evolution have their own

retention schedules — typically they purge player session data after six months — so contact them directly if you want your gameplay history removed from their servers.

Every time you log in, we record your mobile number, device identifier and IP address so we can verify withdrawals and block duplicate accounts. When you send a bKash, Nagad or Rocket deposit, we store the transaction ID, amount and timestamp to match your payment against your account wallet. We also keep session logs that show which game you opened, how long

you stayed, and whether you placed a bet — this helps us spot unusual activity and respond to support queries. We never share your payment details with third parties outside our payment processor and game-studio partners, and we delete inactive session logs after twelve months. If you request account closure, we archive your transaction history for regulatory record-keeping but remove your mobile

number and device token within thirty days.

We pass your mobile number and transaction amount to our payment gateway when you deposit via bKash, Nagad or Rocket; the gateway confirms the transfer but does not receive your password or game history. Game studios like Pragmatic Play and Evolution see your player ID and bet history when you open a slot or live table, but they never receive your real

name or payment details. If you contact support, our agents read your account logs and recent deposits to answer your question, and those chat transcripts are stored for six months. We do not sell your data to advertisers, affiliate networks or data brokers. When local law requires us to report suspicious transactions, we share only the minimum fields the authority asks for

— typically transaction ID, amount and timestamp — and we notify you unless the request prohibits disclosure.

If we change how we collect, share or delete your data, we post the new version on this page and email a summary to your registered address if you provided one. Material changes — like adding a new payment processor or extending retention periods — are flagged at the top of the notice with a revision date. You have thirty days to

review the update; if you disagree with the new terms, withdraw your balance and close your account before the effective date. Continuing to log in after the revision date means you accept the updated rules. We do not apply retroactive changes to data we already collected under the old policy, so if we shorten our retention period from twelve months to six,

records created before the change still follow the original twelve-month schedule. For questions about a specific revision, contact support with the policy version number shown at the bottom of this page.

All data traveling between your phone and our servers is encrypted with TLS so no one can intercept your password or bKash transaction ID on public Wi-Fi. We store passwords as salted hashes, meaning even our database administrators cannot read your original password if they look at the raw table. Session tokens expire after twenty-four hours of inactivity, forcing you to log

in again if you leave the app open overnight. We run daily backups of your account wallet and transaction history, but those backups are encrypted at rest and stored in a separate facility so a server breach does not expose your payment details. When you request a withdrawal, we send an OTP to your registered mobile number and wait for you to

confirm before releasing the funds — this two-step check blocks unauthorized transfers even if someone steals your password.