Reference

Read the ledak 138 Privacy Policy

Our Privacy Policy explains what we collect when you open an account, sign in from a phone, or use DANA, OVO, GoPay and QRIS.

Account dataWallet recordsCookie choicesAccess requests
ledak 138 Read the ledak 138 Privacy Policy
CONTACT YOUR WAY

Find the privacy support path

A clear contact route helps when your Privacy Policy question involves a phone number, wallet reference or account record.

Account request Use the support path inside your account to ask for a copy, correction or deletion of eligible personal data. Include the email or phone detail linked to your account so we can locate the right record.
Wallet question For DANA, OVO, GoPay or QRIS records, share the transaction reference and date, not your wallet PIN. We use those details to check the account match while keeping payment credentials outside our support process.
Access concern If a new phone or browser changes your login status, contact support through the account route and explain the device path. We may ask for verification before discussing stored data or changing account details.
HOW WE HANDLE DATA

Explore our privacy handling steps

Privacy work is part of each account action, from the first phone verification to a later request about stored records.

Account collection

When you open an account, we record the details needed for login, phone verification and account support. We do not ask for more personal detail than the account step or a specific service request requires.

Payment references

A DANA, OVO, GoPay or QRIS transaction can create a reference, amount, status and timestamp in our records. These details help match a wallet event without requiring your wallet password or personal wallet PIN.

Cookie controls

Cookies and similar browser signals help remember a session, support account access and identify unusual sign-in behaviour. You can manage available cookie choices through your browser path, although some account functions may then need to reload.

Device security

We may record device type, browser details and sign-in timing to protect your account. If access changes after moving from mobile to desktop, verification helps us check the request before sharing or editing account data.

Retention period

We keep personal and transaction records only as long as needed for account operation, security checks, dispute handling or legal duties. When a record no longer serves one of those purposes, our handling process moves it toward removal.

Change requests

To request access, correction or removal, use the support route connected with your account and identify the record clearly. We verify the request, explain any limit that applies, and respond through the available account contact path.

Browse Privacy Policy answers

These Privacy Policy answers address the searches we hear most often from Indonesian account holders. They cover wallet records, cookies, phone verification, device access, retention and requests to change stored details. If your case is unusual, use the support path connected with your account and include only the details needed to identify the question.

It covers account details, phone verification, sign-in and device records, cookies, payment references, retention and requests to access, correct or remove eligible personal data.

We use phone verification to create and protect your account, confirm sensitive changes and reduce mistaken access. The verification status can also help support locate the correct account record.

Yes. The Privacy Policy covers payment references such as status, timestamp and transaction identifiers from DANA, QRIS, OVO, GoPay, bank transfer and virtual account steps.

You can request a correction through the support route connected with your account. Tell us which detail is wrong, and we may verify your identity before changing the stored record.

Cookies can remember a session, support account access and help identify unusual browser activity. Your browser provides cookie controls, but changing them may require another sign-in or affect some account functions.

We retain records for account operation, security checks, dispute handling or legal duties. The period depends on the record and its purpose; records no longer needed move toward removal.

Yes, where local law permits. Use the account support path, describe the records you want, and complete any verification needed to protect your account before we process the request.