Reference

Open Your lokal188 Privacy Policy

Our Privacy Policy explains how we handle the details you provide when opening a lokal188 account, signing in from a phone, or checking wallet status through DANA, OVO…

Clear data purposesWallet activity contextAccount access steps
lokal188 Open Your lokal188 Privacy Policy
HELP PATH

Contact Us About Privacy Questions

A clear support route matters when you want to know what we hold or why an account step requested it. Start from your signed-in account support area and include the phone number or email connected to your profile, plus the relevant wallet reference if your question concerns DANA, OVO, GoPay or QRIS. We use those details to locate the correct record without asking you to send a password. If you cannot sign in, use the account recovery route and explain that your request concerns the Privacy Policy.

Team online

Data request

Ask us to explain the account, device or wallet details linked to your profile. Include your registered contact detail so we can distinguish your request from another account and reply through the account support path.

Correction request

Tell us which profile detail needs changing and why it is inaccurate. For a phone verification issue, mention the failed account step; we may ask for additional confirmation before making a change.

Wallet question

For a DANA, OVO, GoPay, QRIS, bank transfer or virtual account record, share the transaction reference and date. Never include your password or full payment credentials in a support message.

DATA PRACTICE

Explore Our Privacy Handling Steps

We treat privacy as an account process rather than a distant statement. The controls below explain what we do with sign-in details, cookies, wallet references, device signals and requests to change your…

Account records

We use your registration details to create the profile, support phone verification and maintain sign-in continuity. If you open the lobby from a new device, related security signals may be checked before account access is allowed.

Wallet references

Payment records help us match a deposit or status question to the correct account. DANA, OVO, GoPay, QRIS, bank transfer and virtual account references are used for tracing and support, not as a reason to request your password.

Cookies

Browser storage and similar tools can remember session choices, keep the account path functioning and measure whether a page loads correctly. You can manage browser settings, although some sign-in functions may then require another verification step.

Device safety

We use device and connection information to spot unusual login patterns, protect account sessions and investigate access that you did not authorise. Keep your phone lock and account credentials private, and contact support if a session looks unfamiliar.

Retention

We keep records for as long as needed for the stated account, security, payment tracing and support purposes, subject to applicable requirements. When a record is no longer needed, our handling follows the retention process relevant to that record.

Your requests

You can ask what personal details we hold, request a correction, or raise a question about use and retention. Send the request through account support with enough detail to verify ownership; access depends on local law and identity checks may apply.

Find Privacy Policy Answers Before Login

These questions cover the points Indonesian customers usually want settled before they open an account or connect a local wallet. Each answer stays focused on the Privacy Policy, from phone verification and device data to cookies, payment references and requests for changes. If your situation is not listed, our account support route can assess the specific record without requiring your password.

It covers details connected with your account, phone verification, sign-in activity, device and connection signals, cookies, support messages, and payment references. It explains why we use those details, how we protect account access, how retention works, and how you can request clarification or correction.

Phone verification helps us connect the right person to the right account and reduce unauthorised access. If a verification step fails, contact account support and identify the affected profile without sending a password. Account eligibility and access depend on local law.

Yes. A wallet or QRIS reference can be used to match a payment status, receipt question or stalled transaction to your account. Bank transfer and virtual account references may be handled for the same tracing purpose, while full credentials should remain private.

We may use device and connection signals related to login security, session continuity and unusual activity checks. This can help when you switch between a mobile browser and desktop. The policy does not make unrelated device details necessary for ordinary account support.

Cookies and similar browser storage can remember a session, support account navigation and help us see whether pages load correctly. You can adjust cookie settings in your browser. Turning some tools off may end a session or require another sign-in verification step.

Use the signed-in account support route and state the exact detail that needs correction. Include your registered phone or email and any relevant reference, such as a wallet transaction date. We may verify ownership before changing records, where local law permits.

Retention depends on why the record exists, such as account operation, security, payment tracing or support. We keep it only as long as needed for that purpose and applicable requirements. You can ask support about a particular record and its handling.