Reference

Privacy Policy for your lucksvip account

Our Privacy Policy shows how lucksvip handles the details connected with your account, phone verification, device access and wallet status before you enter the lobby.

Account dataWallet recordsDevice accessPrivacy requests
lucksvip Privacy Policy for your lucksvip account
REQUEST HELP

Get help with a privacy request

A clear request path matters when your account record or wallet reference needs attention. Open your account help area and include the phone number linked to your login, the subject of your request and any relevant DANA, OVO, GoPay or QRIS reference. We use those details to locate the correct record without asking you to send a wallet password. If you are in Makassar or elsewhere in Indonesia, the same privacy route applies, subject to local law.

Team online

Account request

Use the account help path to ask what personal details we hold, why they are used, or which record is connected with your login. Include your registered phone number so we can check ownership before discussing account data.

Wallet record check

If a DANA, OVO, GoPay or QRIS receipt appears with the wrong status, send its reference through the support path. We compare the receipt with the account ledger and explain which data can be corrected.

Access concern

When a familiar phone or browser is not recognised, contact us through account help rather than sharing a password. We can review the sign-in record, confirm the account step and explain the privacy action available.

DATA CONTROL

Your account data from login to lobby

We keep this policy practical by tying each privacy choice to a real account step. Your registration details support login, your phone check supports account ownership, and device signals help us protect…

Registration details

When you open an account, we record the details needed to create your login and connect your phone verification. We use that record to identify your account when you ask to view, correct or remove eligible personal data.

Payment references

For DANA, QRIS, bank transfer or virtual account activity, we retain transaction references and status details needed to reconcile your account. These records help us check a receipt without requesting your wallet password.

Device signals

Your phone or computer may send browser, device and sign-in signals when you move from login to the lobby. We use these signals to recognise unusual access and investigate an account concern without reading unrelated device content.

Cookies in practice

Cookies can keep your account path working between login, wallet status and lobby pages. You can manage cookie controls in your browser, although changing them may affect saved preferences or require you to repeat an account step.

Retention choices

We keep account, payment and security records only for the period needed for the stated purpose, account support or a legal obligation where applicable. When retention is no longer needed, we remove or de-identify the record where the process allows.

Change or removal

Ask us to correct inaccurate details, explain a processing purpose or remove eligible data through the account help path. We may verify your phone-linked account first, and the result depends on local law and any required recordkeeping.

Privacy Policy answers for lucksvip accounts

These questions cover the privacy points you are most likely to check before opening an account or using a local wallet. We keep the answers tied to login, verification, device access and payment records so you can understand the policy before sharing account details.

It covers account registration, phone verification, device signals, cookies, wallet references, support requests, retention and your available data choices. It also explains how records connected with DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity are handled.

Phone verification helps us confirm that the person requesting account access or a privacy change controls the registered account. It also gives our support team a safer way to locate the correct record without asking you to disclose a wallet password.

Our payment record handling is based on references, status, amount and timing needed to match activity with your account. We do not need your DANA or QRIS wallet password for that check, so you should never send that password through account help.

The policy covers practical access signals such as browser type, device details and sign-in activity connected with the account route. We use them to recognise unusual access and protect your login; they are not a request to read unrelated files or content.

Yes. Use the account help path, state which detail is inaccurate and include the phone number linked to your login. We may verify ownership before making a change, and the available result depends on local law and any recordkeeping duty.

We retain records for the account, support, security or legal purpose that requires them, including time needed to reconcile a wallet receipt. When that purpose ends, we remove or de-identify data where the process allows and local requirements permit.

Open account help and identify your request as a Privacy Policy question. You can ask about registration data, cookies, a phone-linked login, a DANA or QRIS reference, or a removal request; we will explain the next verification step.