Reference

How zerbet Handles Your Personal Data

This Privacy Policy sets out exactly what data zerbet collects when you open an account, make a deposit via bKash, Nagad or Rocket, or contact our support team.

Account data kept securebKash, Nagad, Rocket payment data protectedNo data sold to third partiesRight to request your dataBangladesh-relevant policy scope
zerbet How zerbet Handles Your Personal Data
PRIVACY CONTACT PATHS

Reach Us About Your Privacy

If you have a question about this policy, want to review the data we hold on your account, or need to report a concern, our support team is the right first stop. You can reach us through live chat inside your account dashboard, by email, or via the help form on this site. We aim to respond to all privacy-related requests within a reasonable period and will confirm receipt of your query when we receive it.

Live Chat Open your account dashboard and start a live chat session. This is the fastest way to ask about your personal data or wallet transaction records.
Email Support Send your privacy request by email with your registered phone number and account details so we can locate your record and respond accurately.
Help Form Use the on-site help form to submit a written privacy query. Select the privacy category so it reaches the right team without delay.
DATA HANDLING PRACTICES

How We Protect and Manage Your Data

Data security on zerbet runs across four areas: how we store it, how we use cookies, how we handle your account credentials, and how long we keep everything. We use SSL encryption on all data transfers, including when your bKash or Nagad deposit confirmation passes through our system. Account passwords are hashed and never stored in plain text. We do not share your personal data with advertisers. Cookies can be managed through your browser settings, though disabling them may affect lobby loading behaviour on your device.

Encryption in Transit

All data sent between your device and our servers — including bKash and Nagad payment confirmations — passes through SSL-encrypted connections at every step.

Cookie Controls

Session cookies keep your account logged in and your lobby preferences saved. You can manage or clear cookies through your mobile or desktop browser settings at any time.

Account Security

Your login credentials are hashed on our servers. We send an OTP to your registered phone number for account verification steps so only you can confirm sensitive changes.

Data Retention

We hold your account data while your account is active. Once you request closure and deletion, we remove your personal records in line with applicable legal retention requirements.

Common Questions About This Privacy Policy

These are the questions we hear most often about how zerbet handles personal data, account records and payment information. If your question is not covered here, use the live chat or help form to reach our support team directly.

We collect your name, phone number, email and date of birth at registration. When you deposit via bKash, Nagad or Rocket, we also log the payment reference linked to that transaction.

No. Your wallet PIN stays entirely within the bKash or Nagad app. We receive only the transaction reference and amount confirmation — never your PIN or full wallet credentials.

Contact our support team via live chat or the help form with your registered phone number. We will locate your account record and share a copy of the data we hold on you.

Yes. Submit a deletion request through email or the help form. We will close your account and remove your personal data, subject to any legal retention periods that apply in your eligible region.

We do not sell or share your personal data with advertisers. We share data only with payment processors like bKash, Nagad and Rocket strictly to process your transactions.

Cookies save your session state so the lobby loads correctly when you return. You can clear them in your browser settings, but this may require you to log in again on your next visit.
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.