Reference

How fg662 Handles Your Personal Information

Your privacy is a practical concern, not a formality — when you use fg662, including when you deposit via bKash, Nagad or Rocket, we collect only what we need to run your account and keep it secure.

Account data protectionbKash, Nagad, Rocket payment privacyYour right to access your dataCookie and device controlsContact us to update records
fg662 How fg662 Handles Your Personal Information
REACH OUR PRIVACY TEAM

Contact Us About Your Data

If you want to access, correct or remove data we hold about you — including payment records linked to your bKash or Nagad wallet — reach out through any of the channels below. Our team handles data requests separately from general account queries, so mention that your message is a privacy request when you write in. We aim to respond within a reasonable timeframe, and we will confirm receipt so you know your request is being handled.

Live Chat Open the chat icon inside your fg662 account. State it is a privacy or data request and our team will route it correctly.
Email Support Send your data access or deletion request to our support email. Include your registered mobile number so we can verify your identity quickly.
Account Settings Some data preferences — including marketing messages and cookie settings — can be adjusted directly inside your account profile without contacting support.
DATA HANDLING PRACTICES

How We Protect and Manage Your Information

Security and transparency are the two pillars of how we handle your data. Your account credentials are encrypted in transit and at rest. Payment flows through bKash, Nagad and Rocket are processed via their own secure APIs — fg662 never stores your wallet password or mobile banking PIN. We review our data handling practices when our systems or third-party integrations change, and we update this policy to reflect those changes.

Encryption in Transit

All data exchanged between your device and fg662 — including account logins and payment confirmations — travels over an encrypted connection to block interception.

Cookie Controls

We use cookies to keep you logged in and to understand which parts of the site you use most. You can adjust cookie preferences from your browser settings at any time.

Retention and Deletion

Account data is held for as long as your account is active and for the period required by financial record rules after closure. Non-essential data can be removed on request.

Third-Party Data Sharing

We share your data only with payment processors like bKash, Nagad and Rocket, and with fraud-prevention services. We do not sell or rent your information to advertisers.

Common Questions About Your Privacy at fg662

These are the questions we hear most often about how fg662 handles personal data. If your question is not here, reach out through live chat or email and mention it is a privacy matter so we can respond appropriately.

We collect your name, mobile number, and the payment method you register — such as bKash or Nagad. We also log your device type and IP address for security purposes.

No. Your wallet PIN is entered inside the bKash or Rocket app, not on fg662. We only receive a transaction reference and the deposit amount — never your PIN or full credentials.

Contact our support team via live chat or email and state it is a data access request. Include your registered mobile number so we can verify your identity before releasing any records.

Yes. You can request deletion of non-essential data at any time. Transaction records linked to your Nagad or bKash deposits may be retained for the period required by financial record rules.

We share data only with payment processors — bKash, Nagad, Rocket — and with fraud-prevention services. We do not sell your personal information to advertisers or unrelated third parties.

Log in and go to your account profile to update basic contact details. For changes to your registered mobile number or linked wallet, contact support with identity verification ready.
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.