This page sets out the terms under which ddb33 operates for visitors in Bangladesh — covering account access, session controls and how we handle your information. Access to our platform depends on your local law and the eligible regions we serve, so read this before you take any account step.
Jurisdiction-dependent access
Session control options at account level
Nagad and Upay payment records visible in your wallet
Policy contact route available after login
POLICY SCOPE AND POSTURE
How This Policy Applies to Your Account
ddb33 operates under a framework that places the responsibility for local compliance on you as the account holder. Whether access is permitted in your area depends entirely on the laws of your jurisdiction. We do not represent that using this platform is lawful in every location — you must satisfy yourself on that point before proceeding. Where access is eligible, our policy governs how your account data is held, how transaction records are stored and how you raise a dispute. Payment activity conducted through Nagad or Upay is logged to your account wallet. Those records are accessible from your account dashboard after login and form the primary evidence trail if any transaction question arises. We retain this data for the period required under our operating framework, after which it is removed unless a pending query requires us to hold it longer. Our policy does not extend to third-party services linked from our platform — including external payment processors, affiliate sites or game content pages hosted outside our domain. If a dispute arises involving a third-party service, you will need to raise it directly with that provider. For any policy question specific to your account, the contact route is set out in the support section below.
Nagad
Nagad transaction records are stored in your account wallet and viewable after login.
Upay
Upay deposit entries appear in your payment history under account settings.
Account Dashboard
Your full payment record is accessible from the dashboard — no separate request needed for recent entries.
Data Retention
Records are held for the period required by our operating framework, then removed unless a query is open.
WHAT THIS COVERS
Where This Policy Applies and What It Does Not
Not every part of your experience falls under the same policy rules. Understanding what is inside and outside our scope helps you raise the right question with the right party. Account access, your transaction log and how we store your data are all governed by this policy. Third-party integrations are not.
Account Access
Access to your ddb33 account — including login, session controls and account closure requests — falls fully within this policy. Eligibility to hold an account depends on your jurisdiction and the eligible regions we serve.
Transactions
Deposits and withdrawals processed through payment rails we support are covered. The record of each transaction is held in your account wallet. Disputes about those entries are handled through our policy contact route.
Site Content
Game content displayed on our platform — including titles from PlayStar, Pragmatic Play, Joker and Bigtime Gaming — is covered by our content policy. We present what is available in the lobby; we do not control individual provider systems.
Third-Party Services
External links, affiliate pages and payment processors that operate outside our domain are not covered by this policy. If an issue arises with a third-party service, contact that provider directly. We cannot intervene in their processes.
YOUR ACCOUNT RIGHTS
Actions You Can Take Under This Policy
You have specific, practical routes available to you under this policy — not just a general right to complain. Start with your account dashboard: your payment history, session log and account details are all visible there after login. If something looks wrong, you can raise a correction request by contacting us through the support route listed on this page. We handle correction requests in the order they are received and will confirm receipt in writing. If you want to review what data we hold against your account, submit a written request using the contact details in the support section. We aim to respond to data review requests within a reasonable period; we do not commit to a specific number of days because some requests require additional verification steps before we can respond fully. Account closure is also a right you can exercise at any time — the process begins with a written request to our support team, after which your account is placed in a review queue before closure is confirmed.
Review Your Records
Log in and open your account dashboard to see your full payment and session history. Nagad and Upay entries appear there directly — no separate request is needed for recent transactions.
Correct Account Details
If your name, contact information or payment details need updating, submit a correction request through our support channel. We will confirm the change in writing once it has been applied.
Raise a Policy Question
For questions about how your data is stored or how a specific policy rule applies to your account, contact us in writing. We respond to policy questions separately from general account support queries.
Request Account Closure
You may close your account at any time by sending a written request. Your account enters a review queue and closure is confirmed once any open transaction queries are resolved.
POLICY CONTACT ROUTES
How to Reach Us About This Policy
Three contact paths are available for policy-related questions. Choose the one that matches your query type — account data requests should go to the written channel, not live chat, so there is a clear record on both sides.
Written Policy Request
Send policy and data-related questions in writing through the contact form in your account settings. Written requests create a record that both sides can reference if follow-up is needed.
Live Account Support
For account-level questions — login issues, session control access, or transaction queries — use the live support channel available after you log in. This route handles operational questions, not formal data requests.
Account Settings Path
Many policy actions — reviewing payment records, checking session history, updating contact details — can be completed directly inside your account without contacting support. Start there before raising a formal query.
HOW WE HANDLE THIS
Our Approach to Data, Cookies and Account Security
We handle your account data carefully and with defined retention limits. Here is how the main areas of policy practice work on ddb33.
Data Handling
Your information — including payment records from Nagad and Upay — is stored in our system only for as long as required. Once the retention period ends and no query is open, the data is removed. You can request a summary of what we hold by contacting us in writing.
Cookies and Session Tracking
We use cookies to keep your session active and to understand how the platform is used. You can adjust cookie preferences through your browser settings. Turning off session cookies may affect how your account behaves during login.
Account Security
Access to your account is protected by credentials you set at registration. We do not store your payment wallet PIN or any Nagad or Upay authentication detail. If you suspect unauthorised access, contact our support team immediately through the live channel.
Requesting Changes
To update the personal details held against your account, or to request that certain data be corrected, use the written contact route. We confirm all changes in writing once applied, so you have a record of what was updated and when.
POLICY QUESTIONS ANSWERED
Common Questions About This Policy
The questions below reflect what account holders in Bangladesh typically ask when they read through our legal policy. If yours is not here, use the written contact route.
Does Bangladesh law allow me to use ddb33?
Access depends entirely on your local law and the eligible regions we serve. We do not make a legal determination on your behalf. You should satisfy yourself that using this platform is permitted under the laws of your jurisdiction before creating or continuing to use an account.
Where can I see my Nagad and Upay payment records?
Your full payment history — including Nagad and Upay entries — is visible in your account dashboard after login. No separate request is needed for recent transactions. If an entry appears incorrect, raise a correction request through the written contact route.
How do I request a copy of the data ddb33 holds about me?
Submit a written request through the contact form in your account settings. We handle data review requests separately from general support queries. We aim to respond within a reasonable period, though some requests require additional verification before we can reply fully.
Can I correct my account details if something is wrong?
Yes. Contact us through the written policy channel with the details you want corrected. We will review the request and confirm the change in writing once it has been applied. For name and identity changes, additional verification steps may be required.
What happens to my data if I close my account?
After account closure, we retain your data for the period required under our operating framework. Once that period ends and no query is open, your records are removed. You may request a summary of retained data at any point during that period using the written contact route.
Are third-party payment services covered by this policy?
No. External payment processors — including any Nagad or Upay infrastructure that operates outside our domain — are not covered by this policy. If an issue arises with a third-party service, contact that provider directly. We can only address entries that appear inside your ddb33 account wallet.
App / Live