Reference

Privacy Policy: How We Handle Your Account Information

We collect what we need to run your account, process bKash and Nagad deposits, and keep your login secure. You control your data—request access, corrections or deletion through support any time.

Account data stored securelyWallet details encryptedRequest your data anytimeSupport responds within hoursDevice session tracking
oktaka Privacy Policy: How We Handle Your Account Information
PRIVACY CONTACT

Reach Us About Your Data

Three ways to ask about your information, request a copy of what we hold, or delete your account. Live chat gets you an answer fastest; email works when you need to attach identity documents for a deletion request.

Live Chat Open the chat bubble on any page, choose privacy as your topic, and ask for an export of your data or to close your account. An agent typically replies within minutes during peak hours.
Email Support Send your request to the support address listed in account settings. Include your registered mobile number so we can verify the account. We respond within one business day with next steps or the file you requested.
Account Settings Log in, tap your profile icon, scroll to privacy controls. You can download a JSON export of your transaction history, turn off promotional messages, or start the account-closure process from that screen.
DATA SAFEGUARDS

How We Protect What You Share

We encrypt bKash and Nagad wallet identifiers in transit and at rest, require device verification for new logins, and purge session tokens when you log out. Our payment processor is PCI-compliant; we do not store card CVVs or wallet PINs on our servers.

Encryption Standard

All data moving between your device and our servers travels over TLS. Wallet account numbers and personal identifiers are encrypted in the database using AES-256 so even internal staff see masked values unless a support case requires access.

Cookie Usage

We set a session cookie to keep you logged in and an analytics cookie to track which pages load slowly on mobile. You can block analytics cookies in your browser; the session cookie is required for account access.

Retention Period

We keep transaction records for five years to meet payment-processor audit requirements, then anonymize them. Marketing consent logs are kept until you withdraw consent. Device fingerprints expire after ninety days of inactivity.

Your Rights

You can request a copy of your data, correct inaccurate details, object to marketing messages, or ask us to delete your account. Support walks you through identity verification, then processes most requests within three business days.

Common Questions About Your Data

We collect your mobile number, the wallet account you use for deposits—bKash, Nagad or Rocket—your device type and IP address. That set lets us match payments, verify logins and show your balance when you open the app.

We share wallet identifiers with our payment processor only when you initiate a deposit or withdrawal, so funds route to the correct account. We do not sell wallet data or pass it to advertisers.

We retain bet logs and deposit records for five years to meet payment-processor and regulatory audit requirements, then we anonymize the data. You can request a full export through account settings at any time before that.

Yes. Contact support via live chat or email, verify your identity with your registered mobile number, and request account closure. We delete non-regulatory data within three business days and anonymize the rest after the retention period.

We use a session cookie to keep you logged in and an analytics cookie to track page-load speed. You can block analytics in your browser settings; the session cookie is required for the account to function.

Log in, open account settings, and tap privacy controls. Choose download my data and we will generate a JSON file with your transaction history, wallet details and session logs. The export usually arrives within a few minutes.
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.