Reference

Privacy Policy for Your Indonesia Account

Our liga2000gogo Privacy Policy shows what happens to your account details, phone verification data and DANA, OVO, GoPay or QRIS payment records from the first account step onward.

Clear data categoriesWallet activity contextDirect privacy contact
liga2000gogo Privacy Policy for Your Indonesia Account
CONTACT PATHS

Privacy Questions Near Your Account

A clear contact route helps when a privacy request is tied to a login, wallet receipt or phone verification step. Start with the support form shown through your account path and describe the exact record you want us to check. We may ask for account details to confirm identity, but never request your DANA, OVO, GoPay or QRIS PIN. If you are in Bandung or Medan, the same privacy contact process applies, subject to local law.

Team online

Account data request

Use the account support form to ask what profile, login or verification data is connected with your account. Include the phone number used for access so we can locate the correct record without asking for your wallet PIN or one-time code.

Wallet record question

If a DANA, OVO, GoPay or QRIS receipt appears in your account history, send its reference through the support route. We can check the payment status and explain which details came from the wallet rail and which came from our account system.

Change request

Ask us to correct an outdated phone detail or clarify a retention request through the same contact path. We first confirm that you control the account, then explain what can be changed, restricted or kept under applicable local requirements.

DATA PRACTICE

How liga2000gogo Handles Account Data

We keep this policy practical by connecting each data category with a real account action. Phone verification supports account access, device records help us investigate unusual login activity, and payment references let…

Data we receive

We may receive your account name, phone number, verification result, login timestamps, device or browser details, support messages and payment references. These details help us connect one account step with the correct access request without collecting a wallet PIN.

Cookies and devices

Cookies can remember a session choice and help the account path load correctly on mobile or desktop. Device and browser signals may also be recorded when you log in, helping us examine access problems or activity that does not match your usual sign-in pattern.

Account security

Phone verification is part of the account access path, while login records can support checks after an unusual sign-in. Keep your password, wallet PIN and one-time code private; our support route should not require you to disclose those secrets.

Payment references

For DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity, we use the reference and status needed to connect a receipt with your account. The payment rail may separately process its own details under its own privacy terms.

Retention choices

We keep account, security and payment records for as long as needed for the stated purpose, account support and applicable local requirements. When you ask about removal or restriction, we explain which records can be changed and which must remain temporarily.

Your contact rights

You can ask for access to your account data, correction of an inaccurate detail or clarification about its use through the support form. We may verify your identity first, then reply with the available action and any local-law limitation.

Privacy Policy Questions From Indonesia

These Privacy Policy answers cover the searches we hear most often before an account is opened or a wallet receipt is checked. They explain the data connected with account access, how local payment references are treated, how cookies work and how to contact us. If your request concerns a specific record, use the account support form so we can check it accurately.

The Privacy Policy covers account details, phone verification, login and device records, support messages, cookies and payment references. It explains why we use those records, how we protect access, how long we retain them and how you can contact us about a data request.

We may collect the name and phone number you provide, the verification result, login timestamps, device or browser details and support messages. If you use DANA, OVO, GoPay or QRIS, we may also receive a payment reference and status needed for account matching.

Yes. Our Privacy Policy explains how we handle the payment reference and status connected with DANA, QRIS, OVO, GoPay, bank transfer or a virtual account. The wallet or bank may process additional data under its own privacy terms, which you should check separately.

You can use the account support form to ask about an inaccurate name, phone detail or other account record. We may confirm that you control the account before making a change, and we will explain if a record must remain because of applicable local requirements.

Cookies can remember a session choice and help the account path work on your mobile or desktop browser. Our Privacy Policy explains their role in access and settings. You can also ask support what cookie or device detail is connected with a particular login.

We retain account, security, support and payment records for as long as needed for the stated purpose, account assistance and applicable local rules. If you ask about removal, we review the specific record and explain whether it can be deleted, restricted or retained.

Use the support form linked through your account path and state whether you want access, correction, clarification or a retention request. Where local law permits, we assess the request after confirming account control. Never include your wallet PIN or one-time code.