Slots / Live
30ok is built around account privacy as a practical standard, not a formality. This policy tells you exactly what we collect, how we use it, and what steps you can take if something needs correcting — with access subject to your local law and eligible regions.
When you open an account, we collect the information you provide during registration — name, contact details, and the payment method you connect, whether that is bKash, Upay or Bank Transfer. Transaction records tied to those payment methods are retained as part of your account history, and you can request a summary of that history through the support route listed on this page. We also collect session data: device type, browser, and interaction patterns that help us keep the account environment working properly on mobile. We do not sell your personal data to third parties. Data shared with payment processors like bKash or Upay is limited to what those processors need to complete your transaction — nothing beyond that. Cookies and similar tracking tools are used for session management and fraud prevention; you can adjust cookie preferences through your browser settings, though some account functions require session cookies to operate. Retention periods depend on the nature of the record: payment records are held for as long as regulatory and operational requirements apply, which varies by the rules of your eligible region. For users in Bangladesh, access to and handling of this data is subject to local law.
This policy covers data collected when you create or use your 30ok account — login activity, profile details and any updates you make to your registered contact information. Actions taken inside your signed-in account fall within this scope.
Records of deposits and withdrawals processed through bKash, Upay or Bank Transfer are within scope. We hold only the transaction metadata needed for account records; full payment credentials are handled by the respective payment processor, not by us.
General browsing of site content — viewing game categories, reading policy pages or checking lobby sections — generates session data covered here. No personal identification is inferred from browsing alone unless you are signed into your account at the time.
Links to external services, including game content providers and payment processors, are outside this policy's scope once you leave our environment. Third-party privacy terms apply from the point of handoff. We do not control how those services handle data on their own platforms.
You have real, actionable choices under this policy — not just passive reading rights. If you want to see what data we hold on your account, you can request a summary through our support channel, and we will respond with what is on record. Corrections to your registered details — contact number, email address, or the name on the account — can be made directly from the account settings area when you are signed in. If you believe a transaction record is incorrect, raise it through the same support route and include the payment reference shown in your account history. For bKash or Upay transactions, the reference number from your mobile wallet confirmation matches the one in your account record, which helps us locate the specific entry faster. If you want to close your account, that request is handled through the support route as well; we will confirm what data is retained after closure and for how long, in line with applicable rules for your eligible region.
Request a summary of the data we hold on your account via our support route. We will confirm what is on file — registration details, payment history references and session log indicators — without requiring you to re-verify beyond your account login.
Update your contact number, email or account name from the settings area while signed in. For name corrections that require document verification, raise those through support with the reference shown in your account profile.
If you have a question about how a specific record was created — a bKash deposit entry, a session log or a device record — contact support with the relevant account reference. We will explain the record or flag it for review.
Account closure requests are handled through the support route. We will confirm retention timelines for your region before processing, so you know what stays on record and for how long under applicable local rules.
The live chat widget is available from within your signed-in account. Use it to raise a data question, request a record summary or flag a transaction discrepancy. Have your account reference ready when you connect.
For written data requests — corrections, summaries or closure — email through the address shown in the Help section of your account. Written requests create a reference trail, which is useful for payment-record queries involving bKash or Bank Transfer entries.
The Help section inside your account lists the current support routes and the steps for common policy requests. Check there first for the published contact paths; the information is kept current and reflects what is actually available.
Session cookies keep your account active and protect against unauthorised access during a session. You can adjust non-essential cookie preferences in your browser settings. Disabling session cookies will affect how the account environment functions, which is noted in the cookie notice.
Transaction records for bKash, Upay and Bank Transfer are held for as long as required by the operational and regulatory standards that apply to your eligible region. We do not extend retention beyond what those requirements specify.
Security settings for your account — including the steps to review active sessions and remove unrecognised device access — are available from the security area inside your signed-in account. Check those settings if you notice activity you did not initiate.
When this policy changes in a material way, we update the version date at the top of this page. Continued use of your account after a posted update means you have seen the revised terms. Contact support if you want clarification on any change before continuing.
We collect the details you provide during registration — name, contact information and the payment method you connect. Session data such as device type and browser is also recorded. Payment credentials for bKash or Upay are handled by those processors directly, not stored by us.
Yes. Send a request through live chat or the email route in your account Help section. We will respond with a summary of what is on record — registration details, payment history references and session indicators. Have your account login ready to verify the request.
Log in and go to account settings — most contact details can be updated directly from there. If a correction requires document verification, raise it through support with the reference shown in your profile. We will confirm once the update is applied.
We share only what is necessary. Payment processors like bKash and Bank Transfer receive only the transaction data needed to complete your deposit or withdrawal. We do not sell personal data. Third-party game content providers receive session context, not your personal registration details.
Retention depends on the rules that apply to your eligible region. Records are held for as long as operational and applicable requirements specify — we do not extend that beyond what is required. Contact support if you want to know the retention period that applies to your account.
Go to the security area inside your account to review active sessions and remove any device you do not recognise. Then contact support through live chat or email with your account reference. We will check the access log and advise on next steps based on what the record shows.