Reference

Privacy Policy for your kl108 account

Your account details, cookie choices, and DANA or QRIS payment records are handled under the kl108 Privacy Policy, with clear routes for access and correction.

Account dataCookie choicesWallet recordsAccess requests
kl108 Privacy Policy for your kl108 account
CONTACT PATHS

Where to ask about your account data

A clear contact route helps when a Privacy Policy request concerns a login, wallet reference, or receipt. Open the support path beside the cashier area and include the account contact detail you used, the relevant date, and the request you want us to process. We use those details to locate the correct record without asking you to send a full password or wallet PIN.

Team online

Account data request

Use the account support route to ask for a copy, correction, or deletion of personal details. We first match your request with the account contact detail before making changes.

Wallet record question

For DANA, OVO, GoPay, QRIS, or bank transfer records, include the payment reference and date. We use that narrow detail to check the correct transaction history.

Access concern

If an unfamiliar device reaches your account, contact us through the support path beside the cashier. We can review login events and guide the next security step.

HANDLING IN PRACTICE

Six ways we handle policy choices

Privacy work is part of each account step, from the first phone check to a later request about stored data.

Collection at account opening

We collect the contact and verification details needed to create your account and confirm access. You can ask which fields are held by using the account support route.

Cookies and browser storage

Cookies can keep a session active, remember selected settings, and help us detect unusual access. Your browser controls can clear or restrict them, though some account steps may then need repeating.

Payment references

A DANA, OVO, GoPay, QRIS, bank transfer, or virtual account reference may appear in account records. We use it to reconcile status, receipts, disputes, and requested account checks.

Account security

We record login time, device type, and selected security events to help identify access that does not match your account pattern. Never send us your password or wallet PIN.

Retention decisions

We retain records for operational, dispute, security, or legal needs, then remove or anonymise them through our retention process. A request may not erase records still required for those purposes.

Changes and questions

To request a correction, copy, or deletion, contact support with your account detail and a precise request. We may ask for a limited identity check before changing stored records.

Privacy Policy answers before account access

These Privacy Policy answers address the searches we hear most often before an Indonesian account is opened or checked. They explain the practical route for data requests, cookies, payment references, device records, and access questions, while keeping every answer tied to the account details we actually handle.

It covers account details, verification responses, login and device events, cookies, support messages, payment references, and records linked to account activity. It also explains retention, security, and requests for changes.

We use your contact detail to create the account, complete the phone verification step before access, send account-related responses, and match a Privacy Policy request with the correct stored record.

Yes. DANA, OVO, GoPay, QRIS, bank transfer, and virtual account references may be stored for status checks, receipts, disputes, account security, and responses to a specific data request.

Use the support route beside the cashier and state whether you want a copy or correction. Include your account contact detail and the relevant record date; we may complete a limited identity check.

You can request deletion through support. We assess the request under the Privacy Policy, but some records may remain where they are needed for security, disputes, operations, or legal requirements.

Cookies can keep your login session, remember settings, and help detect unusual access. You can manage them in your browser, but restricting them may require repeated login or account-setting steps.

The policy is available for account questions, while access to kl108 and related processing depends on local law. Contact support if your location or account status creates a specific access question.