Reference

Privacy Policy How We Handle Your Information

We collect account details, payment data and device information when you use 33db. This policy explains what we gather, why we need it, how long we keep it, and the controls you have over your own data.

Account dataPayment recordsDevice infoCookie useYour rights
33db Privacy Policy How We Handle Your Information
DATA PRACTICES

How We Protect & Manage Your Information

Account security, data encryption, cookie management and retention schedules are all part of how we handle the information you provide. Below are the key areas we focus on to keep your data secure and give you control over what we collect.

Account Security

Every login is protected by OTP sent to your registered phone. Session tokens expire after inactivity, and you can force-logout all devices from the security panel. We hash passwords and encrypt sensitive fields in our database.

Payment Data

When you deposit via bKash, Nagad or Rocket, we store the transaction reference, amount, timestamp and wallet identifier. Full wallet credentials never reach our server; the payment gateway handles sensitive details and passes us only a confirmation token.

Cookie Policy

We use session cookies to keep you logged in, preference cookies to remember your language and interface choices, and analytics cookies to understand how visitors navigate the site. You can disable non-essential cookies in your browser settings.

Data Retention

Active account records are kept for the lifetime of your account plus any period required by law. Inactive accounts may be archived after extended non-use, and you can request deletion by contacting support with proof of identity.

PRIVACY CONTACT

How to Reach Us About Your Data

If you have questions about what data we hold, want to request a copy, ask for corrections, or submit a deletion request, use any of the channels below. We aim to respond within a reasonable timeframe and will verify your identity before processing data requests.

Email Inquiry Send your privacy question or data request to our support email. Include your registered phone number or account identifier so we can locate your record and confirm ownership before sharing any information.
Live Chat Open the chat widget in your account dashboard to ask about data handling, cookie settings or how to update your contact details. The agent will verify your identity before discussing account-specific information.
Account Settings View and update your email, phone number and communication preferences directly in the account-settings panel. Some changes require re-verification via OTP to protect your account from unauthorised edits.

Common Questions About Data & Privacy

We collect your phone number, email address, date of birth and chosen password. When you deposit, we also log your bKash, Nagad or Rocket transaction reference and the amount sent to verify the payment.

Yes. Contact support via email or live chat, verify your identity with your registered phone number, and request a copy of your data. We will send a summary of account details, transaction history and device logs.

Email support with your registered phone number and request account closure. We will verify your identity, settle any pending balances, then delete or anonymise your record in line with legal retention requirements.

We share transaction data with bKash, Nagad and Rocket to process deposits and withdrawals, and with game providers to deliver live tables and slots. We do not sell your data to advertisers or data brokers.

We use session cookies for login state, preference cookies for language and layout, and analytics cookies to measure traffic. Essential cookies are required; you can block non-essential cookies in your browser settings without losing core functionality.

Transaction logs are retained for the period required by applicable law and internal compliance. After your account closes and the retention period ends, records are either deleted or anonymised so they cannot be linked back to you.
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.