Reference

Open lpg888 Privacy Policy With Clarity

lpg888 Privacy Policy explains what we collect when you open an account, verify your phone, browse on mobile or desktop, and use DANA, OVO, GoPay or QRIS.

Account dataWallet recordsCookie choicesPrivacy requests
lpg888 Open lpg888 Privacy Policy With Clarity
ASK OUR TEAM

Switch To A Clear Privacy Contact

A privacy question should not require you to search through unrelated account screens. We keep a direct route for questions about collection, cookie choices, wallet references and account access, while the account help path can identify the right request when login details or a payment receipt are involved. Send enough detail for us to locate your account, but never include a wallet password or full authentication code.

Team online

Privacy request route

Use the privacy contact path to ask what personal data we hold, why it is used, or how to request a correction. Include your account identifier so we can check the right record without asking for your DANA, OVO, GoPay or QRIS password.

Account help path

If you cannot reach your account on a mobile browser or desktop browser, begin with account help and state that the question concerns privacy. We use the login event and phone verification status to route the request without requesting your secret login code.

Receipt data check

For a wallet or bank transfer question, attach only the relevant reference, date and status shown in your account. Our team can compare that record with DANA, OVO, GoPay, QRIS, BCA, BRI, Mandiri or BNI details while keeping unrelated account data out of the request.

DATA HANDLING

Browse The Controls Behind Our Policy

Privacy is part of the account path rather than a separate promise placed away from the login screen.

Account details

We use the details you submit during account opening and phone verification to create the account record, confirm account ownership and respond to requests. If a field changes, ask us to correct it through the privacy route rather than sending replacement details in an open message.

Device signals

A mobile browser or desktop browser can send device and login signals such as session timing, browser type and security events. We use these signals to detect unusual access and investigate an account question; they are not treated as a request for your private wallet credentials.

Cookies

Cookies help keep a signed-in session working, remember selected settings and show whether a page request completed. You can manage cookie settings in your browser, although turning some cookies off may affect the path from phone verification to your account area.

Wallet records

For DANA, OVO, GoPay and QRIS, we record references, amounts supplied by the transaction flow and status results needed for account history. Bank transfer and virtual account records follow the same purpose. We do not ask you to disclose a wallet password in a support request.

Retention steps

We keep account, security and transaction records only for as long as needed for the stated account, dispute, security or legal purpose. When a record is no longer needed, our retention process removes it or separates it from direct account identification where that is suitable.

Change requests

You can ask what personal data is held, request a correction, raise a concern about use, or ask about removal where applicable. We may verify your account through the registered phone path before making a change, so another person cannot alter your lpg888 record.

Check Privacy Policy Answers Before Opening

These questions cover the privacy points most often raised before account opening: what we collect, how wallet references are used, what happens on different devices, and how to contact us. If your situation is not listed, use the privacy request route and describe the account step or record you want us to check.

It covers account details, phone verification, login and device signals, cookies, support messages, and transaction references from DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity. It also explains retention, security checks and the way you can request access or correction.

Phone verification helps us create the right account record, confirm that an account request comes from its stated owner and protect access when a login event looks unusual. We use the verification status for those account purposes and do not need your wallet password.

Yes. The Privacy Policy covers the reference and status connected with DANA, OVO, GoPay and QRIS activity, plus bank transfer and virtual account history. These records help match a wallet action to your account without requiring us to store a wallet password.

You can contact us through the privacy request route to ask what personal data is held or to request a correction. Include your account identifier and the field you mean. We may confirm ownership through your registered phone path before discussing private records.

Cookies can keep your session active, remember settings and show whether an account page completed. Your browser controls whether cookies are accepted. If you disable a required cookie, the path from login or phone verification to the account area may not work as intended.

We retain account, security and transaction records for the period needed for the account purpose, a dispute, security work or a legal requirement. After that need ends, our process removes the record or separates it from direct identification where suitable.

The policy is written for supported Indonesia access routes, but availability and eligibility depends on local law. If you are unsure whether an account path is available in your location, contact us before opening an account and ask us to check the applicable route.