Casino / App
ob 55 operates under a defined set of legal terms that govern how your account, transactions, and access to the platform work. Whether you connect via bKash, Rocket, or a mobile browser, these terms set out your rights and our responsibilities — availability depends on your local law and eligible regions.
Our legal terms cover the full range of activity on the platform — from the moment you open an account to how we handle your transaction records and support requests. These terms are written to be read on a phone, so the structure is direct: each clause addresses one real situation rather than a broad abstract principle. Access to ob 55 depends on whether your local law and the eligible regions we serve include your area. We do not make claims about availability outside what we can verify. If your region is supported, the terms apply in full from your first login. Transactions processed through bKash and Rocket are recorded in your account wallet and are subject to the transaction terms set out in the payment section of these policies. You can check individual transaction records from the wallet history screen at any time. For account security, we apply session management so your login state is preserved across your browser or device without requiring you to re-enter credentials on each return visit. The security section of these terms explains how session data is stored and for how long it is retained. Any questions about specific clauses can be sent through the support route listed in our contact section.
Understanding what falls within these legal terms helps you know where to look when a question comes up. Four areas are defined clearly so there is no ambiguity about what we are responsible for and what sits with a third party.
These terms apply fully to your ob 55 account: login credentials, session continuity, balance records, and the account wallet where bKash and Rocket transactions are reflected. Any access dispute starts here.
Deposits and withdrawals processed through bKash or Rocket fall under our transaction terms. The record shown in your wallet history is the binding reference. Third-party processing timelines are outside our control.
Game content from studios available in the lobby, sportsbook markets, and live tables are covered by the content terms. RTP and game mechanics are disclosed only where the relevant studio or provider publishes that data.
Payment processors, mobile network operators, and any external service you use to fund your account operate under their own terms. ob 55 is not liable for actions or delays originating on their side of a transaction.
You hold specific rights over your account data and how it is used. These are not passive entitlements — each one has a practical path you can follow from your account settings or through our support route. To review your transaction records, open the wallet history screen on your account page. Every bKash and Rocket transaction is listed there with a timestamp and reference number. If a record looks incorrect, the correction process starts with a support request that references that transaction ID. Your account profile details — name, contact number, and registered payment method — can be updated from the account settings screen. Some changes, such as a registered mobile number linked to bKash, may require identity verification before the update is confirmed. The on-screen instructions walk you through each required field. If you have a question about how your data is handled or want to request a change that is not available in self-service settings, our support channel is the correct path. Response handling follows the process described in the contact section of these terms.
Open the wallet history screen to see every deposit, withdrawal, and transaction tied to your bKash or Rocket account. Each entry carries a reference ID you can use in a support request if something needs checking.
Account profile fields are editable from settings. Changes to a payment-linked mobile number require verification — follow the steps shown on screen rather than contacting support first.
Policy questions that go beyond self-service are handled through our published support route. Include your account reference and the specific clause or transaction you are asking about so the team can respond accurately.
For anything that affects your account balance or access rights, use the support contact path listed on this page. Describe the issue and attach any relevant transaction reference for a faster resolution.
These are the contact routes published on ob 55 for policy and account queries. Use the route that matches your question — general account questions, transaction disputes, and data requests each have a clear path.
Use the support form available in your account dashboard for questions about these terms, your data, or account access. Include your account reference number to help the team locate your record quickly.
For bKash or Rocket transaction disputes, contact support through the in-app help section and include the transaction reference ID shown in your wallet history. This is the fastest route for payment-related questions.
To request a copy of your account data or to submit a correction request, use the dedicated data request option in account settings, or raise it through the support form if the self-service option does not cover your case.
Account security and data handling are built into the platform at the session level, not bolted on as an afterthought. Here is what that looks like in practice across the four areas that matter most to your account.
Your account data — login details, wallet records, and transaction history — is stored and processed in line with the data handling terms. We do not share identifiable account data with third parties outside what is required to process a bKash or Rocket transaction.
We use cookies to maintain your login session across browser tabs and return visits on the same device. You can manage cookie preferences from your browser settings. Disabling session cookies will affect account continuity on your next visit.
Session management keeps your account accessible without repeated logins on the same device. If you access your account from a new device or browser, you will be asked to verify your credentials again before the session is established.
Transaction records are retained for the period set out in our data retention policy. To find out how long specific data types are held, or to request deletion where applicable, raise a data request through your account settings or the support contact form.
These questions cover what our members actually ask when reviewing the legal terms on ob 55. Each answer points to a specific action or account path rather than a general statement.
Access to ob 55 and the application of these terms depends on your local law and whether your region is among the eligible areas we serve. If you can access the platform and have an active account, the terms apply in full from your first login.
Your wallet history screen shows every bKash and Rocket transaction tied to your account, with a timestamp and reference number for each entry. Open it from your account page after logging in. If a record looks wrong, raise a support request with the reference ID.
Most account fields are editable from the settings screen. If the field you need to change is linked to a payment method like bKash, a verification step is required. Follow the on-screen instructions — the process is explained at each field that needs it.
We hold your login credentials, registered payment details, wallet transaction history, and session data. The data retention terms set out how long each type is kept. You can request a summary of your account data through the data request option in account settings.
You can raise a deletion request through the data request option in your account settings or via the support contact form. Whether the request can be fulfilled in full depends on legal retention requirements that apply to transaction records in your jurisdiction.
Send your question through the support form in your account dashboard. Include your account reference and identify the clause or section you are asking about. The support team handles policy queries through that route — do not use the transaction support path for policy-only questions.