App / Casino
yessbet publishes these legal terms so you know exactly what governs your account, your transactions through bKash or Rocket, and your use of this site. Access and eligibility depend on your local law and the eligible regions we support.
This policy governs all account activity on yessbet, including how we collect and handle information tied to your account, your wallet activity, and your session history. Whether you access via bKash, Rocket or any supported method, the same policy terms apply to your account records. We do not sell or transfer your personal account data to third parties for their own marketing purposes. Data we hold is limited to what is necessary to operate your account, verify transactions and respond to your support requests. Where local law in Bangladesh requires additional steps or restricts certain features, those restrictions take effect regardless of what is otherwise available on the site. Our policy is reviewed periodically; when we update it, the revised version is published here with the date of change noted at the top. If you continue using your account after a policy update is published, that constitutes your acknowledgement of the revised terms. For any question about a specific policy clause — including those touching your bKash deposit records or Rocket transaction history — you can reach our support team through the contact routes listed on this page.
bKash transaction records linked to your account are held under this policy.
Rocket payment history is stored against your account and subject to the same retention rules.
Your account wallet balance and adjustment logs are covered by this policy in full.
Not every service connected to your yessbet experience is directly governed by this single policy document. Some services operate under separate terms or are managed by third parties. The table below clarifies what this policy covers directly and what falls outside it, so you are not left guessing which terms apply to which part of your account.
Your login credentials, session data and account-level settings are fully within scope. If you believe your account access has been compromised, the steps to report and resolve that are described under our support routes.
Deposits and withdrawals processed through bKash or Rocket are covered in terms of the records we hold. The payment network's own terms also apply to the transfer itself; those sit outside our direct policy scope.
Game content, lobby displays, promotional notices and category pages on yessbet are within scope. We are responsible for what we publish here; third-party game studios supply content under their own separate agreements.
External links, third-party identity verification services and payment network operations fall outside this policy. We do not control those services and cannot be held responsible for their separate terms or data practices.
This policy is not just a document we publish for our own purposes — it creates practical actions you can take at any time. You have the right to ask us what account data we hold, to request a correction if something is recorded incorrectly, and to raise a formal question if you disagree with how a policy clause has been applied to your account. To review your own transaction records, open the account history section once you are signed in; your deposit and withdrawal entries — including bKash and Rocket transactions — are listed there with timestamps. If you notice a discrepancy, do not wait: contact our support team through the routes listed on this page and include the transaction reference shown in your account history. Corrections to your registered account details, such as your contact number or linked wallet, must be requested through support rather than changed unilaterally, because we need to verify your identity before updating sensitive fields. Eligibility for certain account features depends on your region and local law in Bangladesh.
Sign in and open your account history to see all transaction entries, including bKash and Rocket deposits. Timestamps and reference numbers are shown for each entry.
Contact support to request a correction to your registered information. Identity verification is required before we update any sensitive field on your account.
If you disagree with how a term has been applied, you can submit a written question through our support contact. We will respond with the relevant policy clause and the reasoning behind any decision.
You may ask us for a summary of the personal data we hold against your account. Make this request through the support route and include your registered account details so we can verify the request.
If you have a question about a specific clause, a data request, or a concern about how your account records are handled, the routes below are the right place to start. We respond to policy-related queries through the same support channels used for account help — there is no separate legal department queue you need to find.
Open the chat widget from any page while signed in. State that your question relates to the legal policy or your account data, and the agent will route it appropriately.
Send your policy question or data request to the support email address listed in your account settings. Include your account username and the policy clause or transaction reference your query concerns.
The help section inside your signed-in account contains links to published policy documents and a form for submitting a formal written request about your data or account records.
Understanding what we actually do with your information is more useful than reading abstract reassurances. Here is a direct account of the four areas that matter most: how data is stored, what cookies do on this site, how account security works at the session level, and how long we keep records before they are deleted or anonymised.
Account data — including your wallet activity, login history and transaction records tied to bKash or Rocket — is stored on secured servers. We do not share it with third parties for marketing. Access is restricted to authorised operations staff.
We use session cookies to keep you signed in and functional cookies to remember your lobby preferences. Analytics cookies help us understand how the site performs. You can adjust cookie preferences through your browser settings at any time.
Sessions are tied to your device and network fingerprint. If we detect an unusual login pattern, your session may be paused and you will be asked to re-verify. Do not share your login credentials with anyone.
We retain your account records for as long as your account is active and for the period required by applicable rules after closure. After that period, records are deleted or anonymised. Submit a deletion request through support once your account is closed.
These are the questions we hear most often about how this policy works in practice. If your question is not here, reach out through the support routes listed above.
Yes. Any transaction record linked to your account — whether processed via bKash or Rocket — is covered by this policy in terms of how we store and use that data. The payment network's own terms also apply to the transfer itself on their side.
Submit a data request through the support email or account help section. Include your account username and the nature of your request. We will compile a summary of the data held against your account and respond through the same contact route.
Access and eligibility depend on your local law and the eligible regions we support. We do not make legal determinations on your behalf. Check the applicable laws in your area before creating or using an account on this site.
We retain records for the period required under applicable rules after account closure. After that period, your data is deleted or anonymised. You can request information about the specific retention period through the support contact route.
When we update this policy, the revised version is published here with the effective date noted at the top of the page. Continued use of your account after an update is published constitutes acknowledgement of the revised terms.
Raise a formal written query through our support email, referencing the specific clause you believe was applied incorrectly. Include your account details and any transaction reference. We will respond with the relevant policy reasoning and the steps available to you.