Slots / Sports
This page is where 585h sets out the legal terms that apply to your account: how it is opened, funded through bKash, Upay or Bank Transfer, and used in the lobby. What is open to you depends on your local law and eligible regions, so read the parts that apply where you are before you begin.
Legal terms on this site are written as a plain agreement between you and us. We keep the wording short on purpose. When you open an account, you accept the rules that sit behind it: how your wallet balance is held, what we expect from the details you submit, and how a dispute gets raised. Nothing on this page overrides the law where you live. Access depends on your local law and eligible regions, so a feature that works for one reader may not be open for another, and we do not present one set of rules as universal. Payment context belongs here too. If you fund the account with bKash, Upay or Bank Transfer, the terms around that deposit and any later withdrawal sit inside the same set. Your wallet provider or bank keeps its own conditions, and those are between you and them. Obligations run both ways. You agree to keep your sign-in details private, to hold one account in your own name, and to give accurate details when we ask for them. We agree to keep your transaction records visible in the account area and to answer questions through the published support route. If a clause changes, the updated version replaces the older one on this page, and the date shown on this page is the one that applies. If you would rather not accept a change, you can leave the service and ask us to close the account.
Not everything you touch on the site sits under the same set of rules, so it helps to know where our terms end. Account access, wallet activity and the records we keep are ours to set, and that is the ground this policy governs. The lobby screens you open while signed in come under the same agreement as the pages you read before you sign in. Outside that line sit services we do not run. Your bKash, Upay or Bank Transfer account is operated by the provider, and their own conditions govern the transfer, the confirmation message you receive and any query about a send that did not arrive. Your mobile network, browser and device maker also sit outside our terms. When a dispute is really about a wallet or a bank, the provider's own help desk is the faster path, and we can share the reference number your account shows so they can trace the transfer themselves.
Opening the account, signing in and keeping your details current sit with us. Your sign-in credentials, the single account held in your name and the accuracy of what you submit are governed here, together with how we act when the details we hold no longer match what you tell us.
Deposits and withdrawals made through bKash, Upay or Bank Transfer are governed on our side of the line: what we accept, how the entry appears in your transaction list, and how we handle a gap between what left your wallet and what reached the account.
Lobby screens, table graphics and the game pages you open while signed in come under the same agreement, whether you are on a phone or a laptop. Titles appear in the catalogue as provided to the lobby, and opening them creates no separate agreement between us.
Your wallet provider, bank, mobile network and browser maker sit outside this agreement. Their rules govern transfer handling, confirmation messages and network behaviour. Where a question is really about their side, we can point to the reference number your account shows so they can trace the transfer.
You have more than one lever here, and none of them needs a phone call. Start inside the account, where the transaction list shows each deposit and withdrawal beside the route you used, with the reference number tied to it. That entry is the first thing to check before you raise anything. If a detail we hold about you is wrong, ask for a correction. Say which field is out of date and what it should read, and send the request from the account you signed in with. For everything else, such as a clause you want explained or a charge you do not recognise, the published support route is the place to raise it. We take requests in the order they arrive, and we will say plainly if the question belongs with your wallet provider instead of us.
Sign in and open the transaction list. Each deposit and withdrawal appears beside the route used and the reference number attached to it, so you can match what left your wallet against what reached the account before you ask us anything.
When a name, contact number or saved detail is out of date, send a correction from inside the account. Point at the field, state what it should read, and we update the record once the request can be matched to your signed-in session.
For a clause you want explained, or a charge you do not recognise, use the published support route and quote the reference number from your transaction list. That one line lets us find the entry quickly and saves you repeating the same details twice.
You can ask us to close the account whenever you choose. Access tied to it ends once the request is handled, and where a transaction record still has to be kept, we hold it under the retention rules described on this page rather than clearing it the same day.
Questions about these terms reach us through the routes published on the site, and nowhere else. We do not chase people on messaging apps, and we never ask you to send a password or a wallet PIN through any channel. If a message, call or page claims to act for us and asks for those details, treat it as an attempt to take your account and report it through the help link inside your account. The quickest way to a useful answer is to bring the reference number. Your transaction list shows one beside each bKash, Upay or Bank Transfer entry, and quoting it tells us exactly which record to open. Say what you expected and what you saw instead, in one or two lines. Requests are answered in the order they arrive, and we will tell you when a question sits with your wallet provider rather than with us.
Once you are signed in, the help link in your account area opens a request tied to your profile. Anything you send from there carries your account reference along with it, so we can look at the right record without asking you to repeat what we already hold.
If you cannot sign in, the contact form published on this site is the route to use. Include the wallet name you paid with and the reference number from your own record, and keep the wording to what happened and when you first saw it.
Tell us straight away if a message, call or page claims to come from us and asks for a password, a wallet PIN or a payment to release a withdrawal. Use the same published route, attach a screenshot if you have one, and do not act on the instruction.
What we keep is tied to running your account: the details you submit when you open it, the transaction entries linked to bKash, Upay or Bank Transfer, and the sign-in activity shown in your account. Cookies do the plumbing. They hold your session while you move between lobby pages, remember the language you picked, and show us which areas load slowly on a phone so we can fix them. Retention follows the same logic. A payment question can arrive well after the transfer itself, so a record is held while the account is open and for the period set out on this page afterwards. You can ask what we hold and why, and you can ask for a change to the details on file. Keep your sign-in details to yourself, because nobody from our side will ask for them, in any channel, at any time.
The details you submit when opening the account, the transaction entries tied to bKash, Upay or Bank Transfer, and the sign-in activity your account shows. You can ask which of these we have and why each one is needed to run the account.
Cookies keep you signed in between pages, remember the language you chose and tell us where pages load slowly on a phone. Clearing them through your browser settings signs you out and may reset a preference you had saved for later visits.
Your password and wallet PIN stay yours. Nobody on our side asks for them, and no route published on this site will request them from you. If a page or message does, treat it as an attempt at account takeover and report it through the help link.
Ask for the details we hold about you, a correction, or a deletion where no retention rule applies, through the published support route. Each request is logged against your account and handled in the order it arrives, with a reply through the same channel you used.
Most questions that reach us about this page are about where the rules apply, what we keep and how to get in touch. The answers below take the ones we hear most often. If yours is not among them, the published support route is the way to ask, and bringing a reference number from your transaction list usually gets you a clearer reply first time. Nothing on this page replaces the law where you live, and nothing here changes conditions set by your wallet provider or bank. If you are weighing a specific clause before opening an account, the paragraph above the answers explains how the agreement is written, while the questions deal with the practical side of records, corrections and contact.
It applies wherever you reach the site, but what we can offer you depends on your local law and eligible regions. A feature may be open in one region and not another. If something is not available where you are, we will say so rather than leave you guessing.
Account access, wallet activity and the records we hold are governed here. Services run by others, such as your bKash, Upay or Bank Transfer provider, your bank, your network and your browser, follow their own conditions, and those sit outside this agreement.
Send the request from inside your account so it matches your signed-in session. Name the field that is wrong and what it should read instead. We update the record once the request checks out, and the change shows in your account area.
Access ends once the closure request is handled. Transaction entries are kept for the retention period set out on this page, because a payment question can arrive long after the transfer and we need the entry to answer it properly at the time.
Yes. When a clause is updated, the new wording replaces the old one on this page and the date shown here is the version that applies. If you would rather not accept the change, you can leave the service and ask us to close the account.
Use the help link inside your account, or the contact form published on this site if you cannot sign in. Quote the reference number from your transaction list, set out the question in a line or two, and we will reply through the same channel.