Reference

Open the luck77 Privacy Policy

luck77 Privacy Policy explains what we collect when you open an account, sign in from a mobile device, or check DANA, OVO, GoPay and QRIS status.

Account recordsWallet referencesCookie choicesSecurity requests
luck77 Open the luck77 Privacy Policy
CONTACT PATHS

Reach policy support from your account

A clear contact route helps you ask what a record means, why a verification detail is needed, or how to request a change.

Account help Use the account help path for Privacy Policy questions about your name, phone detail, sign-in record or verification step. Include the account identifier you can safely share, and we will use the request to locate the relevant record without asking for your DANA, OVO or GoPay password.
Payment status For a DANA, OVO, GoPay, QRIS, bank transfer or virtual account query, send the payment reference shown in your account and describe the status displayed. We can check the matching record and explain which data was retained for that payment event.
Access requests If you cannot sign in, use the contact option shown beside the login or cashier path and state that your request concerns the Privacy Policy. We may ask for an account check before discussing personal data, so another person cannot obtain your records.
DATA CONTROLS

Check security around your account data

We keep the Privacy Policy practical by linking each data use to an account action, such as sign-in, phone verification, payment matching or support.

Account details

We may hold the details you provide during account opening, including contact information and verification data. These details help us match your sign-in and support request to the right account, rather than treating a message from an unknown address as proof of ownership.

Device signals

A phone or desktop session can create technical records such as browser type, session timing and security signals. We use these details to recognise unusual access and keep the account path safer; they are not a request for access to your private device files.

Cookie controls

Cookies can keep a sign-in session working, remember selected settings or show whether a page loads correctly. Check your browser privacy controls to clear or restrict them. Removing a session cookie may sign you out, but it does not itself send us a deletion request.

Payment matching

When a payment record names DANA, OVO, GoPay, QRIS, bank transfer or a virtual account, we retain the reference and status needed to match it with your account. We do not need your wallet password to investigate a receipt or pending status.

Retention checks

We keep records only for the period needed for the stated account, security, support or legal purpose, subject to local requirements. If you ask how long a particular record remains, tell us its type or payment reference so we can answer more precisely.

Change requests

To request access, correction or removal of eligible personal data, contact account help from the email or phone detail attached to your account. We may verify ownership first, then explain what can be changed and what must remain where local law permits.

Find answers about the Privacy Policy

These Privacy Policy answers address the account and wallet questions you are most likely to have before opening an account on luck77. We keep the wording tied to actual actions: sign-in, phone verification, cookies, payment references and requests made through account help. If your situation is not covered, contact us using the route shown in your account.

The luck77 Privacy Policy covers account details, sign-in activity, device signals, cookies, phone verification, support messages and payment references. It explains why we use each category, how requests are handled and when access depends on local law or is available where local law permits.

Yes. The Privacy Policy covers references and status details connected with DANA, QRIS, OVO, GoPay, bank transfer and virtual account activity. We use those records to match a payment event to your account and support a status check, without asking for your wallet password.

Sign in, open account help and ask for access to your personal data under the Privacy Policy. Include the contact detail attached to your account and describe the record you need. We may verify ownership before explaining which records can be provided where local law permits.

You can request a correction through account help by identifying the phone or email detail that needs updating. We may ask for a verification step before making a change, because the Privacy Policy requires us to avoid giving account control to an unauthorised person.

Cookies can preserve a sign-in session, remember selected settings and help us check page performance. Your browser controls can clear or restrict them. After clearing session cookies, you may need to sign in again; the Privacy Policy explains the related use and request path.

Retention depends on the type of record and the purpose behind it, such as account security, payment matching, support or a legal requirement. Ask account help about a specific record, such as a QRIS reference or verification message, and we will explain the applicable handling.

Use the support contact shown on the sign-in or cashier path and state that your request concerns the Privacy Policy. Share only safe account details and the relevant payment reference if needed. We may verify ownership before discussing personal data or changing access.