Casino / Slots
betss operates under a policy framework designed to be clear about what we do, what you can expect from us, and where the limits sit. Access to our platform depends on your local law and eligible regions — we encourage you to read this page before you open or use an account.
Our legal policy sets out the terms under which betss makes its platform available and how we handle the obligations that come with that. Nothing in this document creates a guarantee of access, service continuity or payout outcome — availability is always subject to your local law and the eligible regions we can serve at any given time. Where you use bKash, Nagad or Rocket to fund your account, those transactions are governed by the payment provider's own terms as well as ours. We do not override the rules of those networks; we work alongside them. Our policy applies from the moment you create an account and continues for as long as your account record exists, including after any closure. Changes to this policy are published on this page with a revised date at the top — continued use of the platform after a change is posted constitutes acceptance of the updated terms. If you disagree with any revision, the correct step is to stop using the platform and contact our support channel to request account closure. We aim to write policy language that is readable, not just legally defensive, but where a conflict arises between plain-language summaries and the formal clause text, the clause text takes precedence.
Transaction scope under bKash is set by both betss account terms and the bKash network rules.
Nagad transfers into your wallet are subject to Nagad's own eligibility and limit policies.
Rocket payments follow the DBBL network rules alongside our platform transaction terms.
This policy applies to betss accounts, platform content and transactions processed through our wallet. It does not extend to third-party services, external payment networks or any website we do not own. Understanding the boundary between what we control and what we do not is important before raising a query — if something falls outside our scope, we will tell you which party to contact.
Our policy governs login, account creation, identity checks and suspension. Access itself depends on your local law and eligible region — we do not override local legal restrictions.
Deposits and withdrawals processed through your betss wallet — including those made via bKash, Nagad or Rocket — fall within this policy's scope for dispute and record purposes.
Game content, odds data and promotional notices published on betss pages are covered by this policy. Content accuracy is maintained on our side; third-party data feeds are not within our direct control.
External links, payment network interfaces and game studio environments operate under their own terms. betss is not liable for conditions outside our platform boundary, though we aim to surface those boundaries clearly.
Your rights under this policy are real and actionable. Reviewing what data we hold, correcting errors and raising questions all follow clear paths inside your account or through our support channel. We do not require a formal legal request to look up a transaction record — your account history is visible from the signed-in wallet page, showing each bKash, Nagad or Rocket movement with its date and status. If you spot an error in your account details, the correction path starts in the account settings screen; most text-field updates take effect immediately once submitted. For anything that requires our team to act — such as a policy question, a transaction that does not match your wallet record, or a request to close your account — our support channel is the right route. We respond to policy-related queries through the same contact paths we publish for general account help.
Open your signed-in wallet page to see a full log of deposits and withdrawals, including the payment method and status for each entry.
Account settings allow you to update contact information and linked wallet identifiers. Follow the fields and confirmation steps shown on that screen.
Any question about how a policy clause applies to your account can be sent through our published support routes — chat or email, depending on what is live on the contact page.
If you want to close your account, submit the request through support. We will confirm receipt and follow the closure steps set out in our terms before removing access.
Policy questions, account data requests and transaction disputes all go through the same support routes we publish on our contact page. We keep these paths consistent so you always know where to start. If a query involves a bKash, Nagad or Rocket transaction, have your wallet reference number ready — it speeds up the review process on our side.
Open the chat window from the signed-in account page to reach our support team directly for policy or account queries.
Send your query to the email address published on our contact page. Include your account ID and the policy section your question relates to.
The help centre on our site covers common policy topics and walks through the steps for data requests, account corrections and closure.
We hold only the account data needed to operate your wallet, verify transactions and respond to support queries. Data is not shared with third parties outside what is required to process a bKash, Nagad or Rocket payment or comply with a lawful request. To request a summary of what we hold, contact us through the published support route with your account ID.
Account records are kept for as long as your account is active and for a defined period after closure, in line with standard platform practice. The exact retention period is stated in the full policy clause.
We use session and preference cookies to keep you signed in and remember your device. You can adjust cookie settings in your browser; some features may not work correctly if session cookies are blocked.
Your account is protected by password and, where active, a second verification step. If you believe your credentials have been compromised, update your password immediately and contact support.
To update personal data we hold, start in account settings. For changes our team must make directly, submit a request via email support with your account ID and the specific correction needed.
The questions below cover what we hear most often about policy scope, data rights, account access and how to raise a concern. If your question is not here, our support channel is the right next step.
Access to betss depends on your local law and eligible region. If your location is within the regions we can serve, this policy applies to your account in full. We recommend checking local regulations before opening or using an account.
Yes. Contact us via the email route published on our contact page, include your account ID, and request a data summary. We will confirm receipt and respond through the same channel with the information we hold.
Transaction data for bKash and Nagad payments is stored in your wallet log and retained for the period stated in our policy. It is used only to verify the transaction, resolve disputes and comply with lawful requests — not for marketing.
Most details can be updated directly in account settings — open the screen, edit the relevant field, and follow the confirmation steps shown there. For changes that require our team to act, send an email to our support address with your account ID and the correction needed.
If a revised policy is not acceptable to you, stop using the platform and contact our support channel to request account closure. We will follow the closure process set out in our terms and confirm when it is complete.
Start with our support team via live chat or email — include your Rocket wallet reference and the date of the transaction. For issues that sit within Rocket's own network, we will direct you to the correct contact point at DBBL.