Reference

Privacy Policy for Your luck567 Account

luck567 Privacy Policy explains what we collect when you open an account, sign in from a phone or desktop, and use DANA, OVO, GoPay or QRIS.

Account dataWallet recordsCookie choicesSecurity requests
luck567 Privacy Policy for Your luck567 Account
CONTACT THE TEAM

Where Privacy Policy Questions Go

A clear contact path helps you resolve a Privacy Policy question without sending account details to the wrong place. Use the support contact displayed after you sign in, and include the email or phone detail linked to your account plus the subject of your request. We may ask for a receipt reference when your question concerns DANA, QRIS or a bank transfer. Keep sensitive credentials out of messages. For customers in Bandung and elsewhere in Indonesia, the same account support route handles access, data-copy and correction requests.

Team online

Account contact

Send your Privacy Policy request through the support contact inside your signed-in account. Tell us whether you need a data copy, a correction or a question about how your account details are used.

Receipt check

For DANA, OVO, GoPay or QRIS questions, include the payment reference rather than a wallet password. We use that reference to locate the relevant record and keep the request focused on your account.

Access help

If login or phone verification stalls, use the same support path and explain the device step where it happened. We can separate an account-access issue from a request to change or remove personal data.

DATA HANDLING

Inside luck567 Privacy Controls

We handle this policy area through practical account controls rather than vague promises. Sign-in checks help us link a request to the correct account, while device and browser records help identify an…

Account details

We collect the details you enter during account creation and phone verification. These details help us associate your sign-in, policy requests and account activity with the correct record instead of another account using a similar contact detail.

Device records

Your browser, device type and session signals may be recorded when you sign in. On mobile, this helps us investigate a failed login or an unexpected switch between the lobby and the wallet-status screen.

Cookie settings

Cookies can keep a signed-in session working as you move between account pages. You can adjust cookie permissions in your browser, although refusing some cookies may require you to sign in again during the same visit.

Wallet references

A DANA, OVO, GoPay, QRIS, bank transfer or virtual account reference lets us match a cashier event with your account. We do not need your wallet password for a receipt-status request.

Security checks

Phone verification and sign-in checks help protect account details from an unverified change. Never send a password or one-time code in a support message; we use account-linked checks for identity confirmation.

Retention requests

We keep records for the purpose they serve, including payment reconciliation or a legal requirement. Ask us to correct, copy or remove eligible data through your signed-in account, and we will assess the request against those purposes.

Privacy Policy Questions Answered

These Privacy Policy answers cover the questions you are most likely to ask before opening a luck567 account from Indonesia. We explain the account step, wallet references, cookies, device records and contact route in plain English. If your situation is specific, use the signed-in support path and mention the exact record or session involved. Availability depends on local law, so a request about access and a request about personal data may require separate checks.

The luck567 Privacy Policy covers account details, phone verification, device and browser records, cookies, support messages and payment references. It applies when you sign in, move through the mobile lobby or use DANA, OVO, GoPay, QRIS, bank transfer or a virtual account.

We use the details entered during account creation and phone verification to connect you with the correct account and protect access. They also let us answer a data-copy or correction request without disclosing another person’s account record.

Yes. The Privacy Policy covers the transaction reference needed to match a DANA or QRIS receipt with your account. It also covers OVO, GoPay, bank transfer and virtual account status records. Send a reference through support, not a wallet password.

Sign in and use the support contact shown in your account area. State whether you want a copy or a correction, identify the contact detail linked to the account, and describe the record. We may verify the request before responding or changing it.

Cookies can keep your signed-in session connected while you move between account, cashier and lobby pages. You can change permissions in your browser settings. If some cookies are refused, you may need to repeat the sign-in step on your phone or desktop.

We retain each record for the purpose it serves, such as matching a wallet reference, investigating access or meeting a legal requirement. Retention can differ by record type. Ask through the account support path if you want a specific retention question checked.

You can send a removal request through the signed-in support contact. We first verify that you control the account, then assess which records can be removed and which must remain for payment reconciliation, security review or a legal requirement.