Reference

How We Handle Your Information

We collect and process the information needed to run your account, verify bKash and Nagad deposits, protect your wallet and respond when you contact support. This policy sets out what we gather, why we need it and how you control it.

Account verificationPayment processingDevice recognitionSupport recordsCookie preferences
52222 How We Handle Your Information
PRIVACY CONTACTS

Reach Us About Your Data

If you want to see what information we hold, correct a detail or ask us to delete your account, our support channels handle privacy requests the same way we handle wallet questions. You can ask about data access, retention periods or cookie settings through any of the contact paths below.

Live Chat Open the chat widget in the account menu and select privacy request from the topic list. Our team confirms your identity before sharing or updating personal records so your data stays protected.
Email Support Send your data request to the support email shown in your account footer. Include your registered mobile number and describe what you need; we respond with next steps or the information you asked for within a few business days.
Account Settings You control marketing preferences, session history visibility and cookie consent directly from the privacy tab in your account dashboard. Changes take effect immediately without contacting support.
DATA PRACTICES

How We Protect Your Privacy

We built account security, payment verification and support logging around the data-handling principles below. Each practice explains what we collect, how we use it and where you have control so you understand what happens when you deposit via bKash, browse the lobby or contact our team.

Payment Data We store your bKash, Nagad or Rocket account identifier to process deposits and verify withdrawal requests. Card details for bank transfers are tokenised by the payment processor; we never see or store your full card number or PIN.
Session Cookies When you log in, we set a session cookie to keep you authenticated as you move between the lobby, wallet and support pages. You can clear cookies from your browser or opt out of analytics tracking in account settings.
Device Recognition We log your device type, browser and IP address to detect unusual login patterns and prevent account takeover. If we see a new device, we send an OTP to your registered mobile before granting access to your wallet balance.
Data Retention Transaction records are kept for financial compliance; support chat logs are archived for six months. If you close your account, we delete marketing preferences and session data but retain transaction history as required by payment-processing regulations.

Common Data Questions

We collect your mobile number for account verification and OTP login, your payment identifiers for bKash, Nagad or Rocket deposits, and your device IP address to enforce regional access rules and detect fraud.

Yes. Contact support via live chat or email with your registered mobile number and we will send you a copy of your account profile, transaction history and support tickets within a few business days.

We share transaction data with bKash, Nagad, Rocket and bank processors only to complete your deposits and withdrawals. We do not sell your information to advertisers or unrelated marketing platforms.

Request account closure through live chat or email support. We delete your profile, marketing preferences and session cookies but retain transaction records as required by financial compliance and dispute-resolution obligations.

We use session cookies to keep you logged in, preference cookies to remember your language choice and analytics cookies to measure lobby traffic. You can disable analytics tracking in your account privacy settings.

When you request a cashout, we check your registered mobile number against the bKash or Nagad account you provided at signup. If details do not match, we ask for wallet ownership proof before releasing funds.
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.