Reference

Privacy Policy for Your kilat188 Account

kilat188 Privacy Policy explains how we handle the account details, wallet records and device data connected with your access to Auto Roulette, mantul77 and other lobby areas.

Account dataWallet recordsDevice accessCookie choices
kilat188 Privacy Policy for Your kilat188 Account
CONTACT PATHS

Get Privacy Help Near Account Support

A clear contact path helps when a privacy request and an account question arrive together. Start from the support route shown inside your kilat188 account and state whether you need access, correction, deletion or an explanation of wallet data. Include the relevant payment rail, such as QRIS or DANA, only when it helps us locate the record. We may ask for account details to confirm that the request comes from you.

Team online

Account privacy request

Use the support path available from your account and describe the Privacy Policy request in plain English. We may ask for your registered phone detail or another account step before discussing personal data, so your records are not disclosed to the wrong person.

Wallet record question

If a DANA, OVO, GoPay or QRIS reference appears unfamiliar, send the receipt reference through the account support route. We compare it with the account record and explain what data is held, while avoiding a request for your wallet password or full security code.

Access and correction

For a copy, correction or removal request, tell us which account detail or device record is affected. We check identity first, then explain any data that must remain for payment reconciliation, security checks or legal duties where local law permits.

DATA PRACTICES

What We Do With Your Personal Data

Privacy becomes easier to judge when each data use has a clear account purpose. We connect phone verification, login events and wallet references only as needed for account access, payment matching and…

Account details

We handle the details you provide during account creation and phone verification to establish the account path. These details help us recognise your request when you ask about access, correction or a Privacy Policy matter, rather than treating an unknown message as an account instruction.

Payment matching

A DANA, OVO, GoPay, QRIS, bank transfer or virtual account reference can be linked to your account record so payment status can be checked. We use the reference for reconciliation and support, not as a reason to request your wallet password or private security code.

Device security

We may keep device, browser, IP and login-event details to identify unusual account access. This matters when you move from a phone to desktop or when a new session follows a phone verification step. These records support account protection and privacy-request checks.

Cookie choices

Cookies can preserve a session and help the account path work when you move between the login page and lobby. Browser controls can limit some cookies, although changing them may affect access. Our Privacy Policy explains the purpose of these records without treating them as wallet credentials.

Retention period

We retain personal and payment-related records only for the period connected with account security, reconciliation, support handling or legal duties. When a deletion request cannot remove a record immediately, we explain the reason and identify the category that must remain.

Request changes

You can ask us to access, correct or remove eligible data through the support route shown in your account. Tell us the exact record, such as a phone detail or QRIS receipt reference, so we can check the request accurately and reply with the next step.

Privacy Policy Answers For Indonesian Accounts

These Privacy Policy answers focus on the account questions you are most likely to ask before using the kilat188 access path. They cover wallet records, mobile sessions, cookies, account requests and local eligibility. If your case does not fit a question below, use the support route shown in your account and include enough detail for us to locate the correct record.

It covers account details, phone verification, login events, device records, cookies and payment references connected with your access. That includes DANA, OVO, GoPay, QRIS, bank transfer and virtual account records when they are used to match an account transaction or answer a support request.

We use phone verification as an account access step and to help confirm that a privacy request comes from the account holder. The detail can also help us identify the correct account when you ask about a login event, wallet reference or correction.

Yes. The Privacy Policy covers payment references and status records connected with DANA and QRIS, as well as OVO, GoPay, bank transfer and virtual account use. We use those references for reconciliation and support, while your wallet password remains yours.

Open the support route shown inside your account and ask for an access copy under the Privacy Policy. Identify the account detail you need, such as your phone record, login history or QRIS reference. We may verify your account before releasing personal data.

You can request a correction through the account support path. State which detail is wrong and provide the updated value or a clear explanation. We check the request against your account step and payment records, then tell you whether the change can be made.

Cookies may keep a mobile session available while you move between login and the lobby, and they can record preferences used by the account path. You can manage some choices in your browser. Limiting cookies may require another login or affect parts of access.

Ask through the support route shown in your account and specify the data you want removed. We assess the request under the Privacy Policy. Some security, payment reconciliation or legal records may need to remain where local law permits, and we explain that outcome.