Reference

lusa777 Privacy Policy For Your Account

Our Privacy Policy explains how lusa777 handles the details you provide before account access, including your phone verification, wallet records and mobile session data.

Account recordsWallet activityMobile sessionsYour privacy choices
lusa777 lusa777 Privacy Policy For Your Account
PRIVACY HELP ROUTE

Ask About Privacy Policy Through Your Account

A privacy question should have a simple route, so we keep requests close to the account area rather than asking you to repeat sensitive details in…

Account support link Open the support link from your signed-in account and describe the Privacy Policy request.
Receipt context For a DANA, OVO, GoPay or QRIS question, include the visible reference and status…
Access check If you cannot reach the account area, tell us the device path you used…
CONTROL YOUR RECORDS

Explore Privacy Controls For Mobile Accounts

Our handling practices are designed around the moments that create a record: opening an account, confirming a phone, signing in, selecting a wallet route and contacting support.

Data we receive

We may receive account details, phone verification results, sign-in timestamps, device signals and payment references.

Cookies and sessions

Cookies and similar session tools help keep your account path active between pages.

Account security

We use phone verification, sign-in records and device-related signals to identify unusual account activity.

Retention timing

We keep records only for the period needed for account operation, security checks, dispute handling and applicable legal duties.

Request a change

You can ask us to correct an inaccurate account detail or explain a payment reference through the signed-in support link.

Who handles contact

Our account support team receives privacy questions submitted through the account path.

Browse Privacy Policy Answers Before Opening

These Privacy Policy answers cover the practical searches you may make before opening a lusa777 account. They explain the records connected with phone verification, wallet activity, cookies, mobile access and account requests, so you know what to expect from the first account step.

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 your phone number to create and verify account access, connect you with account records and investigate unusual sign-in activity. Verification can be required before we discuss a privacy request.

Yes. It explains that DANA and QRIS flows may provide us with a reference, amount, status and timestamp. We use those details to match the account action, not to request your wallet password.

Sign in, open the account menu and use the support link. Name the record that appears incorrect and explain the requested correction. We may confirm your phone or account details first.

You can submit a deletion request through the account support path. We will assess the request against active account needs, security checks, dispute handling and legal duties that may require some records to remain.

Cookies can keep a signed-in path and session choices available between pages. If you restrict them in your mobile browser, you may need to repeat verification or sign-in steps.

Use the support link inside your signed-in account and describe the privacy matter. If access is unavailable, provide the device path and account contact detail requested for identity checking.