Reference

Privacy Policy for lucky777 apk Accounts

Our lucky777 apk Privacy Policy explains what we collect when you create an account, verify your phone, use DANA or QRIS, and move through the lobby on mobile.

Account clarityWallet recordsCookie choicesAccess requests
lucky777 apk Privacy Policy for lucky777 apk Accounts
HELP WITH RECORDS

Where Your Privacy Questions Go

A clear support path helps when a privacy request is connected to a login, wallet reference, or device you no longer use.

Account help route Use the account help path for a Privacy Policy question about your registered phone number, sign-in record, or phone verification. We may ask you to confirm account ownership before discussing personal data, and you should never send us your password or one-time access code.
Wallet record check For a DANA, OVO, GoPay, QRIS, bank transfer, or virtual account query, provide the payment reference and approximate date through account support. We compare the reference with your account record, then explain what data we hold and why it is connected to the request.
Privacy request Ask us to access, correct, or remove eligible personal data through the same support route. State the exact change you need, such as an outdated phone detail, and we will confirm identity before taking action where local law permits.
DATA HANDLING

What We Do With Account Data

Our privacy process follows the account journey rather than collecting broad details without a purpose.

Account details

We use your registered contact details and phone verification status to create and protect account access. When you request a change, we compare the request with the existing account record before editing it, helping prevent another person from changing your details.

Wallet references

Payment references from DANA, OVO, GoPay, QRIS, bank transfer, or virtual account activity may be retained to reconcile account history and answer status questions. We use the reference for that operational purpose rather than treating it as a separate profile.

Cookies and sessions

Cookies can keep a signed-in session, remember selected settings, and help the mobile path return to the right page. Clearing browser cookies may sign you out and remove those choices, but it does not automatically delete account records held for required purposes.

Device security

We may record device or browser signals when you sign in so we can spot unusual access and ask for an account check. These signals support account security; they are not used to read unrelated files, contacts, or messages on your device.

Retention choices

We keep personal data only for the period needed for account operation, payment reconciliation, security checks, support history, or a legal requirement. When you ask about retention, tell us which record you mean, such as a wallet reference or old device session.

Policy changes

If this Privacy Policy changes in a way that affects your account data, we will place the revised wording on the policy page. Check the page before opening an account or continuing access, especially when local law changes the conditions that apply to you.

Privacy Policy Answers for Indonesia

These Privacy Policy answers address the practical questions we expect before you open an account or ask us to handle personal data. We cover the account step, phone verification, local wallet references, cookies, device access, and requests to see or change records. If your question is not listed, use the account help route with a precise description and avoid sending passwords or one-time access codes.

The Privacy Policy covers data linked to your account, phone verification, sign-in activity, device signals, cookies, support messages, and payment references. It explains why DANA, OVO, GoPay, QRIS, bank transfer, or virtual account details may be connected to an account record.

Phone verification helps us confirm that the person opening or accessing an account controls the registered number. It also supports account recovery and privacy checks. We do not need your password or one-time access code in a support message.

Yes. The Privacy Policy covers payment references connected with DANA and QRIS, as well as OVO, GoPay, bank transfer, and virtual account records. We use those references to reconcile account activity, check status, and answer a specific support request.

You can ask for access to eligible personal data through the account help route. Include your registered phone number and describe the records you want, such as device sessions or wallet references. We confirm account ownership before responding where local law permits.

Cookies can retain a session, selected settings, and the page path used on your mobile browser. Clearing them may sign you out or remove saved choices. Cookie clearing does not by itself erase account records that must remain for security, support, or legal reasons.

Send a correction request through account support and identify the outdated field, such as a phone detail or contact record. We compare your request with the existing account information and may ask for phone verification before making an eligible change.

You can request deletion of eligible personal data through the privacy support route. Explain which record you mean and confirm account ownership. Some account, payment, security, or support records may need to remain where local law permits.