Reference

How gd66 Handles Your Personal Data

When you open an account with us, we collect only what we need to run it — your contact details, wallet identifiers for bKash, Nagad or Rocket, and device activity tied to your sessions.

Account data onlybKash, Nagad, Rocket wallet contextNo data sold to third partiesYour rights explained clearlyContact us to request changes
gd66 How gd66 Handles Your Personal Data
DATA HANDLING STANDARDS

How We Protect and Manage Your Account Data

We apply SSL encryption to all data in transit between your device and our servers, which means your bKash wallet token and account credentials are not readable in transit. Internally, access to personal data is restricted to staff with a specific operational need — payment reconciliation, fraud review or account verification — and logged for audit. Cookie use on gd66 is limited to session management and basic analytics; we do not drop advertising or cross-site tracking cookies without your explicit consent.

SSL Encryption Every connection between your device and gd66 uses SSL. This covers login sessions, wallet data for bKash, Nagad and Rocket, and account preference changes.
Cookie Controls We use session cookies to keep you logged in and analytics cookies to understand page load issues. You can manage or withdraw cookie consent through your browser settings at any time.
Data Retention Transaction records tied to Nagad, bKash or Rocket payments are retained as long as dispute and regulatory requirements demand. Browsing session logs are cleared on a rolling schedule.
Access Requests You can request a copy of the personal data we hold, ask us to correct inaccuracies or request deletion where no legal retention obligation applies. Use the support paths on this page.
PRIVACY CONTACT PATHS

Reach Us About Your Privacy

If you want to access, correct or delete the personal data we hold on your account, contact our support team directly. You can reach us through live chat inside your account dashboard, by email at the address listed on the Contact page, or via the in-app support form on mobile. We aim to acknowledge privacy requests within a reasonable period and will confirm the outcome in writing.

Team online

Live Chat

Open your account dashboard and tap the chat icon to send a privacy request. Our team handles data queries through the same channel as account support.

Email Support

Send your request to the email address on our Contact page. Include your registered phone number so we can match it to your account record.

In-App Form

On mobile, go to Account Settings and select Support Request. Choose the Privacy category and describe what you need changed, corrected or removed.

Your Privacy Questions Answered

Below are the questions we hear most often about how gd66 handles personal data — covering wallet details, cookies, account access and how to submit a data request. Availability of all services depends on your local law and eligible regions.

We collect your name, phone number, email and the wallet reference you link — bKash, Nagad or Rocket. We also log device type and session timestamps for security purposes.

No. We store only the transaction reference token returned by the payment processor. Your mobile banking PIN and full wallet credentials are never passed to or held by us.

Yes. Contact us via live chat or email with a deletion request. We will remove data where no legal retention obligation applies and confirm the outcome in writing.

We use session cookies for login continuity and basic analytics cookies for page performance. You can disable non-essential cookies through your browser settings without losing account access.

We share your data only with payment processors needed to complete bKash, Nagad or Rocket transactions, and with fraud-detection partners. We do not sell your data to advertisers.

Open the in-app support form under Account Settings, select the Privacy category and request a data export. Include your registered phone number so we can verify ownership quickly.
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.