Reference

Privacy Policy for Your lgoac Account

lgoac Privacy Policy explains how we collect, use and protect the account details you provide before entering the lobby.

Account detailsWallet recordsDevice accessPolicy requests
lgoac Privacy Policy for Your lgoac Account
CONTACT THE TEAM

Privacy Help Beside Your Account Path

A privacy question should have a clear route, especially when it concerns phone verification or a wallet reference. We ask you to contact us from the email or phone details connected with your account so we can confirm the request belongs to you. Our team can explain a data record, correct an account detail or check why a payment receipt is attached to a status. If you are in Surabaya or elsewhere in Indonesia, the same contact path applies where local law permits.

Team online

Account message

Send a message through the account contact path when your request concerns phone verification, login history or a detail shown on your profile. Include the relevant date and reference, but do not send your password or wallet PIN. We use the account record to locate the request.

Payment receipt

For DANA, OVO, GoPay, QRIS, bank transfer or virtual account questions, attach the payment receipt number and the account phone number. We use those details to check status and explain which transaction record we hold, without asking for your private wallet credentials.

Access request

Ask us to correct, explain or remove eligible personal data through the same account contact route. We may request an account check before making a change, because changing phone or payment records without verification could affect your access and transaction history.

DATA CARE DETAILS

What Our Privacy Policy Covers

We separate the data needed for account access from records used to understand payment status and site performance. Our Privacy Policy also explains cookies, security checks and the period for keeping records.

Account security

Phone verification connects your account access with a contact route we can check. Login time, device type and related security signals may be used to investigate an access issue. We do not treat a device signal as permission to read private files stored on your phone.

Cookies

Cookies can keep your session active and help us understand whether a page loads correctly on mobile or desktop. You can manage browser settings, although removing necessary cookies may interrupt login, policy access or the path from account entry to the lobby.

Payment records

DANA, OVO, GoPay and QRIS can return a payment reference and status to us. Bank transfer and virtual account activity can also create reconciliation records. We use these details to match a transaction, answer a receipt question and detect account misuse.

Data retention

We keep personal and transaction records only for the period needed for account operation, security checks, dispute handling and legal duties. When a record no longer serves one of those purposes, our retention process can remove it or separate it from direct account identifiers.

Correction requests

If your name, phone detail or account contact record is wrong, tell us which field needs correction and why. We may compare the request with your verified account details before changing it, then confirm the outcome through the contact route already attached to your account.

Policy contact

Use our account message route for questions about collection, cookies, device data, payment references or deletion. Please include a useful date or reference and keep passwords, one-time codes and wallet PINs out of the message. We reply with the next required step.

Privacy Policy Answers For lgoac

These Privacy Policy answers address the account and payment questions we expect from Indonesian customers before access begins. They explain what we collect, how requests are checked and which details help us investigate a wallet or device issue. If your situation is not covered, contact us through the account message route and mention whether your question concerns DANA, OVO, GoPay, QRIS or another record.

It covers account details, phone verification, login and device signals, cookies, payment references, support requests and retention. It also explains how we use those records for access, security, transaction matching and legal duties. Where access or eligibility is discussed, it depends on local law.

We may collect the phone number and account details you submit, verification results, login events, device information and messages sent to support. When you use DANA, OVO, GoPay or QRIS, we may receive a transaction reference and status needed to match activity to your account.

No. Our payment records are used to identify a transaction reference and status, not to request your private wallet PIN. Do not include a PIN, password or one-time code in a support message. We may ask for a receipt number to investigate a payment question.

Send an account message stating the field that is incorrect, such as your phone detail, and describe the requested correction. We may verify you through the contact route connected with the account before making a change. We then confirm whether the correction was completed.

Device signals help us identify unusual login activity and troubleshoot access on mobile or desktop. Necessary cookies can keep a session active and help pages load correctly. Browser cookie controls remain available, but removing necessary cookies may interrupt account entry or policy access.

We keep records for the period needed to operate and secure an account, reconcile payment activity, handle disputes and meet legal duties. The period can differ by record type. When a record is no longer needed, our process removes it or separates it from direct identifiers.

You can contact us through the account message route and request removal of eligible personal data. We first confirm the request and check whether a security, dispute or legal duty requires some records to remain. We will explain the result and any next step where local law permits.