Slots / App
This is where ok69 lays out the rules behind your account: what our legal notice covers, how wallet activity gets recorded, and which choices stay in your hands. Access depends on your local law and eligible regions, so read this page before you move money in or out.
Legal footing first: we publish the rules that sit behind an ok69 account instead of burying them in a signup screen. Whether you can open an account, deposit, or use any part of the sportsbook and casino lobby depends on the law where you live and on the eligible regions we can serve. We do not present ourselves as any particular authority, and we do not promise access where your local rules say no. You are the one who knows your own position, so confirm it before you move money. What this notice covers: how an account is opened and closed, how wallet activity through Nagad, Upay and Bank Transfer is recorded, how gameplay is scored, and what happens if a dispute comes up. It also reaches the content side, the sportsbook markets, live tables and slot rooms you see once you sign in. Two practical habits help you stay on the right side of it. Keep your account details accurate, and read the notice version published on this page, because that is the one that applies to you. If a mandatory rule in your country conflicts with something written here, the local rule wins. When we change how the account or the lobby works, we update the text here, and the version live on this page is the current one. If any line is unclear, ask us through the support routes further down before you act on it.
Think of this policy as the frame around your account rather than the whole building. Inside the frame: how you get in, what you can do once you are signed in, and how we record what happens. Outside the frame: anything run by another company, which carries its own terms and which we cannot change on their behalf. Account access sits at the centre. The sign-in steps, the email confirmation and the session on your device are covered here. So are wallet movements. When you send money through Nagad, Upay or Bank Transfer, the record we keep of that request is part of this policy, though the wallet operator's own rules still apply to their side of the transfer. Site content and gameplay come next: the sportsbook markets, live tables and slot rooms we publish, plus the way results are logged. Third-party services are a different matter altogether. A payment provider's app, a browser extension or a store page you reach from us sits under their policy, not ours. If something breaks there, start with them and bring the reference back to us.
Everything around getting in sits here: creating the account, confirming the email address you gave us, signing back in and managing the session on your own phone or browser. If your region is not eligible, we cannot open the account, and the signup step will say so before you go further.
When you send money through Nagad, Upay or Bank Transfer, the request we log is covered by this policy: the amount, the date and the reference attached to it. The wallet operator's own rules still govern their side of the transfer, and we cannot change those on their behalf.
The sportsbook markets, live tables and slot rooms we publish sit inside this policy, along with the way results are recorded, how a disputed round is checked against our own log, and what we show you about it in the account area.
A payment app, a browser extension or a store page you reach from us runs under someone else's terms. Their rules apply to that service. Start with them, then bring the reference back to us so we can check what our side of the record shows.
You are not stuck waiting on us to explain your own account. Several actions are yours to take directly, and each follows a path you can already see in the app or the browser. First, read your own records. Order history, wallet movements and gameplay entries sit in your account area, and they are the same entries we would look at if you asked. Second, correct what is wrong. If a phone number, an email address or a name on your profile no longer matches, change it in your profile fields; accurate details make every later step shorter. Third, ask when something does not add up. Bring the reference number, the date and the payment name, Nagad, Upay or Bank Transfer, and put your question in writing through a published route. Fourth, ask for a second look when the answer you got does not close the issue. You can reopen it and ask for the record to be checked by a person who can see the entry itself. Nothing here takes away a right your local law gives you.
Your account area lists wallet requests, gameplay entries and profile changes. Open it before you write to us. The same entries we would pull up are already on your screen, and the reference numbers you need sit right beside them.
Email, phone and profile fields can be edited by you. Update anything out of date, then save it. If a field will not save, note what you typed and where, and pass that to support so we can see what your account shows on our side.
Send the date, the amount and the payment name, Nagad, Upay or Bank Transfer, through a published contact route. One question per message keeps the thread readable, and a reference number leads to a more accurate answer about your account.
If a reply does not settle the issue, say so and ask for the record to be checked again by someone who can see the transaction entry itself. Keep everything in the same thread so the history stays in one place for both sides.
When a question about the policy needs an answer from us rather than from the page, use one of the routes we publish. They stay short on purpose: a signed-in route inside your account, a written route through the contact address shown here, and the footer link that opens the same contact page. Start signed in where you can. A message opened from your account carries your account reference with it, which saves you retyping the details of a wallet request made through Nagad, Upay or Bank Transfer. If you cannot sign in, the written route still works, so include the email address on your account and the part of the policy you are asking about. Two things help you get a useful reply. Describe what you expected and what you saw instead, and attach the reference number where one exists. Never send your password or a one-time code to anyone, including us. Reply handling moves with volume, so watch the thread for an update rather than assuming a fixed window. Keep that thread open if you need to chase the same issue.
Sign in and open the contact option in your account area. Your account reference travels with the message, so you do not retype the details of a wallet request made through Nagad, Upay or Bank Transfer, and we can match your question to the right entry straight away.
Use the contact address shown on this page when you cannot sign in. Include the email address on your account, the part of the policy you are asking about and any reference number, so the reply reaches the right thread the first time.
The footer link on this site opens the same contact page. Use it when you are reading on a desktop, or when you want to send a longer message about the policy with several points and references listed together in one place.
Handling your details is not a side note for us; it sits under the same policy you have just read. What we hold is the account detail you give us, your email, your profile fields and your sign-in history, plus the transaction entries that come from wallet requests made through Nagad, Upay and Bank Transfer. That record is what lets us answer a question about a payment long after the fact. Cookies keep the session alive and remember small choices such as your language. You can clear them from your browser whenever you like, and the trade-off is that you sign in again. Blocking all cookies may stop parts of the lobby from loading properly, so change one setting at a time and watch what changes. On security, the basics are in your hands. Keep your password to yourself, sign out on shared devices, and treat any message that asks for your code as a fake. We do not ask for it. Account records stay while the account is open and for the period local rules require afterwards, then we remove what is no longer needed.
Your email, profile fields, sign-in history and the transaction entries that come from wallet requests through Nagad, Upay or Bank Transfer. That is what we use to answer your questions about the account, and we do not gather more than the account itself needs.
Cookies keep your session open and remember small choices such as language. Clearing them signs you out. Blocking them all can stop parts of the lobby from loading, so change one setting at a time and watch which parts of the site respond.
Your password stays private, so sign out on shared phones and browsers. Treat any message asking for your password or a one-time code as a fake, whoever it appears to come from. We do not ask for your code and do not need it to look at your account.
Account records stay while the account is open and for the period local rules require afterwards, then we remove what is no longer needed. To ask what we hold, or to have something changed, use a published contact route and name the record you mean.
Most of what people ask us about this page comes down to a few things: whether they can use the site where they live, what we keep about them, how to change something, and how to reach a person. Here are the questions we see often, answered in the same plain terms we use above. Read them as a starting point rather than a replacement. The notice itself is the document that applies, and your local law sits above both of us. If your question is not here, say a wallet request through Nagad, Upay or Bank Transfer that looks wrong, or a profile field that refuses to save, send it to us through a published route with the reference attached. We would rather answer it before you act than unpick it afterwards.
Access depends on your local law and on the eligible regions we can serve. Create the account, confirm your email address, fill in the profile fields, then follow whatever verification the account area asks of you. If your region is not covered, the signup step tells you before you go any further.
How an account is opened and closed, how wallet activity through Nagad, Upay and Bank Transfer is recorded, how gameplay and results are logged, and how you raise a question about any of it. Third-party services you reach from us sit under their own terms.
Open your account area and look at the transaction list. Each entry carries a date, an amount and a reference you can quote. On mobile, the same list is in the account menu under your wallet, so you can copy the reference straight into a support message.
You can edit your own profile fields at any time. For anything you cannot change, ask through a published contact route and name the record you mean. Some entries stay for the period local rules require, so removing every trace is not always possible.
No. This page explains how we run the account and the lobby. If a mandatory rule in your country says something different, that rule applies to you, and it sits above anything written here. Check your own position before you deposit or play.
Treat it as a fake and do not reply, whoever it claims to come from. We do not ask for your password or a one-time code, and we do not need either one to look at your account. Report it to us through a published route.