Reference

567luck Privacy Policy, Clearly Set Out

Your account details, wallet references and mobile device signals are handled for clear account access and safer cashier checks.

Account dataWallet recordsCookie choicesSecurity checks
567luck 567luck Privacy Policy, Clearly Set Out
CONTACT ROUTES

Where To Ask About Account Data

A clear contact path helps you act on this Privacy Policy without sending sensitive details through an open message.

Account support panel Open the support panel after login to ask about stored account data, a correction…
Cashier-linked request For DANA, OVO, GoPay or QRIS records, use the support path beside the cashier…
Phone verification A phone verification step may be required before we disclose, correct or remove account…
CONTROLLED HANDLING

Security Around Wallet And Device Records

Our Privacy Policy separates ordinary account use from the checks needed for wallet and security events.

Account details

We use your submitted phone number, login details and verification responses to open, maintain and protect your account.

Cookie controls

Cookies and similar browser storage help remember a session and support account navigation from a mobile browser or desktop.

Wallet references

For DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity, we retain references needed to match a request, confirm…

Security checks

Phone verification before account access helps us connect a request with the right account.

Retention periods

We keep records only for as long as they serve account security, payment matching, dispute handling or a legal duty.

Change requests

You can ask us to see, correct or delete personal data through the signed-in support panel.

Privacy Policy Questions For 567luck

These answers cover the account and device questions we expect before you open an account from Indonesia. They explain how the Privacy Policy relates to payment references, browser cookies, phone verification and requests made through support. If your situation involves a specific DANA, OVO, GoPay or QRIS record, use the signed-in route so we can locate the correct entry.

It covers account details, phone verification, wallet references, device and browser signals, cookies, support requests and retention. The Privacy Policy applies when you use account pages or cashier functions, with access depending on local law and availability where local law permits.

We use payment references and status details to match DANA, OVO, GoPay or QRIS activity, but you should not send a wallet PIN, password or one-time code to support. The Privacy Policy does not require those secret credentials for an ordinary status check.

Log in, open the account support panel and state whether you want a copy, correction or deletion. Include the relevant account detail, not your password. We may complete phone verification before responding so the Privacy Policy request is linked to the right account.

Device, browser, IP and cookie signals help maintain a session, remember essential account choices and identify unusual login behaviour. You can adjust cookie permissions in your mobile or desktop browser, though blocking them may interrupt account access.

We retain payment references for the period needed to match cashier activity, handle a dispute, protect account security or meet a legal duty. DANA, OVO, GoPay, QRIS, bank transfer and virtual account records may therefore follow different deletion timing.

Yes. Send the request through the signed-in support panel and identify the record you want changed. We verify account control first, then correct or remove data where possible. Some records may remain when security, dispute handling or legal duties require retention.

Yes, the same Privacy Policy covers mobile browser access and desktop access. Browser settings can change cookie behaviour, while account access and eligibility depend on local law. If a mobile login stalls, use the signed-in support route after access is restored.