Reference

loby89 Privacy Policy, Clearly Set Out

loby89 Privacy Policy explains what account, device and wallet details we collect, why we use them, and how you can ask about your data.

Account dataWallet detailsCookie choicesAccess requests
loby89 loby89 Privacy Policy, Clearly Set Out
HELP WITH PRIVACY

Get Clear Answers About Your Data

A direct support route helps when a privacy question appears beside an account or wallet task. Tell us which account step concerns you, such as phone verification, a QRIS receipt, or a device login, and include only the details needed to locate the record. We use the support path linked near the cashier and account area so your request reaches the right team without sending sensitive wallet credentials. Requests are handled under this Privacy Policy and according to local law.

Team online

Account data request

Ask us what account details we hold by using the support path beside your account area. Include your registered contact detail and the request type; never send a DANA, OVO, GoPay or bank password.

Wallet record question

If a QRIS, virtual account or bank transfer record looks unfamiliar, contact support with the amount reference and date shown in your account. We use those details to locate the payment record without asking for private wallet access.

Privacy correction

You can ask us to correct an inaccurate account detail through the same support route. We may request phone verification before changing access-related data, helping us avoid altering the wrong loby89 account.

DATA HANDLING

What We Do With Your Account Details

Privacy controls work best when each data use has a clear reason. We separate account access, payment matching, security checks and service measurement rather than treating every record the same.

Account creation

When you open an account, we use the contact details and phone verification result needed to create your login and protect access. We do not ask you to place wallet passwords in our account form for DANA, OVO or GoPay.

Payment matching

A DANA, OVO, GoPay, QRIS, bank transfer or virtual account reference helps us connect a payment status to your account. We use the reference for reconciliation and support, not as a request for your private wallet login.

Cookies and devices

Cookies can remember a session choice, while device and browser signals can help us detect a login that does not match your usual path. You can manage browser cookie settings, though some account functions may then need another sign-in.

Account security

Phone verification and login records support access checks when you move from a mobile browser to desktop. If a sign-in looks unusual, we may ask for an account step before changing contact details or showing wallet status.

Retention choices

We keep records only for the period needed for account operation, payment matching, security, support and legal duties. You can ask which category applies to your record and request removal where local law permits and no required exception applies.

Your request route

For access, correction or deletion questions, use the support route near the account and cashier areas. State the request plainly, identify your registered contact detail, and avoid sending passwords, full wallet credentials or unrelated personal records.

Privacy Policy Answers For loby89

These Privacy Policy answers focus on the searches you may make before opening an account or checking a wallet record. We keep the wording practical: what we collect, how access works, what cookies do, and how you can contact us. If your question depends on Indonesian requirements, we apply the rule where local law permits and explain the next account step.

It covers account details, phone verification, login and device records, cookies, payment references and support requests connected with your use of loby89. It also explains why we use each category, how long records may remain, and how you can ask about access or correction.

We collect the contact and account details needed for registration, plus the phone verification result used before account access. We may record login, browser and device signals for security. We do not need your DANA, OVO or GoPay password to match wallet status.

Yes. The Privacy Policy covers payment references and status details connected with QRIS, bank transfer, virtual account, DANA, OVO and GoPay. These records help us match a transaction to your account and answer receipt questions without requesting private wallet credentials.

You can send an access request through the support route beside your account area. Identify your registered contact detail and explain which category you want checked, such as login records, phone verification or a QRIS receipt. We may verify account ownership before responding.

Use the same support path and state whether you want correction or deletion, then identify the affected account detail. We assess the request under the Privacy Policy and local requirements. Where local law permits, we remove or amend eligible records after account verification.

Cookies can retain a session preference and help the mobile browser return you to the account path. If you block or clear them, you may need to sign in again or repeat phone verification. Device signals may still be processed for access security.

Yes. Your access and eligibility depend on local law, and our Privacy Policy is applied where local law permits. If a local requirement affects an account or data request, contact support through the account area so we can explain the available path.