Reference

lawas 777 Privacy Policy For Your Account

Our Privacy Policy explains how lawas 777 handles the details connected with your account, from phone verification before account access to wallet records for DANA and QRIS.

Account dataWallet recordsCookie choicesAccess depends on local law
lawas 777 lawas 777 Privacy Policy For Your Account
CONTACT PATHS

Get Privacy Policy Help Through Account Support

A clear contact path matters when you need a copy of your data or want to correct an account detail.

Account message Send a privacy request through the signed-in account route and include your registered phone…
Wallet record check If your request concerns DANA, OVO, GoPay or QRIS, name the rail and date…
Access assistance When phone verification blocks a privacy request, tell us which mobile browser or computer…
HANDLING DETAILS

Six Ways We Handle Your Data

We keep the Privacy Policy practical by linking each data use to an account action you can recognise.

Account details

We use your submitted account details to create, maintain and identify your profile.

Security signals

Sign-in time, browser type and device signals can help us identify unusual activity.

Cookies and sessions

Cookies and session tools help keep your signed-in path working across the mobile lobby and account pages.

Wallet references

We retain payment references needed to match account activity with QRIS, bank transfer or virtual account requests.

Retention periods

We keep different records for the period needed for account security, support handling and applicable obligations.

Change requests

To request correction, deletion or a copy of personal data, contact us through the account support path.

Privacy Policy Answers For lawas 777

These Privacy Policy answers address the account questions you may search before opening access. They explain the practical route for data requests, cookies, phone verification and wallet records, without asking you to share sensitive payment credentials.

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

Use the signed-in account support route and state that your request concerns the Privacy Policy. Include your registered phone number or account identifier; we may verify your identity before responding.

Yes, request a correction through account support and identify the detail that needs changing. Phone verification may be required before we alter account-linked information or confirm the result.

Phone verification helps us confirm that the person requesting access or a data change controls the account. It is an account step before access and may apply to privacy requests.

Yes. It covers payment references used to match account activity with DANA, QRIS and other listed rails. We ask for the rail and date, not your wallet PIN or security code.

Cookies and session tools help maintain your signed-in path between the mobile lobby and account pages. You can adjust browser settings, but restricting cookies may affect selected account functions.

You can submit a removal request through account support. We assess it against security, account handling and applicable obligations; availability of a particular request depends on local law.