Live / Casino
These terms govern how ok666 operates for you, where local law and eligible regions permit. Read through the scope, your rights, and how to reach us if anything needs correction or clarification.
Access to ok666 is available only where local law in Pakistan permits online account activity of this kind. We do not extend service into regions where such activity is restricted, and we do not represent that access is unrestricted in any jurisdiction. By opening an account, you confirm that you are doing so in a region where this is permitted under applicable law. Payment methods — including Raast, Bank Transfer, and Debit Card — operate subject to the rules of the respective payment provider and any applicable regulatory framework. We process transactions through the channels shown at account setup; the current available options are displayed in your account dashboard after login. We do not guarantee availability of any payment rail at all times, as provider-side conditions apply. Account data you provide at registration is held for the purpose of running your account, verifying transactions, and responding to support requests. We retain records in line with our data retention practice, described in the trust section below. If you have a question about what we hold, the support routes listed on this page are the right place to start.
This policy covers how ok666 handles your account relationship — from login to transactions to support contact. It does not extend to third-party services connected through the platform, which operate under their own terms.
Login sessions, account creation, and identity verification steps are covered by this policy. The rules here govern how your account is opened, held, and closed, and what records we maintain about those actions.
Deposits and withdrawals processed through Raast, Bank Transfer, or Debit Card fall within scope. The transaction record visible in your account dashboard is the authoritative log for any amount moved through your wallet.
Game content supplied by studios in our lobby — including titles from Pragmatic Play, Habanero, and CQ9 — is governed by those studios' own content terms. We carry their titles; their licence conditions for the content remain theirs.
External payment providers, network carriers, and any linked services outside the ok666 platform operate under their own terms. This policy does not override or replace those terms, and we hold no liability for third-party conduct.
You have practical options for how your data and account records are managed. Start from your account dashboard — the transaction log there shows every deposit and withdrawal processed through Raast, Bank Transfer, or Debit Card, with timestamps. If a record looks wrong, you can raise a correction request directly through the support channel; we will review the account log and respond. Personal details entered at registration — name, contact number, verified payment method — can be updated by following the fields shown in your account settings page. For anything beyond a self-service update, the support team holds the authority to make adjustments on the account side. We aim to respond to correction and data requests within the timeframe stated in your support ticket. If your request involves closing the account or deleting stored data, submit that through the formal support route rather than the in-session chat, so it is logged and traceable.
Open your account dashboard after login to see the full transaction history. Every Raast, Bank Transfer, and Debit Card movement is logged there with date and status.
Account name, contact number, and linked payment method can be updated from the account settings page. Follow the fields and verification steps shown there to complete the change.
If you have a question about how your data is used or what this policy covers, send it through the support contact listed on this page. Reference your account ID so it is matched to your record quickly.
For account closure or data deletion, use the formal support route rather than live chat. This creates a traceable log and ensures the request is handled at the account level, not just the session level.
If something in this policy needs clarification or you have a question about your account rights, the routes below connect you to the right place. Always include your account ID in the message so we can match the request to your record without delay.
Send policy and data questions to our support email address shown in your account dashboard. Include your registered contact number and a brief description of the issue so it reaches the right queue.
The in-session chat option is available from the account area after login. Use it for quick clarifications on policy scope or to be directed to the correct form for a formal request.
Account closure, data deletion, and formal correction requests require a written submission through the support ticket system. This creates a reference number and a traceable log for your request.
We collect the account data you provide at registration and the transaction data generated when you use Raast, Bank Transfer, or Debit Card. That data is held for as long as your account is active and for a retention period after closure, as required to satisfy any applicable record-keeping obligation. Cookies are used to maintain your login session across devices — if you switch from a phone to a desktop, the session token keeps your account state without requiring a full re-login each time. You can clear cookies from your device browser settings; this will end active sessions and require a fresh login. We do not sell account data to third parties. Requests to review, correct, or delete data are handled through the support routes listed on this page.
We hold registration details and transaction records tied to your account. This includes the payment method you verified — Raast, Bank Transfer, or Debit Card — and the history of amounts processed through your wallet.
Session cookies keep your account accessible as you move between devices. They do not store payment credentials. Clear them from your browser settings at any time; this ends the active session and prompts a fresh login.
Account and transaction data is retained while your account is open and for a period after closure. The retention period follows applicable record-keeping requirements. Closure requests submitted through support are logged with a reference number.
All data, correction, and security questions go through the support routes on this page. Formal requests — including data deletion — require a ticket submission so they are traceable from submission to resolution.
These are the questions we hear most from account holders about how this policy works, what it covers, and how to act on your rights.
Access to ok666 is available where local law in Pakistan and your specific region permits it. This policy applies to eligible accounts in those regions. If you are unsure whether access is permitted in your area, check the applicable local regulations before opening an account.
We hold the registration details you provided when opening your account — name, contact number, verified payment method — and a full log of transactions processed through Raast, Bank Transfer, or Debit Card. Your account dashboard shows the transaction history after login.
Account name, contact number, and linked payment details can be updated from the account settings page. Follow the fields and verification steps shown there. For changes that cannot be made self-service, raise a correction request through the support ticket system with your account ID.
Yes. Submit a data deletion request through the formal support route — not live chat — so it is logged with a reference number. We process these requests in line with applicable retention requirements, which may mean certain transaction records are kept for a defined period after account closure.
When you close your account, transaction and registration data is retained for a period required by applicable record-keeping obligations. After that period, data is removed from active systems. You will receive a confirmation reference when the closure request is processed.
Session cookies are used to maintain your login state across devices. Without them, your session will not persist between page loads or devices. You can clear cookies from your browser settings at any time; doing so will end your active session and require a fresh login.