Reference

Privacy Policy for Your kilat128 Account

Our Privacy Policy explains how kilat128 handles the account details, wallet records and device data connected with your access.

Account dataWallet recordsCookie choicesContact requests
Explore Our Lobby Read FAQ
kilat128 Privacy Policy for Your kilat128 Account
CONTACT ROUTES

Get Help With Privacy Policy Requests

A clear contact path matters when you want to ask about your personal data rather than a wallet balance. Send a request through the account support route shown in our service, using the phone number or account detail needed to locate your record. We may ask for a matching account step before discussing private details. This keeps a receipt check, login issue or data request connected to the right account without exposing it to another person.

Team online

Account access

If you cannot reach your account, tell us which phone verification step stopped and the device path you used. We use that context to separate an access issue from a request about stored personal data.

Wallet records

For a DANA, OVO, GoPay or QRIS record question, include the payment reference and approximate date shown in your receipt. Do not send your wallet PIN or password; we only need enough detail to locate the relevant account event.

Privacy request

Ask us to explain, correct or remove eligible account data through the available support contact. We may verify your account first, then reply with the next step allowed under local law and this Privacy Policy.

HANDLING DETAILS

How We Apply This Privacy Policy

Our handling process follows the practical steps you see when using an account: phone verification before account access, a device session during login, and a payment reference when a wallet action is…

Account data

We may hold the details needed to create and maintain your account, such as your verified phone status and account activity. These details help us recognise your session and respond when you ask about account access or a stored record.

Payment references

DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity can create reference data. We use it to match a cashier event, check a receipt or investigate a status issue; wallet PINs are not requested through support.

Cookies

Cookies and similar device storage can keep your session working between login steps and remember necessary settings. You can manage browser controls, but blocking required cookies may interrupt the path from phone verification to the lobby.

Device security

We may record device and login signals that help identify unusual account access. If your device changes or a session looks unusual, we may request phone verification again before showing private account or wallet details.

Retention period

We keep account, support and payment-reference records only for as long as needed for service operations, security checks or legal duties. Where local law permits, you can ask which category applies to a particular record and why it remains stored.

Changes and contact

You can ask us to correct an inaccurate account detail, explain a data use or review an eligible deletion request. Submit the request through account support with enough detail to verify ownership, and we will assess it under this policy.

Privacy Policy Questions From Indonesia

These answers address the searches we hear most often about the kilat128 Privacy Policy. They cover account creation, wallet references, cookies, device checks and requests to access or change data. If your situation is not covered, use the privacy contact path with your verified account details so we can assess the request under local law.

It covers account details, phone verification, login and device signals, cookies, support messages and payment references linked to DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity. It also explains retention, security controls and how to request access, correction or eligible removal.

Phone verification helps connect account access to the person who opened the account and helps us protect private wallet or support details. We may request the same step again after a device change or unusual login before discussing account-specific records.

Yes. The Privacy Policy covers payment references created when you use DANA, OVO, GoPay, QRIS, bank transfer or a virtual account. We use those references to match a payment event and check status, not as a replacement for your wallet PIN or account password.

Use the available account support contact and state that you are making a Privacy Policy data request. Include your verified account detail and the record category you want to ask about. We may confirm account ownership before assessing the request where local law permits.

Yes, you can ask us to correct an inaccurate eligible account detail through the privacy contact path. Explain what appears wrong and what should replace it, then complete any ownership check we request. We assess the correction under this Privacy Policy and local requirements.

Retention depends on the record type and the operational, security or legal reason for keeping it. Payment references may be needed to resolve a receipt or status question, while login signals support account protection. Where local law permits, ask us about a specific category.

The policy is available for you to read, while account eligibility, data requests and some processing choices depend on local law. We apply the Indonesia-facing policy where local law permits and may ask for account verification before handling a private request.

Related Pages

kilat128 Indonesia Access guide ShopeePay Min Deposit FAQ Live Roulette Royal