Live / Mobile
puts its terms for account access, transactions and site use in one place so you know what applies before you register. Where a rule depends on local law, we say so plainly, and access itself stays tied to local law and the regions we serve.
We set these terms as the baseline for using qdc88. They cover the moment you reach the lobby, the account record we keep for you, and the transfers you run through the payment rails we support. This includes bKash, Nagad and Rocket where they are offered, and we only point you to a rail that shows in your account at the time you are on it. A few things stay outside what we can promise. Availability depends on local law and eligible regions, so a feature that is open in one place may not be open in another. We do not state a legal outcome for your situation; if a question sits at the edge of the rules, we point you to the published support route instead of guessing. We may update these terms as the site or the rules change. When we do, the current copy on this page is the one that applies. We do not read changes as applying backwards to something that already happened. For anything in dispute, the route is to raise it with support first, then we go through what each side sees in the record.
This policy sits in four places at once, and each one answers a different question. It governs how you reach the account, what counts as a transaction, the content you open in the lobby, and the services we hand to outside providers. Knowing which bucket your question falls into tells you which part of the page answers it, and it also stops a term written for one area from being read onto another. A payment rule, for example, is not the same as a content rule, and we keep the wording separate so there is no drift. We also say plainly where a piece is someone else's to run, because a rail operated by a partner carries its own terms. If you are unsure where a point sits, the safe move is to raise it rather than assume, because we answer from the copy we publish and not from a guess.
This covers who can register and how your log-in works. Eligibility stays tied to local law and eligible regions, so whether you can hold an account depends on the rules where you live. We keep the access steps the same from browser to browser and phone to phone.
Deposits and withdrawals through bKash, Nagad or Rocket fall here, along with the wallet we attach to your account. The rules for a transfer are the ones shown in your account at the time you run it. We record each one so you can look it back.
The games and pages you open in the lobby, and the way they are presented, sit inside our terms. This includes the studios we carry and the categories you can browse. It does not change what a single game does; each title carries its own rules.
Where a payment rail or a partner is run by someone else, their own terms apply to that piece. We describe what we control and point at what we do not. When you move to a provider, that service runs under the rules they publish.
Each of these parts reads as a real path, not just a promise. First, the record we hold for you is open to you: you can pull up the history of transfers and log-ins tied to the account and read it back line by line. Second, when a detail is wrong, you can ask for a correction, and we align the record to what you send us. Third, a rule that is not clear to you is a fair thing to put to us directly, and we answer from the copy we actually publish rather than from a guess. Fourth, if a transfer will not go through or an action is blocked, the support route is the starting point and we keep the exchange in the record so both sides can follow it. Nothing here is a script; you choose which of these you act on and when.
Your account keeps a record of the transfers and log-ins tied to it. You can open that history and read it back at any time. If anything looks off, note it and send it through the route in support. We answer what we see.
If your name, contact or wallet details are wrong, you can request a correction. We ask you to update from the account page, because that is where the fields live. We then align the record to what you sent, assuming it matches the checks we run.
When a rule does not read clearly, write to us instead of guessing. Tell us the page you were on and the point you are unsure about. We take the question to the copy we publish and come back with the answer we can support.
For anything blocked, refused or just not working, go to the published support route and start there. Tell us the device you were on and what you saw. We keep the conversation in the record so the next step is clear to both of us.
Every term above is reachable through a route on the site itself, so you are never sent off looking for a channel nobody can verify. The support area is where you raise a correction, a blocked action or a rule you do not follow. From there you are pointed to the wallet help topics for a transfer question, and to the account help topic for anything about your own record. The one thing we do not do here is list an hour range or a separate phone line, because the page is the route and it holds the answer we can stand behind.
The support area is where you start for anything on this page. Open it from the main menu and you can read the help topics tied to accounts, wallets and access. It covers what these terms describe, without needing to leave the site.
From the account page, the help link takes you to the rules that apply to your own record and transfers. That is the place to raise a correction or a blocked action. We have not set an hour range here, because the page is open whenever you are.
Questions about a bKash, Nagad or Rocket move land in the wallet help topics. They walk through what a transfer needs and where to look for the record. If the topic does not cover it, the support area is the next step.
How we handle this policy area is set out in one place so you are not left digging. The data you give us runs the account and the transfers you start, and session cookies keep you signed in across the pages you visit on the same device. We keep records for as long as the account needs them and trim what is no longer required, which is the part most people ask about. Account security is tied to the sign-in you set up and the device checks you can see on the account page, so the measure we actually use is the one you can verify. If something should change in the record, the route is the support area, and we confirm the change through the same path you used to reach us. We avoid holding anything longer than the account needs it, and we answer a retention question from the record rather than from habit.
The details on your account are used to run the service and to show you your own record. We do not build a profile for anything you have not asked for. What leaves the site does so only through a service you are using.
Session cookies keep you signed in across the pages you visit on the same phone or browser. They are tied to your device, not to something we publish about you. You can clear them from the browser and sign back in fresh.
Security is built around the sign-in and device checks on the account page. We ask you to keep your own detail current so the checks line up. When you sign in, the account page is where you confirm the device you are on.
Records stay for as long as the account needs them and are trimmed once they are no longer required. To change what we hold or to ask how long we keep it, go through the support area. We confirm the request in the record.
These are the points people raise most often after reading the terms. Each answer points back to a rule on this page, so you can read it yourself before you act.
Access stays tied to local law and eligible regions, so the terms describe what we run, not a promise that runs everywhere. If a feature is closed where you live, the rule on the page is the one that applies. The support area answers what is open for you.
Open the account page and update the fields that are wrong, then use the support route to confirm it. We align the record to what you sent and keep the change visible. A record that did not go through stays noted for you.
Yes. Your account keeps a list of the transfers you ran through bKash, Nagad or Rocket along with log-in events. Open the history from the account page and read it back. If a line does not match, note it and raise it through support.
The terms follow the rails that show in your account at the time you use them, including bKash, Nagad and Rocket where offered. If a rail is not available in your region, it will not appear. The wallet help topics describe what each needs.
We keep records for as long as the account needs them and trim what is no longer required. If you want a specific detail removed or confirmed, ask through the support area. We keep the conversation tied to your record so you can follow it.
Start at the support area from the lobby and describe the step where it stopped, plus the device you were on. We work from what you saw and the record we hold. We resolve it through the published route, not by guessing.