Reference

kilat289 Privacy Policy and Your Account

kilat289 Privacy Policy explains what we collect when you create an account, verify your phone, use a mobile browser, or select DANA, OVO, GoPay and QRIS.

Account clarityWallet recordsCookie choicesPhone verification
kilat289 kilat289 Privacy Policy and Your Account
ACCOUNT HELP ROUTE

Where To Ask About Privacy Policy

A clear support path helps you act on the Privacy Policy without guessing which team handles a request. Start from the account-help route beside the cashier path and include the phone number linked to your account, the relevant date and the payment rail involved. We use those details to locate the right record while limiting unnecessary disclosure.

Team online

Access request

Ask our account-help team to confirm which account details are held about you. Include your registered phone number and a recent account step so we can check identity before replying.

Wallet record

For a DANA, OVO, GoPay or QRIS privacy question, mention the cashier reference and date. We can distinguish a wallet status record from general account activity before handling your request.

Correction path

If your phone, device or account details need correction, use the support path shown near the cashier. We may request phone verification before changing information connected to account access.

DATA HANDLING

How We Keep Policy Requests Clear

Privacy work is tied to practical account events rather than broad statements. We separate login, wallet and device records, use cookies to maintain a session, and check phone verification before account access.

Collected data

We may hold your phone number, account identifiers, verification result, payment reference, browser details and security events. The Privacy Policy links each category to an account, session or cashier action.

Cookie use

Cookies help keep your signed-in session and remember necessary browser settings. On a mobile browser, they support the path from phone verification to the lobby without creating a separate account record.

Account security

Phone verification is checked before account access, while device and session events help us spot unusual sign-in activity. We use these checks to protect account records, not to create unrelated profiles.

Retention period

We retain account, wallet and security records only as long as needed for the stated account purpose, a requested status check or a legal obligation. Requests can ask us to explain the applicable period.

Changing details

You can request correction of inaccurate phone, account or device details through our support route. We first compare the request with the account record and may repeat phone verification.

Contacting us

For a Privacy Policy request, provide your registered phone number, request type and relevant date through the account-help path. Avoid sending wallet passwords or unrelated personal details.

Privacy Policy Answers For Indonesia

These Privacy Policy answers address the searches we expect before account access: what data is collected, why wallet records appear, how cookies work and how you can request a change. If a situation is not covered here, use the account-help route with the smallest useful set of details.

It covers account details, phone verification, device and browser data, cookies, security events, payment references and requests to access or correct records connected with your account.

We record the selected rail, reference and status so a cashier event can be matched to your account and checked if a DANA or QRIS transaction needs clarification.

Yes. The Privacy Policy covers OVO and GoPay status records, references and timestamps created through the cashier, along with the account details needed to investigate that specific event.

Use the account-help path and state that you want an access request. Add your registered phone number and a recent account date so we can verify the correct account.

Yes. Request a correction for an inaccurate phone, account or device detail through support. We may ask you to complete phone verification before changing a protected record.

Cookies maintain necessary sessions and browser settings, including the mobile path from login to the lobby. If cookies are blocked, some account steps may not remain connected.

Yes. Access and eligibility depend on local law. Where local law permits, we apply the Privacy Policy and use location or account checks needed for the requested service.