Before you use any part of ddb33 — your account wallet, session controls, or payment routes through Nagad and Upay — these terms set out the rules that apply. Access to this platform depends on your local law and the eligible regions we serve; read this page before making any account decisions.
Nagad & Upay payment records verified
Session controls visible at account creation
Policy applies to all account activity
Eligibility depends on local law and region
POLICY POSTURE
How These Terms Apply to Your Account
These terms form the agreement between you and ddb33 the moment you open an account or use any platform feature — including deposits made via Nagad or Upay, session activity, wallet transfers and any support request you submit. They are not a summary; they are the operative document. Where local law in Bangladesh restricts or conditions certain activities, those restrictions apply regardless of what this page says. Your continued use of any account feature confirms your acceptance of the current version of these terms. We update this document when policy changes occur; the version shown here is the one in effect. You are responsible for reading it before each session if you want to stay current. If any part of these terms conflicts with a jurisdiction-specific rule that applies to you, the stricter rule applies. We do not waive any term by failing to enforce it on a particular occasion. Questions about specific clauses should be directed to our support channel before you act on an interpretation you are uncertain about. Context chips below reflect the payment rails active under this policy.
Nagad
Deposits and withdrawals via Nagad are governed by these terms alongside Nagad's own service conditions.
Upay
Upay transactions processed through your account wallet fall under these terms at the point of confirmation.
bKash
Where bKash is used for account funding, the same policy obligations apply as for any other supported payment rail.
Rocket
Rocket transfers are subject to these terms; eligibility depends on your region and the payment method's own conditions.
POLICY COVERAGE
What Falls Inside and Outside This Policy
Not every action you take on ddb33 is governed by the same rule set. Some areas fall squarely within this policy; others are handled separately or by a third party. The comparison below clarifies what this document covers, so you are not left guessing when something goes outside its scope.
Account Access
Opening, suspending or closing your account, changing login credentials and managing session controls all fall within this policy. We handle those steps and the rules here apply directly to each one.
Transactions
Wallet deposits and withdrawals — including those made via Nagad and Upay — are covered. The specific amounts, verification steps and processing instructions shown in your account at the time of the transaction are part of these terms.
Site Content
Game content from studios such as PlayStar, Pragmatic Play, Joker and Bigtime Gaming is made available under this policy, but each studio retains its own content rights. We present the titles; we do not own the underlying game software.
Third-Party Services
Payment processors, mobile wallet operators and any external link you follow from ddb33 operate under their own terms. We are not responsible for those services once you leave our platform or once a payment instruction leaves our system.
YOUR ACCOUNT RIGHTS
Practical Steps Available to You Under This Policy
These terms are not just obligations — they also define what you can ask of us and how to do it. If you want to review your transaction history, the account dashboard shows a record of every Nagad, Upay or other wallet movement linked to your profile. That record is your primary reference for any payment query. If any account detail — your registered contact, your wallet reference, or your stated preferences — is incorrect, you can request a correction through the support channel. We will confirm receipt and tell you what verification we need before making the change. Where you believe a term has been applied incorrectly to your account, raise it directly; we review each case against the version of this policy that was in effect at the time. You also have the right to ask what data we hold on your account, and we will respond according to the applicable rules for your region.
Review Your Records
Your transaction log in the account dashboard shows every confirmed deposit and withdrawal. Check it first before contacting support — the details you need are usually already there.
Correct Account Details
If your registered mobile number, wallet reference or contact detail is wrong, submit a correction request through support with the account identifier you used at registration.
Raise a Policy Question
If you believe a rule has been applied in a way that does not match what is written here, contact us with the specific clause and the transaction reference. We will review it against the active policy version.
Request Data Information
You may ask what personal information we hold for your account. We respond according to the rules applicable to your region and the eligible jurisdiction governing your account.
CONTACT ROUTES
How to Reach Us About This Policy
If you have a question about these terms, the account support team is the right starting point. We handle policy queries, account correction requests and transaction disputes through the channels below. Describe the specific clause or account action in question and include your account reference so we can locate your record without delay.
Live Chat
Open the chat window from your account dashboard for real-time policy queries. Suitable for straightforward questions about account rules or transaction records.
Email Support
For detailed correction requests or disputes, email is the appropriate route. Include your account reference, the relevant term and any transaction ID so we can review the full record.
Account Help Section
The Help section inside your account lists common policy questions with direct answers. Check it first — many term-specific queries about Nagad and Upay payment steps are answered there.
HOW WE HANDLE POLICY
Inside ddb33: Policy Practice and Account Security
Operational consistency is how we demonstrate that these terms mean something in practice. Account security measures, data handling and the way we process correction requests all follow the procedures described here — not a separate internal standard.
Data Handling
Account data — including your wallet references for Nagad and Upay — is held only for as long as your account is active or as required by the rules of your eligible region. You can ask what we hold at any point through the support channel.
Cookie and Session Policy
We use session data to keep your account active during a single visit. Cookie use is explained in the separate privacy notice linked from your account settings. These terms apply to the account session itself, not to cookie preferences.
Account Security Obligations
You are responsible for keeping your login credentials private. If you believe your account has been accessed without your permission, contact support immediately using the email route. We will place a temporary hold on the account while we investigate.
Policy Update and Retention
When these terms change, the updated version appears on this page. We retain prior versions for internal reference. If you want a copy of the version that was in effect on a specific date, submit that request through email support with the date and your account reference.
POLICY QUESTIONS
Common Questions About These Terms
The questions below are the ones we see most often from new account holders. If your question is not covered here, reach us through live chat or email with your account reference.
Do these terms apply if I use Nagad or Upay to fund my account?
Yes. Any transaction processed through your account wallet — including Nagad and Upay payments — falls under these terms at the point the transaction is confirmed. The payment processor also applies its own service conditions alongside ours.
Can I use ddb33 if online betting is restricted in my area?
Access depends entirely on your local law and the eligible regions we serve. We do not override local restrictions. You are responsible for confirming that your use of the platform is permitted under the law that applies to you before opening an account.
How do I know which version of the terms applies to my account?
The version shown on this page is the one currently in effect. If you need to know which version was active on a specific date — for example, to reference it in a dispute — submit a request via email support with the date and your account reference.
What should I do if I think a rule has been applied incorrectly to my account?
Contact us through live chat or email and quote the specific clause you believe was misapplied, along with your account reference and the relevant transaction ID. We review each case against the policy version that was in effect at the time of the action in question.
How can I correct a mistake in my registered account details?
Submit a correction request through the email support channel. Include the detail you want changed, your account identifier and any verification document we may need. We will confirm what is required before updating your record.
What information does ddb33 hold on my account, and can I ask to see it?
We hold the registration details, wallet references and transaction history linked to your account. You can request a summary at any time through email support. Our response follows the rules applicable to your eligible region and local law.