Reference

Open the olx123 Privacy Policy

olx123 Privacy Policy shows how we handle your account details, phone verification, device signals and payment references when you use the Indonesia site.

Clear data purposesPayment reference detailAccount access controlsCookie choices
olx123 Open the olx123 Privacy Policy
CONTACT ROUTES

Choose a privacy support path

A privacy question should reach a clear account route, not disappear inside a general message.

Account access Use the account support route when you need to ask which personal details are…
Payment references For DANA, GoPay, OVO, QRIS, bank transfer, or virtual account records, include the receipt…
Policy requests Ask about access, correction, retention, or deletion through the privacy contact route shown with…
DATA PRACTICES

Browse the safeguards behind Privacy Policy

Privacy choices work best when the account flow explains what happens at each step.

Account data

We use details such as your account identifier and verified phone status to connect you with the correct account record.

Device signals

A mobile browser may send session, device, and security-event signals when you sign in or move toward the lobby.

Cookie controls

Cookies and similar storage can keep a sign-in path, language choice, or security session working.

Wallet records

A DANA, OVO, GoPay, or QRIS reference can help match a requested payment status without giving us your wallet PIN.

Retention periods

We keep account, security, and transaction-linked records for the periods and purposes set out in the policy.

Change requests

You can ask us to correct inaccurate account details or explain how a record is used.

Find answers about Privacy Policy

These Privacy Policy questions reflect the account and payment situations you may meet while using olx123 from Indonesia. Each answer stays focused on your data, your access request, and the steps needed to contact us safely. Where local law permits, we will handle valid requests through the account privacy route.

It covers account details, phone verification, device and session signals, cookies, support messages, and payment references connected with DANA, OVO, GoPay, QRIS, bank transfer, or virtual account activity. It also explains purposes, retention, security checks, and available data requests.

Yes. The Privacy Policy explains why we may confirm your phone before account access, how that verification relates to your account record, and how security events can be reviewed. Do not send a password, wallet PIN, or full payment secret in a support message.

We may receive a reference, status, amount context, date, or receipt detail needed to match a requested transaction. DANA, OVO, GoPay, QRIS, bank transfer, and virtual account records are not treated as your wallet credentials, and we do not ask for your wallet PIN.

Where local law permits, you can ask what personal data is linked to your account through the privacy contact route. We may verify ownership first, then explain the available record, any processing limit, and the format or timing for the response.

Send a correction request through account support and identify the field that is inaccurate, such as a phone detail or account name. We may ask for a safe ownership check before changing it, and the Privacy Policy explains when a correction cannot be applied.

Retention depends on the record and the purpose described in the Privacy Policy. Account, security, support, and payment references may remain for dispute handling, fraud prevention, service records, or legal duties, even after a deletion request is made.

Where local law permits, you can ask whether a record may be deleted or restricted. We first verify the request and assess the record's purpose. Some account, security, payment, or dispute records may need to remain for stated legal or operational reasons.