Reference

How We Handle Your Information

We collect what we need to run your account, process bKash, Nagad and Rocket deposits, and keep the lobby secure. Everything else stays optional.

Account securityWallet activityRegional accessContact controlCookie choices
4333 App How We Handle Your Information
DATA PRACTICES

What We Protect and How

We encrypt payment instructions between your device and our servers, separate wallet credentials from game logs, limit staff access to account records, and archive inactive profiles. Each layer addresses a different part of the data lifecycle.

Payment Security bKash, Nagad and Rocket deposits pass through SSL channels; we store transaction references, not wallet PINs. Withdrawal requests trigger OTP verification before funds move, and we log every approval for audit trails.
Cookie Management Session cookies keep you logged in; analytics cookies count lobby visits and device types. You can decline optional tracking on first visit or change preferences later in account settings without affecting core wallet functions.
Access Control Support staff see only the account fields needed to resolve your query; finance teams access wallet logs for reconciliation; technical staff monitor session security. No single role views the complete profile outside regulated audit scenarios.
Retention and Deletion Transaction records stay active for account verification; marketing preferences persist until you opt out; session logs expire after logout. Request full data export or account closure through support, and we process it per regional data-protection norms.
PRIVACY CONTACT

Reach Us About Your Data

Questions about what we collect, how long we keep it, or how to request changes reach our support desk the same way account queries do. We handle data requests during business hours and respond within the timeline local practice expects.

Live Support Open the chat icon in the lobby footer for account, wallet and privacy questions. The desk handles data-access requests, cookie queries and marketing opt-outs during active hours.
Email Inquiry Send data requests, retention questions or consent changes to the support address listed in account settings. Include your registered mobile number so we can verify identity before sharing records.
Account Settings View active sessions, connected devices, marketing preferences and cookie consent status under your profile. Update contact details, toggle promotional messages or request data export directly from the panel.

Common Data and Privacy Queries

We ask for your mobile number, account password and preferred payment method during sign-up. Wallet transactions through bKash, Nagad or Rocket add transaction IDs and timestamps to your profile for deposit and withdrawal reconciliation.

Transaction logs remain active for account audits and wallet verification. If your account stays dormant for an extended period, we may archive records under banking retention practice, but you can request export or deletion through support anytime.

Session cookies keep you logged in and are required for core wallet functions. Analytics and marketing cookies are optional; you can decline them on first visit or adjust preferences later in account settings without losing access to the lobby.

We share transaction data only with payment providers to process bKash, Nagad and Rocket deposits, or with authorities when local regulation requires disclosure. We do not sell contact lists or send wallet logs to advertisers.

Log in, open account settings, and submit a data-export request. Include your registered mobile number so we can verify identity. We process requests during business hours and deliver the file per regional data-protection timelines.

We archive transaction logs for regulatory retention, then delete marketing preferences and session records. Contact support to request full closure, and we walk you through the steps, including final wallet balance and data-removal confirmation.
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.