Reference

lineslot88 Privacy Policy For Your Account

Our lineslot88 Privacy Policy explains what we collect when you open an account, sign in from a mobile device, or check wallet status through DANA, OVO, GoPay and…

Account clarityWallet recordsDevice securityYour access rights
lineslot88 lineslot88 Privacy Policy For Your Account
CONTACT YOUR WAY

Get Policy Help Beside Your Account

A clear support route matters when you want to understand a wallet record, correct a phone detail, or ask why a security check appears. Start from the support link in your signed-in account, where we can match your request with the right account record. If access stalls, use the same route without sending a wallet password or full payment credentials.

Team online

Account support

Use the support link after signing in to ask about collected account details, a phone verification record, or a correction request. We can respond with the account context needed to locate your case.

Wallet questions

For DANA, OVO, GoPay, QRIS, bank transfer, or virtual account records, include the payment reference and date. We use those details to check status without asking for your wallet password.

Access concerns

If a mobile sign-in or security check blocks your account, contact us through the account support path and describe the device step. Do not send a one-time code in your message.

DATA HANDLING

What Your Privacy Settings Cover

We keep the policy practical: you can see why account, device, cookie, and payment-reference records are used, and you can ask us to check a particular entry.

Account records

We use your registration details, phone verification status, and sign-in history to provide account access and respond to account questions. You may ask us to confirm or correct these records through support.

Payment references

A DANA, OVO, GoPay, QRIS, bank transfer, or virtual account reference helps us match a transaction event. We record the status needed for reconciliation, not your wallet password or private wallet login.

Device signals

Browser type, operating system, session time, and network details can support fraud checks and sign-in protection. These signals help us compare a new mobile session with normal account activity.

Cookies

Cookies can retain session status, language choices, and security settings so the account path works when you move from login to the lobby. You can manage cookie controls in your browser.

Retention choices

We keep records for the period connected with their purpose, including open support cases, payment reconciliation, account security, and applicable legal duties. When a record is no longer needed, our process removes or de-identifies it.

Change requests

Ask us to access, correct, or explain personal data through the signed-in support path. Include the account contact detail and the specific record, and we may verify ownership before making a change.

Privacy Policy Answers For Indonesia

These Privacy Policy answers address the account and payment questions you are most likely to have before opening or using an account. They also explain the practical path for requests, device access, cookies, and records linked with local wallet activity in Indonesia.

It covers account details, phone verification, sign-in and device signals, cookies, support messages, and payment references connected with DANA, OVO, GoPay, QRIS, bank transfer, or virtual account activity.

We use phone verification to confirm account ownership, support sign-in protection, and investigate access requests. If you ask for a correction, we may compare the request with the verified account contact.

No. Our policy concerns transaction references and status needed for account reconciliation. We do not ask you to send a DANA, OVO, GoPay, or QRIS wallet password through support.

Yes. Use the support link in your signed-in account, identify the record you want checked, and provide the account contact detail requested for ownership verification. We will assess the request under applicable law.

We may use browser, operating system, session time, and network details to protect sign-in activity. This helps us examine an unfamiliar mobile session without reading private files or wallet credentials.

Retention depends on why a record exists. We keep active account, security, payment-reconciliation, and open support records for the period needed for those purposes and applicable legal duties, then remove or de-identify them.

Open the support link inside your account and ask for a privacy request. If you cannot sign in, describe the access issue without sharing a password or one-time code; eligibility depends on local law.