App / Slots
ok330 sets out clear terms so you know exactly where you stand — what this platform covers, how your account data is handled, and how to reach us when you have a question. Access to ok330 and its features depends on your local law and the eligible regions we serve.
These terms govern your use of ok330 — the games lobby, account wallet, and payment flows including Nagad, Upay, and Bank Transfer. Whether you reach us via mobile browser or a full desktop session, the same policy applies across every device. Eligibility to use ok330 depends on your local law and the regions we currently serve; if you are uncertain whether access is permitted where you are, check the eligibility notice shown during account registration or contact our support team directly. We do not collect payment data ourselves — transactions processed through Nagad, Upay, or Bank Transfer are handled by those respective services under their own terms. Our policy governs what ok330 does with account-level data: session records, login history, and wallet activity linked to your profile. We update these terms when our services change, and we notify account holders through the contact address on file. Continued use after a posted update means you accept the revised terms. If any clause conflicts with the law of your jurisdiction, the legal requirement in your region takes precedence for users in that region. Questions about specific clauses can be sent to our support team — the contact routes are listed in the Support section below.
Transactions made via Nagad are processed by Nagad's own service. ok330 records the transaction outcome against your wallet but does not store your Nagad credentials.
Upay transfers follow Upay's own terms. Your ok330 wallet reflects confirmed transfer amounts once Upay confirms the transaction on their end.
Bank Transfer deposits and withdrawals are routed through standard banking channels. Processing times depend on your bank, and ok330 records only the confirmed credit or debit.
Not every interaction falls under the same part of our policy. Account activity, third-party payment services, site content, and external links each sit in a different part of the scope. Understanding the boundaries helps you know who to contact and what steps apply to your situation.
Login sessions, account wallet activity, and profile data fall fully inside this policy. Rules on access, data retention, and your right to review or correct records all apply here.
Payment processing via Nagad, Upay, or Bank Transfer is governed jointly — ok330 policy covers the wallet record, but the payment provider's own terms govern the transfer itself.
Game content supplied by our studio partners — Habanero, PlayStar, JDB, and CQ9 — is available through the ok330 lobby. Studio content terms sit with each provider; ok330 policy covers your access to that content through this platform.
Links to external sites or services fall outside this policy. ok330 does not control third-party terms, privacy practices, or availability, and we are not responsible for content or conduct on those sites.
You have concrete steps available to you at any point. Open your account settings page to review the transaction and session history we hold against your profile — every wallet credit, debit, and login event is listed there with a timestamp. If any detail is wrong — a display name, a contact address, or a linked payment method — you can update most fields directly from the account page. For changes that require verification, the form walks you through the identity step needed. If you want to raise a question about how your data is held, or request that specific records be reviewed, send the request through our support contact. We aim to respond to data questions through the same channel you used to send them. Deleting your account removes your profile from active use, but transactional records may be retained for the period required by applicable law in your region. The rights below are the practical actions available to you right now.
Open the account history section to see every session, wallet movement, and payment event logged to your profile.
Update contact information, display name, and linked payment methods from the account settings page; identity-verified fields show the verification step required.
Send a written request through our support contact if you want to know more about what data we hold or how long we retain specific records.
Submit a closure request via support. Transaction records may be kept for the period local law requires even after your account is closed.
If you have a question about these terms, your account data, or how a specific clause applies to you, use the contact routes listed here. We handle policy and data queries through the same channels as general account support.
Open the chat widget from any page while signed in. Use this for account-level questions — wallet records, access issues, or a question about a specific policy clause.
Send written policy or data requests to the support email address shown in your account settings. Written requests are useful when you need a record of the exchange.
The Help Centre linked from the site footer covers common questions about account access, payment records, and terms. Start there for straightforward queries before raising a direct request.
We hold account data only for as long as it serves a defined purpose — active account management, dispute resolution, or the retention period your local law requires. Cookies on ok330 are used for session continuity and basic analytics; you can adjust cookie preferences through the banner shown on first visit or through your browser settings at any time.
Active account data stays on file while your account is open. After closure, we retain only what applicable law in your region requires, and we do not use closed-account data for marketing.
Your account is protected by the credentials you set at registration. If you think your login details have been compromised, update your password from the account page and contact support immediately.
We use session cookies to keep you logged in and preference cookies to remember your lobby settings. Analytics cookies are optional and can be declined through the cookie banner.
When these terms change, we post the revised version and note the effective date at the top of this page. Account holders with a registered email receive a notification at that address.
These are the questions we hear most often about policy, data, and access. If yours is not here, reach out through the support routes listed above.
Access to ok330 depends on your local law and the eligible regions we serve. We do not make legal-certainty claims about any specific jurisdiction. Check the eligibility notice during registration or consult local regulations to confirm whether access is permitted where you are.
We hold your registration details, login history, wallet transaction records, and any contact information you have provided. You can review a summary of session and wallet activity directly from the account history section while signed in.
You can request account closure through our support contact. Once closed, active profile data is removed from use. Some transactional records may be kept for the period required by applicable law in your region, and we will tell you which records those are when you submit the request.
Most account details — contact address, display name, linked payment method — can be updated from the account settings page. Fields that require identity verification show the step needed. For anything you cannot change directly, send a request to support with the correction you need.
Nagad and Upay process payments under their own terms. ok330 records only the confirmed transaction outcome against your wallet — we do not store your wallet credentials or payment-service login details. Contact the relevant payment provider if you have a query about their data practices.
We post the revised policy here with an updated effective date and notify registered account holders by email. Continuing to use the platform after the effective date means you accept the updated terms. If you disagree with a change, raise the question with support before that date.