Reference

Privacy Policy for Your com303 Account

Our Privacy Policy explains how com303 collects, uses and protects the details connected with your account, device and wallet activity.

Account dataWallet referencesCookie choicesPolicy requests
com303 Privacy Policy for Your com303 Account
REQUEST A RESPONSE

Get Help With Privacy Requests

A clear request path helps you ask about the personal data connected with your account. Use the support route shown inside your account area and include the email or phone detail used during registration, plus the subject of your request. We may ask for an account check before disclosing or changing data, so another person cannot act on your behalf. If a wallet receipt or device record is relevant, attach only the reference needed to locate it.

Team online

Account data request

Ask us what account details we hold and why they are used. Include your registered phone detail and the account step concerned, such as phone verification or access to the lobby from a mobile browser.

Wallet record query

For a DANA, OVO, GoPay or QRIS privacy question, send the payment reference visible in your receipt. We use that reference to locate the record without asking you to share a wallet password or security code.

Correction request

Tell us which account detail needs correction and why. We may request a confirmation through the registered phone path before changing it, particularly when the request could affect access to your account or stored transaction records.

DATA HANDLING

How We Protect Your Account Details

Our privacy process separates account identity, technical access records and payment references so each detail has a clear purpose.

Collection purpose

We collect registration details to create your account, confirm the phone path and support sign-in. Game activity, such as opening rocket4d or bingo4s, may create technical records used to maintain an accurate account history and investigate access concerns.

Cookie control

Session cookies keep your account path connected while you move from login to the lobby. You can adjust browser cookie settings, although removing required cookies may interrupt sign-in or prevent the site from remembering a selected language or session state.

Security checks

We compare sign-in time, device signals and account activity when access appears unusual. A security check may pause an account action until we confirm the registered phone detail, helping reduce the chance that another person uses your account.

Payment separation

For DANA, OVO, GoPay, QRIS and bank rails, our records may contain a status, amount and reference rather than your wallet login credentials. This separation lets us match a receipt while keeping your wallet password outside our account records.

Retention review

We keep account, support and transaction records for the period needed to operate the account, resolve disputes and meet applicable duties. When a record is no longer needed for those purposes, our retention process marks it for deletion or further restriction.

Change request

You can ask us to correct, access or clarify personal data through the account support path. We assess the request against identity checks and local requirements, then explain any restriction if a record must remain for security or legal reasons.

Privacy Policy Questions About com303

The answers below focus on the practical questions you may have before opening an account or using the lobby. They explain what com303 records during account access, how wallet references are treated, how cookies work on your device and how to send a request about your personal data. If your question involves eligibility, access depends on local law and the service is available where local law permits.

The com303 Privacy Policy covers registration details, phone verification, sign-in events, device signals, cookies, support records and payment references. It explains why we use each category, how we protect it, how long we retain it and how you can ask about access or correction.

No. When you use DANA or QRIS, we may receive a payment status, receipt detail or reference needed to match the transaction. Your wallet password and security code remain with the wallet provider, so do not send those credentials through the support path.

Yes, you can request details connected with your account through the support route shown in your account area. Include your registered phone detail so we can confirm your identity. We may limit some records where disclosure could affect security or another person.

Our Privacy Policy treats required session cookies as part of the login path from your mobile browser to the lobby. Optional browser settings may be changed on your device. Removing required cookies can interrupt account access, language memory or the return path to a selected title.

Send a correction request through the account support path and identify the detail that is wrong. We may confirm the registered phone route before making a change. This check protects your account when the requested correction could alter sign-in or payment matching.

We retain payment references, receipts and related account records for as long as needed for transaction matching, support, dispute handling and applicable legal duties. The period can vary by record type. You may ask us to explain the purpose and retention status of a specific record.

The policy can be read before account creation, but service access and certain data requests depend on local law. We apply the service where local law permits and may restrict an account action when Indonesian requirements or another applicable rule requires that result.