Reference

Privacy Policy For Your lucky72 Account

Our Privacy Policy explains what we collect when you open a lucky72 account, use DANA or QRIS, and move between the lobby and cashier.

Account dataWallet statusDevice securityPolicy access

Browse Our Lobby Read FAQ

How Wallet And Account Data Works

lucky72 Service availability depends on jurisdiction. Users are responsible for checking local law before access.

We collect the details needed to create and protect your account, including contact details, verification results, login events, device information and actions taken in the lobby or cashier. When you use DANA, OVO, GoPay, QRIS, bank transfer or a virtual account, we receive payment status and

1
reference details needed to match the transaction to your account; we do not need your wallet password to do that. We use this material to provide access, detect unusual sign-in activity, answer payment-status questions and meet applicable requests. Access depends on local law, and where local
2
law permits, our policy applies to your use from Indonesia. We keep records only as long as needed for these purposes or for a valid legal requirement, then remove or de-identify them through our operating process.

Service availability depends on jurisdiction. Users are responsible for checking local law before access.

HELP WITH PRIVACY

Where To Ask About Your Data

A clear account support path helps when you want to ask about the Privacy Policy or a wallet record.

SECURITY BY DETAIL

What Our Privacy Process Covers

Our handling process follows the moments that matter in your account: opening access, signing in, checking a wallet status and asking for help.

Account creation

When you open an account, we use the contact details and verification step you provide to create access and connect activity to the correct account. Clear phone verification can prevent login confusion, while inaccurate details may delay a requested change.

Payment references

DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity can produce a reference, amount and status record. We use that record to match the cashier event, investigate a missing status and answer your account question.

Device signals

We may record browser, device and sign-in signals when you move from login to the lobby. These signals help us identify unusual access and protect the account; they are not a request for your device content or wallet password.

Cookies and sessions

Cookies or similar storage can keep a session active, remember a selected setting and help the lobby load consistently on mobile or desktop. If you clear them, you may need to sign in again or repeat an account verification step.

Retention choices

We retain account, security and payment-status records for the period needed to operate access, resolve a support question or meet a valid legal duty. When a record is no longer needed, we remove it or separate it from direct account details.

Policy requests

To ask about access, correction, deletion or a copy of personal data, use the account support path and describe the request clearly. We may verify ownership first, then explain what we can change and any reason a record must remain.

Privacy Policy Answers For Indonesia

These Privacy Policy answers cover the account and wallet questions you are most likely to have before opening access. They explain the data connected to login, payment references, cookies, device checks and requests for changes. If your situation is not covered, use the signed-in support path and include only the details needed to locate your account.

It covers personal details linked to your account, login and device signals, cookies, payment references and support requests. It also explains why we use those records, how long we keep them, and how you can ask about access, correction or removal.

Phone verification helps connect account access to the correct person and reduces confusion when you sign in from a new device. We use the verification result for account protection and support checks; we do not need your DANA, OVO or GoPay password.

Yes. When you use QRIS, DANA, OVO, GoPay, bank transfer or a virtual account, we may receive a transaction reference and status. We use those details to match the cashier event, investigate a stalled status and answer your account request.

We may use browser, device and sign-in signals linked to your session, such as access timing or a device identifier. This helps identify unusual account activity when you move from login to the lobby, without requesting the contents of your device.

Yes. Use the account support path and name the field you believe is wrong, such as a contact detail. We may verify account ownership before making a change, and we will explain if a record must remain because of an operating or legal requirement.

We keep account, security and payment-status records for as long as needed to provide access, resolve a support matter or meet a valid legal duty. Once a record is no longer needed, we remove it or separate it from direct identifiers.

Start through the signed-in account support path and describe whether your question concerns account data, cookies, device access or a DANA, OVO, GoPay or QRIS reference. Do not send a wallet password; we may request an account ownership check instead.

Privacy Policy For Your lucky72 Account

Where To Ask About Your Data

What Our Privacy Process Covers

Account creation

Payment references

Device signals

Cookies and sessions

Retention choices

Policy requests

Privacy Policy Answers For Indonesia

01 What does the lucky72 Privacy Policy cover?

02 Why does lucky72 need phone verification?

03 Does the Privacy Policy cover QRIS and wallet payments?

04 What device data does the Privacy Policy mention?

05 Can I ask lucky72 to correct my personal data?

06 How long does lucky72 keep account information?

07 Where can I ask about the lucky72 Privacy Policy?

Related Pages