Reference

Privacy Policy For Your Account

Our Privacy Policy explains how kupu 178 handles the details connected with your account, from the phone verification step to wallet records for DANA, OVO, GoPay and QRIS.

Account dataWallet recordsDevice accessCookie choices
kupu 178 Privacy Policy For Your Account
CONTACT PATHS

Where Privacy Questions Go

A clear contact route helps you act when an account record, wallet reference, or device entry needs attention. Open the support path shown beside the cashier area and describe the issue without sending your password or full payment credentials. We use the details you provide there to locate the relevant account event, while the Privacy Policy sets out what we may check and what you can ask us to change.

Team online

Account access

If your phone verification or login record looks wrong, use the account support path beside the cashier. Tell us the account contact detail and approximate access time so we can locate the event without asking for your password.

Wallet record

For DANA, OVO, GoPay, QRIS, bank transfer, or virtual account questions, send the payment reference and status shown in your account. Remove secret wallet credentials from any message; we only need enough detail to match the record.

Privacy request

To ask for access, correction, or removal of eligible personal data, use the same support contact and write Privacy Policy request in your message. We may verify account ownership before changing records connected with your account.

HANDLING DETAILS

Six Ways We Handle Your Data

Our approach is practical: collect only what helps us run an account, match a wallet event, protect access, or answer a privacy request.

Account creation

When you open an account, we record the contact details and verification result needed to connect you with your account. A clear phone verification step helps us distinguish an authorised access attempt from an unfamiliar one.

Payment matching

A DANA, OVO, GoPay, or QRIS transaction may create a reference, amount, time, and status record. Bank transfer and virtual account entries are handled in the same matching process so support can trace a stalled cashier event.

Device signals

When you move from login to the lobby on a phone or desktop, we may record device type, browser details, access time, and security signals. These details help us recognise unusual access without reading unrelated content on your device.

Cookie choices

Cookies and similar storage can remember a session, keep account pages working, and help us understand which policy page was opened. You can manage cookie settings through your browser, though some account functions may then need another login.

Retention period

We keep account, payment, support, and security records only for the period needed for the stated purpose, account administration, dispute checks, or a legal obligation. When a record is no longer needed, our processes remove or separate it.

Change requests

You can ask us to access, correct, or remove eligible personal data through the account contact path. We may request account verification first, then explain any data we cannot change because a legal, payment, or security record must remain.

Privacy Policy Questions Answered

These questions focus on the records you are most likely to notice while using your account in Indonesia. Each answer connects directly with the Privacy Policy, from wallet references and cookies to account access and requests for data changes.

The Privacy Policy covers account details, phone verification, wallet and payment references, device signals, cookies, support messages, security records, retention, and requests to access or correct data. It applies when you use the account pages and related access points where local law permits.

We record the rail, reference, amount, time, and status needed to match your account activity. This lets us investigate a DANA or QRIS payment that remains pending without requesting your wallet password or unrelated personal details.

Yes. The Privacy Policy explains that a mobile or desktop session may create device, browser, access-time, and security-signal records. These details help us check unusual login activity; we do not use them to read unrelated files or content on your device.

Use the account contact path shown beside the cashier and state that you are making a Privacy Policy request. Include the account contact detail and the record concerned. We may verify ownership before providing eligible data or correcting an account field.

We retain account, payment, support, and security records for as long as needed for their stated purpose, account administration, dispute checks, or a legal obligation. After that period, our processes remove the record or separate it from direct account identifiers.

You can manage cookies through your browser settings. Cookies may keep a session active, remember a page choice, or support account functions. If you block them, you may need to log in again and some account pages may not work as intended.

Use the support route beside the cashier and describe the unfamiliar login, wallet reference, or device entry with its approximate time. Do not send a password or full wallet credentials. We may verify account ownership before discussing or changing the record.