Mobile / Slots
bet35 sets out clear terms so you know exactly where you stand — what this policy covers, how your account data is handled, and what steps are open to you. Access to and use of this platform depends on your local law and the eligible region you are in.
These terms govern the relationship between you and bet35 when you access the platform from Bangladesh or any other eligible region. Whether you reach the lobby through a mobile browser, settle a deposit via bKash or Nagad, or contact support about your account, this policy applies to that interaction. Eligibility to use the platform is determined entirely by the laws and regulations in your jurisdiction — we do not override local law, and nothing in these terms should be read as a claim that access is lawful in every location. We may update sections of this policy when our operational or legal circumstances change. When that happens, the revised version is published here with a clear indication that content has changed. Continuing to use the platform after an update means you have read and accepted the revised terms. If any clause is unclear or you believe a recorded detail about your account is incorrect, the process for raising that with us is described in the rights section below. Transactions processed through bKash, Nagad or Rocket are also subject to the terms of those wallet providers, which sit alongside but do not replace what is written here.
This policy draws a clear line between what we are responsible for and what falls outside our direct control. The four areas below set that boundary so there is no ambiguity when a question arises about your account, your wallet activity or content you encounter on the platform.
Covers how your account is created, authenticated and maintained. Login behaviour, session continuity across mobile and browser, and account-level restrictions all sit within this scope. Access remains subject to your local law and the eligible region you declare at registration.
Covers deposits and withdrawals processed through the payment methods configured on this platform, including bKash and Nagad. The mechanics of each wallet — fees, processing queues, wallet-side limits — are governed by those providers and fall outside what we can override or guarantee.
Covers games, tables and markets published directly in the bet35 lobby. Game availability, category display and any notices shown in your signed-in account area are within scope. Content accuracy for listed categories — slots, live casino, sportsbook — is our responsibility to maintain.
Links to external services, game studio platforms outside our lobby, or wallet provider interfaces are not covered by this policy. When you leave the bet35 environment, the policy of that third party applies. We do not assume liability for third-party content, conduct or data practices.
You have a set of concrete actions available to you at any point while your account is active. These are not conditional on a special request — they are part of how we operate. To review the transaction history linked to your account, open the account section in your mobile browser or desktop session and navigate to the records tab; all logged activity is shown there. If a detail on your account — your registered mobile number, the wallet reference tied to your bKash or Nagad account, or a personal detail — is recorded incorrectly, you can submit a correction request directly through the support channel. To raise a question about how your data is held or how this policy applies to a specific situation, the contact routes in the support section below are the right starting point. We treat correction and query requests as distinct from general account issues, so route them clearly when you write in. Requests for account closure sit within these rights too — the support team can walk you through the steps shown in the platform at the time you ask.
Open the account area from your mobile browser and select the transaction or activity log. All recorded sessions and wallet movements linked to your account are visible there without a separate request.
If your registered mobile number, linked bKash or Nagad reference, or personal details contain an error, submit a correction request through the live chat or email route. Include the incorrect detail and the correct version you want recorded.
If a clause in this policy is unclear or you want to understand how it applies to your specific situation, contact us through the published routes below. We handle policy queries separately from general account support for a faster resolution path.
You may request closure of your account at any time. Contact support with a clear closure request. The team will confirm the steps, outstanding balance position and any final verification required before closing the account.
When a question is specifically about this policy — your rights, a data detail, a scope boundary or a correction — use the routes below rather than a general enquiry path. Routing your query correctly means it reaches the right team the first time.
Open the live chat icon from any page inside your signed-in session. Describe the policy section your question relates to so the agent can route it correctly without a transfer.
Send your policy query to the support email address published in the contact section of this site. Include your registered mobile number and the specific clause or account detail you are asking about.
The help section inside your account lists common policy questions and the steps for correction requests. Check there first — many queries about transaction records and account details are answered without needing to contact support directly.
We handle the data connected to your account — login activity, transaction references, device session data — according to the terms stated here. The specifics of what is stored, how long it is kept, and who can access it are not abstract commitments; they are operational decisions you can ask about directly.
Account data — including the mobile number you registered with and the wallet references linked to bKash or Nagad — is held for the purposes of operating your account. We do not share this data with parties outside the scope of running the platform and processing your transactions.
We use session cookies to keep you signed in across pages on mobile and desktop. Functional cookies support lobby navigation and account continuity. You can review and adjust cookie preferences through your browser settings at any time — this does not require a support request.
Your account is secured through the credentials you set at registration. If you believe your account has been accessed without your knowledge, contact support immediately through live chat. Do not share your login credentials or wallet PIN with anyone, including anyone claiming to be from our team.
We retain account records for as long as your account is active and for the period required after closure by applicable rules in your eligible region. To request detail on what is held after closure, or to ask about deletion where local rules permit it, use the email support route.
The questions below are the ones we see most often from members who want to understand their rights, check what is covered and know how to take action. Each answer points to the specific step or route relevant to that question.
Access to the platform and the rights described in this policy depend on your local law and whether Bangladesh is an eligible region for your account type. We do not determine legality on your behalf — check your local regulations before using the platform.
Open the account section from your mobile browser or desktop session and navigate to the activity or transaction records area. Login history, wallet movements linked to bKash or Nagad, and account changes are all logged there. No separate data request is needed to view this.
Yes. If your registered mobile number, linked wallet reference, or any personal detail is recorded incorrectly, submit a correction request through live chat or email support. Include the incorrect value and the correct version you want recorded. The support team handles these as a distinct request type.
Records are retained for the period required by applicable rules in your eligible region after account closure. To find out exactly what is held and for how long, or to ask about deletion where local law permits it, send a request to the email support route published in the contact section.
Transactions you initiate through bKash or Nagad are recorded within your bet35 account and are within scope for query and correction purposes. However, the wallet-side mechanics — fees, processing queues and wallet limits — are governed by those providers and sit outside what this policy covers.
When we update any section of this policy, the revised version is published on this page with a clear indication that content has changed. Continuing to use the platform after a published update means you have accepted the revised terms. We do not send individual notifications for every policy revision.