Reference

Privacy Policy for olx 168 Accounts

olx 168 explains how we collect, use and protect the details connected with your account, including phone verification, device access and wallet records.

Clear data choicesWallet record contextAccount access checksPolicy contact path
olx 168 Privacy Policy for olx 168 Accounts
CONTACT YOUR WAY

Get Privacy Help Near Account Access

A clear contact route matters when you want to understand a record or change an account detail. We keep privacy questions separate from game or wallet instructions so your request can be handled with the right context. Include the phone number or account identifier connected with your request, but never include your password or full payment credentials. From Medan or elsewhere in Indonesia, use the account support path and tell us whether your question concerns access, cookies, a wallet reference or a data correction.

Team online

Account privacy request

Use the support path connected with your account when you want to ask what personal details we hold. State your account identifier and the request type, such as access, correction or removal, so we can check the right record without asking for your password.

Wallet record question

If a DANA, OVO, GoPay or QRIS reference appears in your account history, send the date, amount reference and wallet name through support. We use those details to locate the record while avoiding requests for your full wallet PIN, card number or login secret.

Access and device concern

Tell us if your account appears on an unfamiliar phone, browser or session. We can review the access context and explain the next account step. Keep your phone verification details private; our support path does not require your password to begin a privacy request.

DATA HANDLING

What We Do With Your Account Data

Privacy is part of the account flow, not a separate promise shown after a payment issue.

Account details

We use the details you provide during account creation to identify the account, complete phone verification and keep access connected to you. A clear account path reduces confusion when you return from a mobile browser, while the Privacy Policy explains the purpose of each required detail.

Device signals

Your browser and device may provide technical signals such as session data, language and access timing. We use these signals to maintain a login session and spot unusual access around the account. They help us investigate a security question without reading private content on your device.

Cookies

Cookies can keep a page session available, remember selected settings and help us understand whether an account page loads correctly. Your browser controls cookie storage. Removing cookies may require you to complete phone verification again, but it does not itself erase account records held for security or legal needs.

Payment references

We record practical payment references rather than asking support to handle your private wallet credentials. DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity may be linked to an account status so we can match a receipt or explain a pending record.

Security controls

Phone verification is required before account access, and session checks help us respond when a device pattern changes. Do not share a password or verification code. If you suspect someone used your account, contact support with the account identifier and the device concern as soon as possible.

Retention and changes

We retain information only while it serves account operation, security, dispute handling or a legal requirement. You may ask us to explain, correct or remove eligible data through support. Some records may remain when they are needed to resolve a payment question or meet a legal duty.

Answers About Privacy Policy Access

These Privacy Policy answers address the questions we expect before an Indonesian customer opens an account. They focus on the records, devices, wallets and contact steps that matter in daily use. If your situation is not covered, send a specific request through the account support path and include only the details needed to locate your record. Access depends on local law.

The olx 168 Privacy Policy covers account details, phone verification, device and browser signals, cookies, support messages and payment references. It explains why we use each category, how we protect access and how you can request access, correction or removal where local law permits.

Yes. The Privacy Policy covers references linked with DANA, QRIS, OVO, GoPay, bank transfer and virtual account activity. We use those references to match account status, check a receipt or investigate a payment question. We do not ask you to send a wallet PIN or password.

Phone verification helps connect account access with the person who created the account and adds a check when you return from a mobile browser. The Privacy Policy explains this use. Keep verification codes private, and contact support if an unfamiliar device reaches your account.

You can request access to eligible personal data through the account support path. Include your account identifier and describe the records you want, such as profile details, device history or wallet references. We may need to verify the request before explaining or providing the relevant data.

Send a correction request through support with the account identifier, the field that is wrong and the accurate replacement. Do not include your password or full wallet credentials. We review the request against the account record and explain any verification step needed before changing it.

You may ask for removal of eligible data through the account support path. Some records can remain when needed for account security, payment dispute handling or a legal duty. Our response will identify the applicable reason, and access or eligibility depends on local law.

Ask through support if you want details about cookies connected with your account session. Your browser also lets you remove or restrict cookies. After removal, you may need to complete phone verification again, while records retained for security or legal duties remain separate.