Mobile / Slots
cd33 pdb publishes these legal terms so you know exactly where you stand — what applies to your account, what your choices are, and how to reach us when something needs clarifying. Access to our platform depends on your local law and the eligible regions we serve.
Our legal terms set out the conditions under which your account operates on cd33 pdb. They are not a blanket permission slip — they reflect the rules that apply based on where you are and what the applicable law allows. If you are accessing from Bangladesh, whether a transaction or session is permitted depends on your local regulations and the eligible regions we can serve at any given time. We do not make legal promises we cannot stand behind, and we will not claim certainty where none exists. When you use a local payment method — bKash, Nagad, or Rocket — the transaction is governed both by our own policy and by the terms of that payment provider. We hold no authority over third-party payment rails beyond what they expose to us. What we can do is ensure the account record on our side is accurate, accessible to you, and correctable if something appears wrong. Any dispute over a transaction shown in your account wallet should first be raised through our support route before escalating to the payment provider. This two-step approach resolves most issues faster and keeps a clear record on both sides.
bKash transactions recorded in your wallet are subject to both our policy and bKash's own terms.
Nagad transfers follow the same dual-policy rule — our account record plus Nagad's provider terms.
Rocket payment entries visible in your account are the reference point for any query you raise with us.
This policy applies to the cd33 pdb platform as accessed through your account. It does not extend to third-party services you reach from our pages, and it does not override the laws of the jurisdiction you are in. The four areas below define the boundary clearly.
Covered. Everything related to opening, verifying, suspending or closing your account on cd33 pdb falls within this policy. Your access rights and the steps to exercise them are described here.
Partially covered. Transactions made through bKash, Nagad, or Rocket are recorded in your account wallet and covered by our policy. The payment provider's own terms run alongside ours and are not replaced by them.
Covered. Game availability, lobby content, and promotional notices published on the site fall within our scope. We can correct or withdraw content at any time, and the version live at the time of your session is the binding one.
Not covered. Links, embedded tools, or services operated by studios or external providers are outside our policy scope. Bigtime Gaming, Microgaming, JDB, and Joker each maintain their own content and terms for the games they supply.
You have several practical options under this policy that do not require legal action or a formal complaint. Start with your account — the transaction history and session records visible there are the primary source of truth for any question you raise. If a record looks wrong, you can request a correction by contacting support with the specific entry reference and the detail you want reviewed. For account details like contact information or payment method links, the settings section of your account lets you update most fields directly. Where a change requires manual review on our side — for example, a name correction that affects identity verification — support handles those requests individually. If you have a question about how a specific policy clause applies to your situation, raise it through the live chat route or the support form, and we will give you a clear written response. We keep a record of all policy queries so that if the same question comes back, the answer is consistent.
Open your account transaction history to see all wallet entries, including bKash, Nagad, and Rocket activity. This is the starting point for any dispute or query.
Most contact details and payment method links can be updated in the account settings section. Name corrections that affect verification are handled by support on request.
Use the support form or live chat to ask about a specific clause. We reply in writing so there is a clear record of the answer given.
If a policy matter is unresolved after using the standard support route, you can escalate via the formal written request path described in the support section below.
Use the routes below for any legal or policy question. We do not publish contact details that are not actively monitored, so each path below connects to a real response queue.
Available from the support icon inside your signed-in account. Use this for immediate policy questions, transaction record queries, and account correction requests. The conversation is logged and accessible to you.
Accessible from the Help section. Submit a written query with your account reference and the specific policy clause or record in question. Written responses from this route serve as the formal policy reply.
The Help section within your account lists published policy documents, correction steps, and escalation paths. Check there first — many common policy questions have a documented answer already in place.
We manage policy matters through four operational areas: data handling, cookie use, account security, and retention. Each is described below so you know what we do and where to go if something needs to change.
Account data — including wallet entries for bKash, Nagad, and Rocket — is held on our platform and used only for account operation and policy compliance. We do not share it with third parties except where a payment provider requires it to process your transaction.
We use session cookies to keep your account logged in and to maintain lobby state between pages. No behavioural advertising cookies are used. You can manage cookie preferences through the settings shown in your browser.
Your account credentials are your responsibility to keep private. If you suspect unauthorised access, use the account lock option in settings or contact support immediately. We do not ask for your password through any support channel.
We retain account records for the period required by applicable policy. If you want to know what we hold or request a change, raise it through the support form. Policy terms may be updated; the version shown in your account at the time of your session is the one that applies.
These are the policy questions we hear most often. Each answer reflects what is actually published and how our support routes work in practice.
Access and eligibility depend on your local law and the eligible regions we serve at the time. We do not override local regulation. If you are unsure whether access is permitted in your area, check the applicable rules in your jurisdiction before opening an account.
Your transaction history, session records, and account details are visible in the signed-in account area. For a full data summary or a question about what else we hold, submit a request through the support form with your account reference included.
If a bKash, Nagad, or Rocket entry in your wallet looks incorrect, contact support via live chat or the support form and provide the transaction reference. We review the account-side record and, where an error is confirmed on our end, correct it in writing.
We retain account records for the period required under applicable policy after closure. You can ask what is retained and for how long by raising a written request through the support form. We respond with a clear written answer specific to your account.
Yes. Use the support form or live chat to reference the specific clause you want clarified. We give a written response so the answer is on record. If the clause has changed since your last session, we note that in the reply.
Raise it with us first through the live chat or support form, referencing the exact wallet entry. We check the account-side record and respond in writing. If the issue originates with the payment provider rather than our platform, we will indicate that clearly so you can follow up with Nagad or Rocket directly.