Reference

Open Your Privacy Policy Path

kilat1000 Privacy Policy explains what we collect when you create an account, verify your phone, use DANA or QRIS, and move through the lobby.

Account dataWallet recordsCookie choicesDevice security
kilat1000 Open Your Privacy Policy Path
DATA HELP ROUTE

Reach Support When Data Questions Stall

A clear support route helps when your Privacy Policy question is tied to an account action. Start from the account support area and include the phone number linked to your profile, the affected device, and the relevant wallet status. We use those details to locate the right record without asking you to send a complete payment credential. Where local law permits, we can explain a collection purpose, access request, correction request or account closure step.

Team online

Account privacy request

Use the account support path to ask what personal records are linked to your profile. Include your registered phone number and request type, then we can match the request to the correct account before discussing any private details.

Wallet record question

If a DANA, OVO, GoPay or QRIS receipt appears with an unclear status, tell us the date, amount reference and wallet name. We check the payment record while keeping wallet credentials and authentication codes out of the support exchange.

Device access concern

For an unfamiliar login or a changed device, contact the same support route and identify the device path you used. We may ask for phone verification before discussing account data, helping keep a private request with the account owner.

HANDLING YOUR RECORDS

Check How kilat1000 Handles Your Data

Privacy work is part of each account step, from phone verification to a payment receipt and a return to the mobile lobby.

Account details

We collect details such as your phone number and account credentials to create, secure and maintain your profile. Phone verification helps us confirm that a request about your Privacy Policy records comes from the person connected with that account.

Payment references

A wallet name, bank transfer reference or virtual account record can be used to match a cashier event with your account. We do not need your DANA, OVO, GoPay or QRIS authentication code to check a receipt status.

Cookies and devices

Cookies can remember selected settings and help us understand whether a session belongs to the same device. Device signals also help flag unusual access when you switch from a mobile browser to desktop.

Security controls

We use login records, phone verification and account checks to reduce unauthorised access. If a request involves private account data, we may pause the response until the registered phone or another account step confirms your identity.

Retention choices

We retain account, payment and security records only for the operational or legal purpose that requires them. When a retention period ends, records are removed, anonymised or kept only where a legal obligation permits continued storage.

Requests and corrections

You can ask us to explain a data use, correct an inaccurate account detail, provide an available copy or close your profile. Send the request through account support, and we may verify your phone before making a change.

Find Privacy Policy Answers Before Access

These Privacy Policy answers focus on the account, payment and device questions you may search before opening access. We keep the wording practical: what we collect, why we use it, how long records stay available, and how you can contact us from Indonesia when local law applies.

The kilat1000 Privacy Policy covers account details, phone verification, login records, device signals, cookies, wallet references and payment records. It explains why we use each category, how security checks work, how retention is handled and how you can request access or correction.

We use your phone number to create and secure the account, complete phone verification before access, and match a privacy request to the correct profile. If you ask about DANA, OVO, GoPay or QRIS activity, verification helps prevent disclosure to another person.

Yes. The Privacy Policy covers payment references and status details connected with DANA, OVO, GoPay and QRIS, as well as bank transfer and virtual account steps. We use those records to match a receipt or investigate a pending status, not to collect wallet authentication codes.

We may collect device and browser signals, login timestamps and session details that help secure your account. These records can show whether access moved from a mobile browser to desktop or whether a sign-in looks unusual, while cookie choices remain part of your policy controls.

Use the account support path and state whether you want an access copy, a correction, an explanation of data use or account closure. Include your registered phone number and the detail concerned. We may complete phone verification before discussing or changing private records.

We keep personal data for the account, security or legal purpose that requires it, then remove or anonymise it when that purpose ends where permitted. Payment and access records may need a defined retention period, and support can explain the category involved.

Yes. You can contact us through the account support route with your registered phone number and question. Requests and account eligibility are handled where local law permits, and we will explain any verification step needed before sharing personal records or changing account data.