Reference

How bde22 Handles Your Personal Information

This privacy policy explains exactly what data we collect when you open an account, make a deposit via bKash, Nagad or Rocket, and use our platform — and how we keep that data secure.

Account data protectionbKash, Nagad, Rocket payment privacyCookie and device data clarityYour right to access or delete dataBangladesh-region eligibility applies
bde22 How bde22 Handles Your Personal Information
PRIVACY CONTACT PATHS

How to Reach Us About Your Data

If you want to request your data, correct inaccurate information, or ask us to remove your account details, our support team handles these requests directly. Reach us through any of the channels below and mention that your query is a privacy or data request so we can route it to the right team without delay.

Live Chat Start a chat session from any page on bde22. Mention 'data request' in your opening message so the agent handles it as a privacy query immediately.
Email Support Send your data request to our support address. Include the mobile number linked to your bKash, Nagad or Rocket wallet so we can verify your account ownership.
Account Help Page Log in and open the Account Help section. You can submit a data access or deletion request directly from there, and we will confirm receipt by message.
HOW WE PROTECT IT

Data Handling, Cookies and Account Security

We apply encryption to your account data at every stage — from the moment you enter your registration details to when a withdrawal is verified against your Nagad or Rocket wallet number. Cookies on bde22 track session state and preferences only; we do not use cookies to build advertising profiles or share browsing data with ad networks. Your account security relies on OTP verification tied to your registered mobile number, which means any login attempt from an unrecognised device triggers an additional confirmation step.

Encryption in Transit

All data moving between your device and our servers is encrypted. This covers your login details, payment references and any document you upload for account verification.

Cookie Policy

We use session cookies to keep you logged in and preference cookies to remember your chosen language and payment method. No third-party advertising cookies are set by us.

OTP Account Security

Your account is tied to your mobile number. Any login from a new device requires an OTP sent to that number, reducing the risk of unauthorised access to your wallet details.

Data Retention and Deletion

We hold your data only as long as your account is active or as required by law. Submit a deletion request and we will confirm the outcome within a reasonable processing period.

Common Questions About Your Privacy on bde22

These are the questions we hear most often about how bde22 handles account and payment data. If your question is not here, reach out through live chat or email and we will respond with a clear answer about your specific situation.

We collect your name, contact details and the mobile wallet number you register with — typically your bKash, Nagad or Rocket number. Device and IP data are also logged for security.

We share only the minimum transaction data that bKash, Nagad or Rocket need to process your payment. We do not sell your data to marketers or unrelated third parties.

Log in, go to Account Help and submit a data access request, or email our support team. Include the mobile number linked to your wallet so we can verify your identity quickly.

Yes. Submit a deletion request through live chat or email. We will process it in line with our retention schedule and confirm once your account data has been removed.

We use session and preference cookies only — no advertising profiles. You can adjust cookie settings in your browser, though disabling session cookies may affect how your account loads.

Access and eligibility depend on your local law and eligible region. The data practices described here apply to supported accounts; check with support if you have region-specific questions.
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.