Reference

lusa777 Privacy Policy for Indonesian Accounts

Our Privacy Policy explains how lusa777 handles your account details, phone verification, device sessions and payment records connected with DANA, OVO, GoPay and QRIS.

Account dataWallet recordsCookie choicesPolicy requests
lusa777 lusa777 Privacy Policy for Indonesian Accounts
CONTACT PATHS

Privacy Questions Reach Our Account Team

A clear contact path helps when your account record, wallet reference or phone check needs attention. Start from the support route shown inside your account and describe the specific Privacy Policy request, such as access, correction or deletion. Include the payment rail involved, such as QRIS or bank transfer, but never send a password or full security code.

Team online

Account access request

Ask us to confirm the personal data connected with your lusa777 account. We may use phone verification before discussing account-specific details or changing access records.

Payment record check

For a DANA, OVO, GoPay or QRIS query, share the receipt reference and approximate account step. We use those details to locate the correct payment record.

Correction or deletion

Send a clear request through the account support path when a profile detail is wrong or you want eligible data removed. We explain any record that must remain for legal or security reasons.

SIX DATA CONTROLS

Six Controls Behind Your Account Data

We apply the Privacy Policy to the details created across your account journey, from the first phone check to a mobile browser session and a wallet status request.

Purpose-based collection

We collect account and phone details to create access, complete verification and protect your session. Payment references support reconciliation for DANA, QRIS, bank transfer and virtual account actions.

Mobile session handling

When you use a mobile browser, session data helps keep the login path connected to the lobby. Closing the browser or signing out can end that active session on your device.

Cookie choices

Cookies can support sign-in continuity, security checks and basic preference handling. Your browser settings let you restrict cookies, although some account steps may then require another verification.

Account security

Phone verification comes before account access, and we may compare session or payment details when activity needs checking. Do not share passwords, one-time codes or wallet security details.

Retention decisions

We keep records only for the period needed for the stated account, payment, security or legal purpose. When a record is no longer required, our process can remove or de-identify it.

Request handling

You can ask what data is held, request a correction or ask about deletion through support. We verify account ownership first and explain the result when a restriction applies.

Privacy Policy Answers For Your Account

These Privacy Policy answers address the searches we expect before account access: what lusa777 collects, how wallet records are matched, why cookies appear and how you can make a request. If your question concerns a specific receipt or phone check, use the account support path with only the reference needed to find it.

It covers account details, phone verification, browser sessions, cookies, payment references, support requests, security checks and retention. It also explains your options for access, correction and eligible deletion.

We use your phone number to create the account path and complete verification before account access. It also helps us confirm that a privacy or security request comes from the account holder.

Yes. The policy includes transaction references and status details returned during DANA, OVO, GoPay or QRIS steps, plus bank transfer and virtual account references used for account reconciliation.

Use the support route shown inside your account and ask for a data access request. We may verify your phone or account details before sharing records connected with your identity.

Yes. Send the incorrect field and the updated detail through account support. We check ownership, update eligible records and explain if a security, payment or legal record cannot be changed.

Cookies can keep a mobile browser session connected and support security checks. You can restrict them in your browser, but sign-in or phone verification may need to happen again.

The policy is written for the account and payment flows available in Indonesia, while access depends on local law. If you are unsure about eligibility, contact support before completing account access.