Reference

Privacy Policy for Your lokasi88 Account

Our Privacy Policy explains how lokasi88 collects, uses and protects the account details connected to your access, including phone verification and payment status for DANA, OVO, GoPay and…

Clear data purposesWallet status detailAccount access rightsPhone verification context
lokasi88 Privacy Policy for Your lokasi88 Account
CONTACT PATHS

Privacy Help for Login and Wallet Questions

A clear contact path helps you act when a Privacy Policy question affects your account. Tell us which account step is involved, such as phone verification, a DANA status check or a QRIS payment reference, and we can direct the request to the right handling process. For access from Makassar or elsewhere in Indonesia, include the device type and approximate time of the event. We use only the details needed to identify the request and avoid asking you to send a full password.

Team online

Account access request

If you cannot reach your account after phone verification, contact us with your registered phone detail and device path, such as mobile browser or desktop browser. We use that context to confirm the request without asking for your password or unrelated personal details.

Wallet data question

For a DANA, OVO, GoPay or QRIS privacy question, send the payment reference and the status shown in your account. We use the reference to trace the relevant record, while the wallet provider remains responsible for data it handles in its own service.

Correction request

If an account detail is inaccurate, tell us which field needs correction and why. We may ask for an account confirmation step before changing it, so the request protects your account rather than exposing its details to another person.

DATA HANDLING

Inside lokasi88 Privacy Controls

We organise this Privacy Policy around the moments that create useful account records: access, verification, payment matching, security checks and support requests.

Account records

We handle details such as your registered phone contact, account settings, login events and verification result to create and protect your access. These records help us separate your account from another account when you ask for a change or account recovery.

Payment matching

Payment references help us match a DANA, OVO, GoPay, QRIS, bank transfer or virtual account event to the correct account. We do not need your wallet password for this matching process, and a provider may handle additional data under its own policy.

Cookies and sessions

Cookies and similar session tools can remember your login state, preserve security checks and support the correct page flow. Browser settings may remove them, but doing so can require you to repeat phone verification or sign in again on the device.

Security signals

We may use device type, browser details, login time and session activity to identify an unusual access pattern. These signals support account protection for mobile and desktop paths; they are not a request for access to unrelated files, photos or messages.

Retention periods

We keep account, payment and support records for as long as needed for the stated service purpose, security checks or applicable legal duties. When a record no longer has a valid purpose, our handling process moves it toward deletion or de-identification.

Your request route

You can ask what personal data we hold, request a correction, ask about deletion where applicable or question a processing purpose. We may confirm your account first, then explain any lawful reason a record must remain available.

Privacy Policy Answers for Indonesia

These Privacy Policy answers focus on the account, device and wallet questions you are most likely to ask before opening access. We keep the wording tied to actual steps, including phone verification, QRIS references and browser sessions. If your question concerns a record not covered here, contact us with the smallest useful detail and we will explain the applicable handling path where local law permits.

The lokasi88 Privacy Policy covers account details, phone verification, login and device signals, cookies, support requests and payment references. It explains why we use each category, how it supports account access or security, how long records may remain, and how you can ask about your personal data.

Yes. The Privacy Policy explains how we use payment references and status details from DANA, OVO, GoPay and QRIS to match an account event. Each wallet provider may collect additional data under its own policy, so you should also check the provider terms for its separate handling.

Phone verification can create a registered contact detail, a verification result, a time record and security-related session data. We use those details to confirm account access and investigate login problems. We do not ask you to send your password when you request ordinary privacy assistance.

Yes. You can request a correction by identifying the account field that appears wrong, such as a contact detail or account setting. We may complete an account confirmation step before changing it. That check helps prevent another person from altering your account information.

Cookies and session tools can keep a mobile browser connected to the correct account flow, preserve security checks and remember whether a verification step has been completed. If you clear or block them, you may need to sign in again or repeat phone verification.

We retain account, payment and support records while they have an operational, security or legal purpose described by the Privacy Policy. The period can differ by record type. When no valid purpose remains, we move the record toward deletion or de-identification where local law permits.

Contact us with your registered account detail and state that you want a personal data access request. We may verify that you control the account before responding. Include a DANA or QRIS reference only if it helps identify the specific payment record you want us to address.