Reference

Open the lucky567 Privacy Policy

The lucky567 Privacy Policy shows what we collect when you create an account, verify your phone and use DANA, OVO, GoPay or QRIS.

Account clarityWallet dataMobile accessPolicy contact
Explore Our Lobby Read FAQ
lucky567 Open the lucky567 Privacy Policy
CONTACT ROUTES

Check your privacy support path

A clear support route matters when a privacy question affects your account or wallet record. From your signed-in account, keep the relevant phone number, receipt reference or device detail ready so we can locate the correct record without asking for unrelated information. If you cannot sign in, explain that in your message and include only details needed to identify the request. We handle access questions, correction requests and deletion enquiries through the same policy-focused support path.

Team online

Account access

Ask us to help locate account data after phone verification or a sign-in issue. We may request a matching account detail before discussing records, so your information is not disclosed to the wrong person.

Wallet receipt

For DANA, OVO, GoPay or QRIS questions, send the payment reference rather than a wallet password or full sensitive credential. We use the reference to check the related account event.

Data request

Request a copy, correction or removal of eligible personal data through support while signed in when possible. We will explain any identity check and the next step for your specific request.

DATA PRACTICE

Browse how we handle your records

We keep the Privacy Policy practical by linking each data use to an account action you can recognise.

Collection

We collect details you enter during account creation, such as contact data and verification information, plus records created when you sign in or contact support about your account.

Cookie use

Cookies and similar browser storage can keep a session active, remember a selected setting or help us understand technical errors. You can manage browser permissions, though some access steps may then need repeating.

Account safety

Phone verification is an account step before access, and device signals can help us investigate unusual sign-in behaviour. We will not ask for your wallet password as proof of ownership.

Payment references

DANA, OVO, GoPay, QRIS, BCA, BRI, Mandiri and BNI references may appear in a transaction record. We use the relevant reference for matching and status checks, not for collecting unnecessary credentials.

Retention

We retain records only while they serve the stated account, security, support or legal purpose, subject to applicable requirements. When a record is no longer needed, our process removes or de-identifies it where appropriate.

Your request

You can ask what personal data we hold, request a correction, or ask about removal where applicable. Send the request through support, and we will explain identity checks, limits and timing.

Find answers about Privacy Policy

These Privacy Policy answers cover the searches you are most likely to make before opening a lucky567 account. We address account records, wallet references, cookies, device checks and requests for access or correction in direct language. If your situation is not covered, use the policy support route with the smallest useful set of details, and remember that access depends on local law.

The Privacy Policy covers data connected with account creation, phone verification, sign-in, device use, cookies, wallet references and support messages. It also explains why we use those records, how retention works and how you can ask about access, correction or removal.

No. Our Privacy Policy does not require a DANA or QRIS password for a receipt or status check. We may use a transaction reference, account detail or verification step to match the event while limiting the payment data shared with us.

Device and browser signals can help us recognise unusual sign-in behaviour, protect account access and diagnose a session error. The Privacy Policy explains this use, and you can ask support what type of device record relates to a particular account event.

Send a data request through the signed-in support path when possible and state whether you want access, correction or another permitted action. We may verify account control before releasing records, so the request reaches the correct account holder.

The Privacy Policy does not promise one fixed period for every record. We consider the account purpose, security need, support history and applicable requirements. When information is no longer needed for those reasons, we remove or de-identify it where appropriate.

Yes. Contact us through the policy support route with the incorrect detail and the replacement you want recorded. We may ask for a matching account or phone verification step, then explain whether the change can be made and what happens next.

Cookies can remember a session or preference, but the Privacy Policy page remains available for you to read. If browser settings block necessary storage, you may need to repeat a sign-in or verification step while we diagnose the access issue.

Related Pages

lucky567 Indonesia No Commission Baccarat lucky567 Casino About Us Account information