Mobile / Sports
These terms set out how your 35db1 account works, what we expect from you, and what you can expect from us. Access to the platform and its services depends on your local law and eligible regions — read these terms before you use the account.
By accessing any part of 35db1 — including the lobby, wallet section, or transaction history — you confirm that you have read and accepted these terms. They apply to all account activity: deposits made via Nagad or Rocket, withdrawals processed through Bank Transfer, game rounds across the casino lobby, and any communication you send to our support team. We may update these terms when required. When that happens, the revised version takes effect from the date it is published on this page. Continuing to use the account after an update means you accept the changes. If you do not agree with a revision, you should stop using the account and contact support to discuss your options. These terms do not override your rights under local law. Eligibility to hold a 35db1 account and use the platform depends entirely on your local law and the eligible regions we operate in. We do not make representations about legality in any jurisdiction — that is your responsibility to confirm before opening or continuing to use an account.
Not every part of your experience falls under the same rule. Understanding what these terms do and do not cover helps you raise the right question with the right team. The four areas below define the boundary clearly.
These terms govern how your account is created, verified, suspended or closed. Login behaviour, session continuity across devices, and password resets all fall inside this scope. Actions taken while signed in are subject to these terms in full.
All deposits and withdrawals processed through Nagad, Rocket or Bank Transfer are covered. Dispute resolution for a transaction follows the process described in your account history section — we do not adjudicate claims made outside that record.
Game descriptions, odds displays, promotional notices and lobby copy are published by us and fall under these terms. We may update or remove content at any time. Content accuracy is maintained on a best-effort basis and does not constitute a contractual offer.
Studio content from Joker, Microgaming, Habanero or PlayStar is delivered under each provider's own service agreement. We carry their titles in the lobby but are not responsible for terms specific to their software, and those terms sit outside this policy.
These terms are not a one-way document. You have specific, practical actions you can take at any point. Your transaction history is visible inside the signed-in account area — every Nagad deposit, Rocket transfer or Bank Transfer withdrawal is logged there with a reference number. If a record looks incorrect, the first step is to raise it directly through the account support route rather than waiting. Personal details on your account — name, contact number, preferred payment method — can be reviewed and, where permitted, corrected by following the fields shown in your account settings screen. You also have the right to ask us a question about any clause in these terms. We will respond through the support channel you used to raise it. If you want to close your account, the request must come through an authenticated support contact, not an unauthenticated message, so we can confirm your identity before acting.
Open the transaction history tab in your signed-in account to see a full log of deposits and withdrawals, including Nagad and Rocket entries. Each entry carries a reference you can quote in a dispute.
Account name, contact number and payment method preferences are editable in the settings section shown after login. Follow the fields and verification steps displayed there — do not send corrections over chat without completing those steps first.
Any question about a specific clause can be sent to support. Quote the section you are asking about. We aim to respond with a clear, specific answer — not a copy of the whole document redirected back to you.
Close the account by contacting support while authenticated. We confirm your identity via the signed-in session before processing the request. Outstanding balances are handled according to the payment method on file at the time.
If a clause is unclear, a transaction needs reviewing, or you want to act on a right described in this document, use the contact routes published on the site. We do not accept terms-related requests through unauthenticated channels — always raise them while signed in where possible.
The live chat widget is available in the signed-in account area. Use it to raise a specific terms question or flag a transaction you want reviewed. Identify your account and the clause or reference you are asking about.
Send a written request to the support email address published in the contact section of the site. Include your account reference, the relevant terms section and the outcome you are requesting. Email creates a written record for both sides.
The help page inside your account area covers common terms questions with step-by-step guidance. Check there first — many questions about payment scope, account closure or record correction are answered without needing a direct contact.
We apply these terms consistently across every account. Here is how the key operational areas work in practice — from how long we retain data to how you request a change.
Account data, including transaction records for Nagad, Rocket and Bank Transfer activity, is retained for as long as your account is active and for a period after closure as required by applicable rules. The signed-in history tab reflects the current retained record.
We use session cookies to maintain your login state across a browser session on mobile or desktop. Preference cookies remember your last lobby position. You can clear these through your browser settings, but doing so will end your current session and reset saved preferences.
You are responsible for keeping your login credentials private. Any activity logged under your account is treated as authorised by you. If you believe your account has been accessed without your permission, contact support immediately through the authenticated live chat route.
Changes to your registered details — including the payment method linked to your wallet — must be requested while authenticated. We verify the request against your account record before applying it. Instructions for each type of change are shown in the account settings screen.
These are the questions we see most often about the terms governing your account. If yours is not listed here, use the live chat or email route described in the support section above.
Yes. All transactions processed through Nagad, Rocket or Bank Transfer are covered by these terms. The specific steps for each payment method — limits, verification fields and transaction records — are shown in the account wallet section after login.
The updated version is published on this page with the revision date. Continuing to use your account after that date means you accept the changes. If you disagree with an update, stop using the account and contact support to discuss your options before the change takes effect.
Access to 35db1 depends on your local law and the eligible regions we operate in. We do not confirm legality in any specific jurisdiction. It is your responsibility to check whether access is permitted in your location before using the account.
Open the transaction history tab in your signed-in account and locate the entry using its reference number. Raise the dispute through live chat or email support, quoting that reference. We review the record against the transaction log and respond through the same support channel.
These studios supply game content to the lobby. Their software operates under their own service agreements. Our terms cover your account use and transactions on the platform; terms specific to studio software sit outside this policy and are not something we can vary.
Contact support while authenticated — through live chat or email while signed in. We confirm your identity using the active session before processing the request. Any remaining wallet balance is handled through the payment method on file at the time of closure.