Reference

How m123456 Handles Your Personal Information

When you open an account with m123456, you share personal and payment details with us — and this policy explains exactly what we collect, why we collect it, and how we keep it secure.

Account data protectionbKash, Nagad, Rocket payment privacyCookie and device data clarityYour right to request changesBangladesh-region scope
m123456 How m123456 Handles Your Personal Information
PRIVACY CONTACT PATHS

How to Reach Us About Your Data

If you want to access, correct or delete the personal data we hold on your account, you can contact our support team directly. We handle privacy requests separately from general account queries so your request reaches the right person without delay. Eligibility to exercise specific data rights depends on your local law and the region your account is registered in.

Team online

Live Chat

Open the chat widget from your account dashboard. Privacy requests made through live chat are flagged and routed to our data team within one business day.

Email Support

Send your privacy request to our support email address listed in your account settings. Include your registered mobile number so we can verify your identity before acting.

Account Settings

Some data preferences — such as marketing communication opt-outs and cookie settings — can be adjusted directly inside your account settings without contacting support.

DATA HANDLING PRACTICES

How We Protect and Manage Your Information

Keeping your account data secure is not a side concern — it is built into how the platform operates. Every section below reflects a real operational practice, not a general promise. What we do with your data is specific, auditable and tied to your account actions, including deposits via bKash, Nagad and Rocket.

Payment Data Security When you transact via bKash, Nagad or Rocket, only the masked wallet reference reaches our servers. Full PIN and wallet credentials never pass through or get stored on our side.
Cookie Controls We use session cookies to keep you logged in and analytics cookies to see which account flows work well. You can review and limit non-essential cookies from the preferences panel in your account.
Data Retention Account records — including transaction history linked to your bKash or Nagad deposits — are retained for the period required by applicable regulations in your eligible region, then deleted or anonymised.
Access and Correction You can request a copy of the personal data we hold on your account, or ask us to correct inaccurate details. We verify your identity before processing any such request.

Common Questions About Your Privacy at m123456

These are the questions we actually receive about how personal data is handled on this platform. If your question is not covered here, reach out via live chat or email from your account settings.

We collect your name, mobile number, and the payment method you register — typically bKash, Nagad or Rocket. Device data and session logs are also recorded for account security purposes.

No. We never store your mobile wallet PIN. Only the masked transaction reference returned by your wallet provider after authorisation is saved against your account record.

Retention periods follow the requirements of applicable regulations in your eligible region. Once a retention period ends, data is deleted or anonymised. Contact support if you need region-specific details.

Yes. Send a data access request via your registered email or through live chat. We verify your identity first, then provide a summary of the personal data held on your account.

Data is shared only with payment processors — including the mobile wallet providers handling your Rocket, bKash or Nagad transactions — and only to the extent needed to complete those transactions. We do not sell data to third-party marketers.

Go to your account settings and locate the communication preferences section. You can turn off marketing emails and SMS notifications there without contacting support. Changes take effect within one business day.
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.