Reference

How hp 6666 Handles Your Personal Information

When you open an account with us, we collect only what we need to run your wallet, process payments through bKash, Nagad or Rocket, and keep your account secure.

Account data onlybKash, Nagad, Rocket payment contextNo third-party sale of your dataYour right to request changesBangladesh-region eligibility applies
hp 6666 How hp 6666 Handles Your Personal Information
PRIVACY CONTACT PATHS

Reach Us About Your Privacy Rights

If you want to see the data we hold, correct something, or ask us to remove non-transactional records, contact our support team directly. We aim to acknowledge your request promptly and work through it in order. For account-wallet queries tied to bKash, Nagad or Rocket transactions, have your registered mobile number ready so we can match your request to the right account record.

Team online

Live Chat

Open the chat widget inside your account dashboard. Describe your privacy request and we will log it and assign a case reference for follow-up.

Email Support

Send your request to our support address listed in your account settings. Include your registered mobile number and the nature of your data query.

Account Settings

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

DATA HANDLING PRACTICES

How We Protect and Manage Your Account Data

We apply SSL encryption across all account pages and payment flows, which means your login session and any wallet reference — whether bKash, Nagad or Rocket — travels over an encrypted connection. Our internal access controls mean only the team members who need your data to resolve a support case or process a withdrawal can see it. We review these controls on a routine basis. Your data is never sold to advertisers or shared with unrelated third parties.

SSL Encryption

Every account session runs over SSL. Your login credentials and payment wallet references are encrypted in transit, not readable in plain text by third parties.

Cookie Management

Session cookies keep your lobby state intact between pages. You can block or clear these via your browser, though some account features may behave differently without them.

Retention Schedule

Transaction records are kept for as long as platform operation requires. Non-transactional profile data is removed on a rolling schedule once your account is closed.

Third-Party Limits

Payment processors handling bKash, Nagad and Rocket transfers receive only the minimum data needed to confirm a transaction. No marketing profiling is shared externally.

Common Questions About Your Data Rights

Below are the questions we hear most often about how we handle account and payment data. If your question is not covered here, reach us through the live chat in your account dashboard or via the support email shown in your account settings.

We collect your name, contact details, and the mobile wallet identifier — bKash, Nagad or Rocket — you use for transactions. Device type and IP address are logged for security purposes.

No. Your bKash PIN and Nagad credentials are never stored on our servers. Payment confirmation flows through each wallet provider's own secured system; we only receive a transaction reference.

Yes. Contact support via live chat or the email in your account settings with your registered mobile number. We will log your request, assign a case reference, and respond accordingly.

Transaction records are retained as long as platform operation and applicable standards require. Non-transactional profile data is removed on a rolling schedule after account closure.

We do not sell your data or share it with advertisers. Payment processors for bKash, Nagad and Rocket receive only what is needed to confirm your transaction, under contractual data-protection terms.

Open your account settings and adjust communication preferences there. You can also contact support to request removal from marketing messages without closing your account.
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.