Casino / Slots
At 333login, your personal data belongs to your account — not to a mailing list, not to a third party, and not to any service outside the scope of this policy. How we collect, store and use your information depends on your local law and the eligible regions where access is permitted, and this page sets out exactly what that means for you.
This policy applies to information collected when you register an account, log in from a mobile device, make a deposit through Rocket, Upay or Bank Transfer, or contact us through any published support route. We collect the minimum data needed to operate your account — your registered contact detail, transaction records linked to your wallet, and device session data used to keep your login secure across browser and app. We do not sell your data to advertisers. We do not share your account details with third parties except where required by the applicable law of your region or to process a transaction you initiated. Data we hold is kept for as long as your account remains active and for a retention period after closure as required under the rules applicable to your eligible region. If you access 333login from a jurisdiction where online account services are restricted, your eligibility and the data we can process on your behalf depends on the laws of that region. We aim to be transparent about every data category we hold, and this policy is the place to check before you register or make any account-level decision.
Deposits and withdrawals processed through Rocket are logged as transaction records on your account. These records include the amount, timestamp and wallet reference. We retain them for the period required under the rules applicable to your eligible region.
When you fund your account via Upay, the wallet reference is stored against your account record for reconciliation purposes. We do not store your full Upay credentials — only the reference needed to match the transaction to your account.
Bank Transfer deposits are matched to your account using the reference number you provide at the time of the transaction. That reference and the deposit amount are held in your account history and are visible to you in your signed-in account area.
We collect session identifiers and device type to keep your account secure across mobile and browser access. This data is used only for login integrity and is not shared with game studios or payment processors.
This policy covers data we control directly — your account record, your transaction history and the communications you send through our published support routes. It does not extend to third-party services you reach from our lobby, and it does not govern the data practices of payment processors like Rocket, Upay or Bank Transfer, who hold their own separate policies. Availability of account services depends on your local law and eligible region.
Any information you provide when creating or logging into your account — contact detail, password hash, device session — falls inside this policy. We control this data and this policy governs how we handle it.
Deposits and withdrawals processed through our verified payment rails are part of your account record and covered here. The payment processor's own data handling sits outside our policy boundary.
Pages you browse, game categories you open and lobby sections you visit generate session data we use for account security. We do not build marketing profiles from browsing behaviour.
Links to external sites, game studio platforms or any service outside 333login are outside this policy. Once you leave our domain, the data practices of that third party apply, not ours.
You have the right to see the personal data we hold against your account, and you can act on that right without waiting for us to prompt you. Log into your account and open the account details section — your registered contact information, deposit history and active session records are visible there. If any detail is wrong, you can update it directly in the account settings fields or raise a correction request through our support route. If you want to know what categories of data we hold beyond what is visible in your account, send a query to our support team using the contact route published on the site. We will respond within the timeframe required by the rules applicable to your eligible region. Account closure requests are also handled through the same support route. Closing your account does not immediately erase all records — some transaction data is retained for the period required under applicable rules — but we will confirm exactly what is retained and for how long when you make that request.
Your account history, registered details and active sessions are visible in the signed-in account area. No special request is needed to view the data held in your own account.
Registered contact details can be updated in account settings. For corrections that require identity verification, raise a request through the published support route and follow the steps shown there.
For questions about data categories we hold that are not visible in your account, contact our support team through the route published on the site. We will identify the data and confirm its retention period.
Account closure and data retention queries are handled through support. We will confirm what records are kept after closure and the basis on which we retain them under the rules applicable to your region.
If you have a question about this privacy policy, a correction to request, or a data query that your account area does not answer, use the contact routes published on 333login. We do not accept policy queries through social channels not listed on the site.
Log into your account and use the support option in the account menu to send a data or policy query directly to our team.
The contact details published on 333login are the correct route for privacy queries. Use the form or address shown there — do not use third-party contact aggregators.
When this policy changes in a way that affects your account, we will notify you through the contact detail registered to your account before the change takes effect.
Security, retention and access control are the three areas that matter most to how we handle account data. Each one has a concrete process behind it, not just a policy statement.
Your login session is protected by a server-side session token tied to your device. If we detect an unusual access pattern — a new device or a location outside your normal session — your account may prompt re-verification before access is granted.
We keep your account record for as long as your account is active. After closure, transaction records are retained for the period required under the rules applicable to your eligible region, then deleted. You can request confirmation of your retention period through support.
We use session cookies to keep you logged in across pages and to maintain your account state during a browser session. We do not use third-party advertising cookies. Cookie settings can be reviewed in your browser at any time.
If we change how we handle a category of data that affects you, we update this page and notify you through your registered contact detail. The date of the last update is shown at the bottom of this policy page.
If your question is not covered below, the support route on 333login is the right place to send it.
We collect the contact detail you provide at registration, the device and session data generated when you log in, and the transaction records linked to your account activity. We do not collect payment credentials — only the wallet references needed to match a deposit or withdrawal to your account.
Deposits made through Rocket or Upay are logged as transaction records in your account history. Each record shows the amount, the timestamp and the wallet reference. These records are visible to you in your signed-in account area and are retained for the period required under the rules applicable to your eligible region.
The data visible in your account area — registered details, transaction history, active sessions — is available to you without any special request. For data categories not shown there, raise a query through the published support route and we will provide a full account within the timeframe required by your eligible region's rules.
Access to your account data is restricted to the team functions that need it to operate your account — support, compliance and payment reconciliation. We do not share your data with game studios like CQ9, PG Soft or Microgaming; they receive only the session data needed to run a game round, not your account record.
Open the account settings section after logging in. Most contact details can be updated directly there. If a correction requires identity verification — for example, changing a registered mobile number — raise a request through the support route published on the site and follow the steps shown.
Closing your account stops new data collection. Some transaction records are retained after closure for the period required under the rules applicable to your eligible region. When you submit a closure request through support, we will confirm exactly which records are kept and for how long before the process completes.