Reference

lgoking Legal For Your Account

lgoking Legal sets out how we handle account access, payment records, personal data and policy requests for customers in Indonesia.

Account termsData choicesLocal-law accessPolicy contact
lgoking lgoking Legal For Your Account
CONTACT ROUTES

Three Ways To Ask About Legal

A clear contact route matters when you need an answer about Legal, an account restriction or a payment record.

Policy questions Send the clause, page name or account step that concerns you through our support…
Payment records For a DANA, OVO, GoPay, QRIS, bank transfer or virtual account query, include the…
Account access If phone verification or a policy restriction stops access, contact us from the support…
DATA PRACTICES

How We Apply The Legal Policy

We apply this policy through specific account controls rather than broad promises. Phone verification connects access to the contact detail you provide, while payment references help us investigate…

Personal data

We use the account details you submit to manage access, answer policy questions and connect payment evidence to the correct…

Cookies

Cookies can help keep your session connected while you move from account access to a policy page.

Account security

Phone verification is part of our access process, and we may ask for matching account details before discussing a transaction…

Record retention

Transaction, access and support records are kept for the period described in the current Legal terms when they are needed…

Correction requests

If your name, phone detail or another account field is incorrect, contact support and describe the change clearly.

Policy changes

When Legal wording changes, we publish the updated version on the relevant policy page and identify the effective date where…

Answers About lgoking Legal

These Legal answers address the account and data questions we hear most often from Indonesian customers. They are written for practical use, but the current published terms remain the controlling text if a detail changes. If your situation involves a restricted location, an unmatched receipt or a request to change account data, contact us with the relevant reference and we will explain the available path where local law permits.

Legal covers account access, phone verification, local-law eligibility, payment records, data handling, cookies, account security, retention and policy changes. It also explains how to contact us when a transaction or account restriction needs clarification. Access depends on local law and is available only where local law permits.

You can open the Legal page from the site, but account eligibility depends on local law. Before opening an account, check that access is permitted in your location. If you are unsure, contact support with your location and question; we will explain the applicable route where local law permits.

Phone verification helps connect account access to the contact detail you provided and gives our team a way to confirm ownership during a policy or payment query. We may request matching account details before discussing records, and you should never share your password or wallet PIN.

We associate the payment reference and timing from DANA or QRIS with the relevant account record so support can check its status. For a question, send the receipt reference and approximate time. We confirm whether the record is matched, pending or requires another check.

Contact support with your registered phone number and describe the field that needs correction. We first verify that you control the account, then assess the request under the current Legal terms and local requirements. We will tell you whether the change can be made and what step follows.

The retention period depends on the purpose of the record and the current Legal terms. Payment, access and support records may be retained for account operation, dispute handling or a legal obligation. You can ask support which category applies to your request and what options exist.

Use the support chat shown on the site between 09:00 and 22:00 WIB. Include the policy page, clause or account event involved, along with a transaction reference when relevant. Do not include passwords, wallet PINs or one-time security codes in your message.