Reference

How Jetabat Handles Your Privacy

We collect only what keeps your account wallet secure and your mobile session moving — nothing more. Every bKash, Nagad or Rocket transaction you approve, plus the cricket markets or slot rounds you open, gets logged for verification and stays out of any outside…

Account wallet protectionDevice session logsPayment verification recordsNo outside ad sharing
Jetabat How Jetabat Handles Your Privacy
REACH OUR PRIVACY TEAM

Where to Ask About Your Data

Privacy questions don't always come up at a convenient moment, so we've built more than one way to reach us from inside your account. Whether you're checking what's logged against a bKash, Nagad or Rocket transaction or asking why your session shows an unfamiliar device, the same support flow applies — no separate ticket system to learn. Pick the channel that fits where you are: live chat inside the mobile site, an account-linked message thread, or email tied to the mobile number you registered with.

Team online

Account Data Requests

Write to our support desk from the email tied to your registered mobile number and we'll confirm what account data, wallet reference logs or session history we hold before any changes are made.

Live Chat on Mobile

Open live chat from inside your account on the mobile site or app wrapper — the same channel handles login issues and privacy questions, and replies land in the same session thread.

Wallet Verification Queries

If a bKash, Nagad or Rocket transaction reference looks wrong on your statement, raise it through support so we can check the matching record without exposing it to anyone outside that verification step.

DATA HANDLING STANDARDS

How Jetabat Secures Your Account Data

Keeping account data locked down isn't a one-off setting — it's a routine we run every time you log in from a new device. Encrypted sessions cover both the mobile site and the lightweight app wrapper, cookies stay limited to lobby preferences rather than tracking you across other sites, and retention periods shrink once a dispute or reconciliation case closes. If something on file looks outdated, raising it through support starts a verification step before any record gets changed or removed.

Session Encryption

Login sessions on both the mobile site and app wrapper run over encrypted connections, so OTP codes and device identifiers stay unreadable if a network is intercepted along the way.

Cookie Controls

Cookies remember lobby settings like the last table you opened in Baccarat GlistenZone, and you can clear them through your browser or app settings without losing account access.

Retention Windows

We hold identity-verification and dispute records only while account security or reconciliation needs them, then move older logs into limited archive access before deletion.

Requesting Changes

To correct a registered mobile number, update contact details or ask what's on file, message support from your account and we'll walk through the verification step needed first.

Common Questions About Your Privacy Policy

Most questions about this policy come down to three things: what we store, how long we keep it, and who can ask us to change it. Below are the ones that come up most from Bangladesh account holders moving money through bKash, Nagad or Rocket, checking session history, or asking about account closure. If your question isn't covered here, the same support channels listed above will pick it up directly from your account.

We collect your mobile number, device type, login times and the wallet reference tied to bKash, Nagad or Rocket transactions you approve — enough to verify it's you and settle disputes fairly.

Yes — message support from your registered account and ask for a summary of stored data; we confirm your identity first, then share what's on file once that check is done.

No — wallet references are matched against your account only for fraud checks and payment reconciliation, and we don't pass that reference to outside marketing or advertising lists.

We hold identity and transaction records only as long as security, dispute handling or reconciliation genuinely need them, then archive or remove older logs from active systems.

You can request closure through support; wallet references and support-ticket logs may stay briefly for reconciliation before removal, and availability depends on your local law and eligible region.

Yes — the same data-handling rules apply whether you sign in through the mobile browser or the lightweight app wrapper, so switching between them doesn't change what we log.
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.