Slots / App
333com collects only the data needed to run your account, process wallet transactions via Upay or Bank Transfer, and keep your session secure. What we collect, why we collect it, and how long we keep it — all of that is set out plainly below. Access to this platform depends on your local law and eligible regions.
When you open an account with us, we collect the information you provide directly — your name, contact details, and the payment method you choose to connect, whether that is Upay, Bank Transfer, bKash, Nagad or Rocket. We also collect session data automatically: device type, browser, IP address and pages visited within the platform. This data helps us identify your account, process wallet activity and detect unusual access patterns that might put your account at risk. We do not sell your personal data to third parties. We do not share it with advertising networks outside our own platform. Data shared with payment processors — such as when you initiate a Bank Transfer or Upay transaction — is governed by those providers' own terms, and we encourage you to review them. Retention periods vary by data type: active account data is kept while your account remains open; transaction logs are held for the period required under the financial record-keeping obligations that apply in your eligible region. If your account is closed, we retain only what we are legally required to keep, then delete the rest. We update this policy when our practices change, and we post the revised version here with a new effective date. Continued use of your account after a policy update means you have had the chance to review the new terms.
Payment data processed through Upay is shared only to complete your transaction. We do not store full wallet credentials on our side.
Bank Transfer details you submit are passed to the relevant processing channel and are not retained beyond what the transaction record requires.
If you connect a mobile wallet such as bKash, Nagad or Rocket, those session tokens are handled under the respective wallet provider's data terms as well as ours.
Not every interaction with 333com falls under the same data rules. Some areas of the platform have distinct data flows — account access is different from a payment transaction, and our own site content is different from a third-party link you follow. The four areas below clarify where this policy applies directly, where it applies in part, and where a separate set of terms takes over. Understanding the boundary helps you know who to contact when a data question comes up.
When you log in, update your profile or change account details, this policy applies in full. We control what is collected, how it is stored and how long it is kept. You can review your account data directly from the account settings screen.
When you initiate a deposit or withdrawal — via Upay, Bank Transfer or a connected mobile wallet — your data passes through a payment processor. This policy covers what we collect on our side; the processor's own privacy terms cover their side.
Session data generated while you browse the lobby or open a game is collected by us and falls under this policy. Game content itself is supplied by studios whose software runs within the platform, but the session record belongs to your 333com account.
If you follow a link that takes you away from 333com — to a payment provider page, a support article on an external site or any other destination — this policy no longer applies. We have no visibility into what those sites collect.
You are not just a passive subject of this policy — you have real, actionable choices. You can review the personal data we hold on your account, ask us to correct anything that is wrong, and raise a question if something in this policy is unclear to you. These rights apply to eligible account holders in supported regions; whether a specific right is enforceable depends on local law where you are located. The steps for each are straightforward and do not require a formal legal process — a written request to our support channel is enough to start. If you have connected a payment method such as bKash or Nagad, the data associated with those wallet sessions can be reviewed through your account transaction history. We aim to respond to data requests within a reasonable period; the exact timeframe depends on the complexity of the request and what records are involved.
Open your account settings to see the personal details we hold, including contact information and linked payment methods. Your transaction history shows wallet activity connected to Upay, Bank Transfer and any other method you have used.
If your name, contact details or any account field is recorded incorrectly, you can update most fields directly in account settings. For fields you cannot edit yourself, contact support with the correction you need and we will handle it from there.
If any part of this policy is unclear — what data we hold, why we hold it, or how long we keep it — contact us through the support route listed in the Support section below. A plain-language question is all that is needed; no formal legal language required.
You may request that your account be closed and your data deleted, subject to the retention obligations that apply in your region. Submit the request through the published support channel and we will walk you through what happens next.
If you have a question, correction request or concern about how your data is handled under this policy, the channels below are the right place to start. We do not publish separate contact details for data queries — the same support routes that handle account and wallet questions also handle privacy matters. State clearly that your message is about a privacy or data request so it can be directed to the right person on our side.
Open the live chat widget from any page on the platform. Describe your privacy question or data request in the first message so it is routed correctly from the start.
Send your privacy or data request to the support email address published in the Contact section of the platform. Include your registered account details so we can locate your record without delay.
The Account Help section inside your logged-in dashboard covers common data and privacy questions. Check there first — many requests, such as reviewing transaction history or updating contact details, can be resolved without contacting support at all.
Knowing where your data goes and who can access it is a reasonable expectation, not a bonus feature. Here is how we handle the four areas that matter most to account holders in Bangladesh: storage and access controls, cookies, session security and the process for requesting changes. Each area below reflects our current practice — if that practice changes, this page is updated before the change takes effect.
Your account data is stored on secured servers with access restricted to authorised personnel only. We do not grant third-party access except where required to process your chosen payment method — such as a Bank Transfer or Upay transaction — or where required by applicable law in your region.
We use cookies to keep your session active, remember your language preference and measure which parts of the platform you visit most. You can manage cookie preferences through your browser settings. Disabling all cookies may affect how some account features function.
Login activity is monitored for patterns that suggest unauthorised access. If we detect something unusual, we may restrict account access and contact you through your registered details. Keeping your contact information current in account settings helps us reach you quickly if that happens.
If you want to update the data we hold, correct a record or ask about retention periods, the support routes in the section above are the right starting point. For formal data requests, state your full account details and the specific change or information you need.
The questions below cover what account holders in Bangladesh ask most often about data, privacy and their rights under this policy. If your question is not listed here, the support routes in the section above are the right next step.
We collect the details you enter during registration — name, contact information and your chosen payment method. We also collect session data automatically, including your device type, browser and IP address. This helps us identify your account and keep your session secure.
We share data only where necessary to process your transactions — for example, passing payment details to the Upay or Bank Transfer processing channel. We do not sell your data to advertisers or share it with unrelated third parties. Each payment processor has its own data terms that cover their side of the transaction.
Active account data is kept while your account remains open. Transaction logs are retained for the period required under financial record-keeping obligations in your eligible region. Once your account is closed and retention obligations are met, remaining data is deleted.
Yes. Open your account settings to review the personal details and linked payment methods we hold. Your transaction history shows all wallet activity, including Upay and Bank Transfer records. For data not visible in settings, contact support with a written request and we will provide what we can.
For corrections, update what you can directly in account settings. For fields you cannot edit, or to request deletion, contact us via live chat or the support email published on the platform. State your account details and the specific change you need, and we will follow up from there.
This policy applies to account holders in all regions where the platform is available. Whether you can access the platform and what rights apply to your data depends on your local law and eligible region. We recommend checking your local legal position before opening an account.
When your account is closed, we retain only what we are legally required to keep — typically transaction records for a defined period under applicable financial regulations. Once those obligations are fulfilled, remaining personal data is deleted. You can initiate a closure request through the published support channel.