qdc88 Privacy Policy: How We Handle Your Information
qdc88 collects only the information needed to run your account, process wallet activity through bKash, Rocket or Upay, and keep your session secure across devices. This policy tells you exactly what we collect, why we collect it, and what choices you have — clearly, without legal fog.
Account data only
bKash, Rocket, Upay context
Your rights, clearly stated
No third-party data selling
POLICY AT A GLANCE
What This Privacy Policy Covers
When you open an account with us, we collect the details you provide during registration — your name, email address, contact number and the wallet identifiers linked to your bKash, Rocket or Upay transactions. We also record session data: the device type, browser, IP address and pages visited during each login. This helps us maintain account continuity so you pick up exactly where you left off, whether you switch from mobile browser to desktop or return after a gap. We do not sell, rent or share your personal details with third parties for their own marketing. When a payment processor such as bKash or Rocket handles a deposit or withdrawal, they receive only the transaction data needed to complete that transfer — nothing beyond it. We retain account records for as long as your account remains active and for a reasonable period after closure, in line with applicable rules. Availability of this service and the scope of data handling depend on your local law and eligible regions. If you have questions about the data we hold, the support routes listed on this page are the right place to start.
bKash
Transaction references passed to bKash cover only the data needed to complete your deposit or withdrawal. No additional profile data is shared with the payment processor beyond what the transfer requires.
Rocket
Rocket payment flows receive a session token and transaction amount only. Your full account record stays within our platform and is not visible to the Rocket processing layer.
Upay
Upay top-up requests are handled through an encrypted handoff. We pass the minimum fields required by Upay to confirm and record the transaction on your account wallet.
INSIDE AND OUTSIDE
Where This Policy Applies
This policy covers everything that happens under your qdc88 account — from the moment you log in to the activity recorded in your wallet history. It does not govern the practices of third-party services you reach from our pages, including external payment processors and game content providers. Understanding the boundary helps you know exactly what we are responsible for and what falls outside our control.
Account Access
Login sessions, device records and authentication steps on qdc88 are fully within this policy. We log access events to protect your account from unauthorised use and to restore your session on a new device.
Wallet Transactions
Deposit and withdrawal records processed through bKash, Rocket or Upay are covered by this policy on our side. The payment provider's own privacy terms govern what they do with their slice of the transaction data.
Site Content
Pages, game lobbies and account dashboards you browse on qdc88 are within scope. Browsing data such as page-load times and session duration is collected to improve navigation and account continuity on mobile.
Third-Party Services
Game content providers, external links and payment gateways operate under their own privacy policies. We do not control their data practices. Check their published terms before sharing information with those services directly.
WHAT YOU CAN DO
Your Practical Rights Under This Policy
You have real, actionable choices about the information we hold. Start by logging into your account — the account settings area shows the profile details we currently hold on file, including your contact number and linked wallet identifiers. If something is wrong or out of date, you can correct it directly from that screen without contacting support. For records you cannot edit yourself, such as historical transaction logs tied to a bKash or Rocket transfer, you can raise a data query through our support channel and we will review what can be amended or explained. If you want to know exactly what data we hold in full, submit a written request via the support route listed in this policy. We aim to respond to data queries in a reasonable timeframe, though exact timelines depend on the complexity of the request. Closing your account does not automatically erase all records — some data is retained as required by applicable rules. We will tell you what remains and why when you make that request.
Review Your Records
Log into your account and open the profile section to see the contact details, wallet links and verification status we currently hold. This is the fastest way to check your stored information without contacting support.
Correct Account Details
Edit your name, email or contact number directly from account settings. For wallet identifiers tied to bKash, Rocket or Upay, follow the update steps shown in the wallet section of your account dashboard.
Raise a Data Query
If you want a full record of what we hold or need to flag an inaccuracy in your transaction history, contact us through the support route listed on this page. Describe the specific record or data point in question.
Request Account Closure
You can request account closure through support. We will explain which records are retained after closure and the reason for retention, in line with the applicable rules for your eligible region.
REACH US DIRECTLY
How to Contact Us About This Policy
If you have a question about the data we hold, want to correct a record or need clarification on how this policy applies to your account, use the contact routes published on qdc88. We do not list operating hours or response-time commitments here because those details are shown in your signed-in account area — check there for the current published routes.
Live Chat
Open the chat widget from any page on qdc88 while logged in. Describe your privacy query clearly — include your registered contact number or account email so the support team can locate your record without delay.
Email Support
Send a written data query to the email address published in the Contact section of your signed-in account. Written requests are useful for data-access queries because they create a record of your request and our response.
Account Help Centre
The Help section inside your account covers common privacy questions, including how wallet data from bKash, Rocket and Upay transactions is stored. Start there before contacting support — many answers are already published.
HOW WE HANDLE DATA
Our Data Handling Practices
We keep the data we collect limited to what is operationally necessary. Cookies on qdc88 are used to maintain your login session and remember your device between visits — not to build an advertising profile. Account security steps such as session tokens are applied at login; if you notice unexpected activity, the account security section lets you review active sessions and take action. Data we no longer need is deleted or anonymised on a rolling basis, subject to any retention period required by applicable rules in your eligible region.
Cookies and Sessions
We use session cookies to keep you logged in across pages and to restore your place in the lobby when you return on the same device. You can clear cookies through your browser settings, though this will end your current session.
Account Security
Each login generates a session token tied to your device and IP. Unusual login attempts are flagged in the account activity log. Review active sessions from your account security settings and close any you do not recognise.
Data Retention
We keep transaction records linked to bKash, Rocket or Upay activity for as long as your account is active and for a period after closure, as applicable rules require. Records beyond that period are deleted or anonymised.
Policy Changes
When this policy changes in a material way, we publish the updated version on this page with a revised effective date at the top. Continuing to use your account after a published update means you have seen the new terms.
PRIVACY QUESTIONS
Privacy Policy Questions Answered
Common questions about what we collect, how we use it, and how your rights work in practice — answered plainly so you know exactly where you stand.
What personal information does qdc88 collect when I open an account?
We collect your name, email address, contact number and the wallet identifiers you provide during registration. When you make a deposit or withdrawal through bKash, Rocket or Upay, we also record the transaction reference and amount against your account wallet.
Does qdc88 share my data with third parties?
We do not sell or rent your personal data. Payment processors such as bKash or Rocket receive only the minimum transaction data needed to complete your transfer. Game content providers do not receive your personal account details. Each third party operates under its own privacy policy.
How do I see what data qdc88 holds about me?
Log into your account and open the profile section — that shows your stored contact details, wallet links and verification status. For a full data record including historical transaction logs, submit a written request through the email support route listed on this page.
Can I correct wrong information in my account?
Yes. Most fields — name, email, contact number — can be edited directly from account settings while you are logged in. For wallet identifiers tied to bKash, Rocket or Upay, follow the update steps shown in the wallet section. For anything else, contact support.
What happens to my data if I close my account?
Closing your account does not delete all records immediately. Transaction logs and identity verification data may be retained for a period required by applicable rules for your eligible region. We will explain exactly what is retained and why when you make a closure request through support.
Does qdc88 use cookies and what are they for?
We use session cookies to keep you logged in and to restore your account position when you return on the same device. We do not use cookies to build advertising profiles. Clear cookies through your browser settings if you prefer — note that doing so will end your current login session.