Slots / Casino
This page sets out how dct88 handles the legal side of your account — what we ask of you, what you can ask of us, and where your local law decides the rest. Access depends on your local law and eligible regions, so read the points below before you open an account and fund a wallet.
Every account on dct88 runs under the same set of rules, and we publish them here rather than hiding them behind a login. When you open the account page, you agree to use the lobby as it is presented to you: real-money play is for adults, one account per person, and the details you provide must be your own. We do not decide for you whether online play is allowed where you live. That is settled by your local law, and eligibility can differ by region, so check your own position before you fund a wallet. Money moves through named rails, not through us directly. Deposits and withdrawals pass through bKash, Nagad, Rocket, Upay or a bank transfer, and each provider applies its own conditions as well. If a provider declines a transfer, that decision sits with them. We keep the transaction reference so a payment can be traced back to your account rather than argued about. The rest of this page answers the practical questions: what sits inside our policy and what belongs to a third party, what you can change or ask for, and where to write when something looks wrong. If any clause here conflicts with a law that applies to you, the law wins and we update the wording.
A short list keeps things clear. Our policy governs your access to the account area, how we hold the details you give us, how transaction records are kept and how you reach our support team. It does not govern the wallet apps themselves, the networks they run on, or the studios whose titles appear in the lobby. If bKash or Rocket changes how a transfer is confirmed, that rule applies to you as a customer of theirs, and their terms sit alongside ours rather than under them. Also outside this page: the outcome of any game round, which follows the rules published for that title, and the laws of your own country, which we cannot rewrite. Where the two overlap, we follow what we are required to follow. Read on for the parts you can actually act on — checking records, correcting a detail, asking a question and getting an answer from a real route.
Your login, the details saved on your profile and the way you reach the lobby all sit inside this policy. If you cannot sign in, or you spot a saved detail that is wrong, raise it with support and we will walk you through the published steps on the account page.
Deposits and withdrawals made with bKash, Nagad, Rocket, Upay or a bank transfer fall under this policy in one direction only: we keep the record and you can trace it. The wallet provider's own rules still apply to the transfer itself, including anything they ask of you.
Headings, category pages and the way titles are listed in the lobby are ours to manage. We can add, retire or relabel a category without notice. What this policy covers is how that content is presented to you, not the outcome of any single round you open.
Wallets, studios and any external pages you reach from our site are separate services with their own terms. We do not control their decisions, their uptime or their account rules. If a question belongs to them, we will say so plainly instead of passing it around.
You are not stuck with whatever is on file. The account area is where you check what we hold, and the transaction record is where you follow a payment from the point it left your wallet to the point it reached your account balance. If a name, number or wallet reference is wrong, correct it there, then message support so we can match the change to your history. Anything you want clarified, ask. Questions about how a rule applies to your own case get an answer through the routes listed on this page, and you can ask before you act rather than after. If you believe your account was accessed without you, tell us straight away — the sooner we know, the more of the record we can look at together. You can also close your account when you are done with it. When you ask, we stop active use and handle the stored details as described further down.
Open the account area and go through your transaction list — every bKash, Nagad, Rocket, Upay or bank transfer entry carries a reference you can quote. Comparing that against the wallet app on your phone is the simplest way to spot a payment that did not land as you expected.
If a saved number, name or wallet handle is out of date, update it in the account area first and then tell support what changed. We match the correction against your transaction record so a future transfer is not sent against an old detail.
You do not have to guess how a clause applies to you. Send the question through the contact route published here, include the reference if a payment is involved, and we will answer against this policy rather than from a general script.
When something looks wrong, or when you simply want to stop using the account, say so through our support route. We will explain the next step, what we keep, and how the record is handled under the retention section below.
We keep one thing simple: there is no secret channel. The routes below are the ones you can see on the site itself, and they all lead to the same team that reads policy questions. If your question is about a payment, start with the reference number — it gives us something to match against the record. Before you write, it helps to know which part of the page your question belongs to. Access problems and saved details are handled through your account area. Payment tracing is handled with the transaction record open. Anything about how a clause applies, or about the data we hold, goes to the contact route linked on this page. We do not publish fixed reply hours for this route. What we can say is that a message with a reference, a date and the wallet name attached is the one that gets resolved with the fewest follow-ups. If the answer lies with bKash, Nagad, Rocket, Upay or your bank, we will point you to them instead of holding the ticket here.
Sign in and use the contact link inside your account area when the question is about your profile, your access or a saved detail. It arrives with your account reference attached, which saves a round of back-and-forth before anyone can look at the record.
For policy questions, use the contact route linked in the footer of this page. Include the transaction reference where a bKash, Nagad, Rocket or bank transfer is involved, and say what you expected to happen so the reply can be specific to your case.
If the problem sits with the transfer itself — a pending bKash or Rocket confirmation, for example — the wallet app is the right place to ask. We keep our own record of the entry and can share what we see when you come back to us.
What we hold is deliberately narrow: the details you enter when you open an account, a record of the transactions that pass through it, and the technical details a browser sends when you load a page. We use those to run the account, to trace payments and to keep the site working on the device you are holding. We do not sell them on. Cookies do most of the quiet work — keeping you signed in between pages, remembering a preference, and showing us which parts of the lobby people actually use. You can clear or block them in your browser settings, though some areas of the account will stop behaving properly if you do. Security is a shared job. Keep your login to yourself, use a screen lock on your phone, and sign out on a shared device. If you think someone else has been in your account, tell us immediately. Retention follows the same logic: we keep what we need to answer a query or meet a requirement, then remove it.
Account details you enter, the transaction entries that follow a bKash, Nagad, Rocket, Upay or bank transfer, and basic device and browser data. That is the working set — enough to run your account, trace a payment and keep the site loading on your phone.
Cookies keep you signed in across pages and tell us which parts of the lobby get used. Your browser settings let you block or clear them whenever you like. Do that and some signed-in areas will not work as intended, which is the trade-off.
Your login is yours. Use a lock on your phone, avoid shared devices, and sign out when you finish. If anything looks unusual on the account, contact us through the published route so we can go through the activity together.
We keep your data while the account is open and for as long as we need it to answer a query or meet a requirement, then delete it. You can ask what is held, request a correction, or ask us to close the account.
These are the questions that come up again and again about the policy side of the account — access, records, data and how to reach us. Each answer below sticks to what we can actually see and control. Where a decision belongs to your wallet provider or to the law where you live, we have said so rather than talking around it. If your question is not here, the contact route on this page is the one to use; include a transaction reference when a payment is involved so the reply can be specific.
It applies wherever you use dct88, but whether you may open an account depends on your local law and eligible regions, so check that first. If online play is allowed where you live, the rest of this page describes how we run the account and where you can act.
Yes. Sign in and go through the account area, where your saved details and transaction entries sit together. If you want something explained or corrected, use the contact route on this page and quote the reference for the payment involved.
Keep the reference from your wallet app and open your transaction record. If the entry is missing or looks wrong, send the reference to support through the published route. The provider's own resolution process may also apply, and we will say when a case belongs there.
The wording changes when the way we run the account changes, or when a rule we follow is updated. The current version is always the one on this page, and anything material is reflected in the text itself rather than buried in a separate document you would never open.
Only what a transfer requires — the account or wallet detail needed to move funds and match the entry on both sides. Wallets, studios and any outside pages you reach from our site have their own policies, and those sit alongside ours rather than under them.
Send the request through the contact route published on this page. We stop active use of the account, confirm what is retained for record-keeping, and explain how any pending transaction is handled before the closure is complete.