Reference

luna805 Privacy Policy for Indonesian Accounts

Our Privacy Policy shows how luna805 handles the details you provide when opening an account, signing in from a mobile device, or checking wallet status through DANA, OVO…

Account dataWallet recordsDevice accessYour request path
luna805 luna805 Privacy Policy for Indonesian Accounts
CONTACT ROUTE

Get Help With Privacy Requests

A clear contact path helps when you want to ask about stored data, correct an account detail or question a wallet record. Start from the support contact available after you sign in, and include your account identifier plus the receipt or status reference involved. We use that context to locate the right record without asking you to resend unnecessary personal details. If sign-in stalls, use the account-help route shown beside the cashier area, where your request can be linked to the affected account.

Team online

Account data request

Ask us which account details we hold and why they are used. Include the phone number linked to your account so we can match the request carefully before discussing private records.

Wallet record question

For DANA, OVO, GoPay or QRIS status questions, send the transaction reference shown in your account. We can trace the payment record without requesting your wallet password or full security credentials.

Access correction

If a phone, device or profile detail is incorrect, contact us through the signed-in support path. We may ask for account verification before changing data that affects login or payment matching.

DATA PRACTICE

Know What We Keep And Why

We make this policy practical by connecting each data use to an account task you can recognise.

Account details

We handle details such as your account identifier, verified phone reference and selected profile settings to create access and respond to account requests. We do not treat a lobby title such as Live Blackjack Gold as a reason to collect unrelated personal details.

Device signals

When you sign in on a phone or desktop, we may record device and session signals that help identify repeated or unusual access. These signals support account protection and are not a substitute for your phone verification step.

Cookies and sessions

Cookies can keep a session active, remember a page setting and help us understand whether a sign-in request belongs to the same browser. You can manage browser cookie controls, although turning them off may interrupt account access.

Payment references

A DANA, OVO, GoPay, QRIS, bank transfer or virtual account record can include a reference, amount status and account match. We use those fields to check receipt progress, not to request your wallet password or banking login.

Retention period

We retain account and transaction records only for as long as needed for the stated account purpose, a support request, security checks or a legal obligation. A retention question can be sent through the signed-in privacy contact path.

Change requests

You can ask us to access, correct or clarify personal data connected with your account. Send the request from the account contact route, identify the record concerned and complete any verification needed to protect your account.

Privacy Policy Answers For Your Account

These Privacy Policy answers cover the account, device and wallet questions we expect you to ask before opening access. Each answer stays focused on how luna805 handles your data, including phone verification, mobile sessions, payment references and requests sent through support. If your question concerns a record not listed here, use the signed-in contact path and include only the details needed to locate it.

It covers data linked to account creation, phone verification, sign-in sessions, device access, support messages and payment status. That includes references connected with DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity.

Phone verification helps connect the account request to the correct person and protects access when a sign-in or data request is made. We may use the verified phone reference to confirm identity before discussing private account records.

Yes. We may handle session and device signals from your phone or desktop to identify unusual access, keep the signed-in path working and investigate an account request. These signals are used for account protection rather than wallet-password access.

We use payment references and status details to match a submitted DANA or QRIS receipt with the right account and cashier record. We do not need your wallet password or banking login to check whether a payment reference has progressed.

You can ask for access to, or correction of, personal data connected with your account. Use the signed-in support contact, describe the record involved and complete identity checks where needed before we disclose or change private details.

We keep records for the time needed to provide the stated account service, handle support, protect access or meet a valid legal obligation. If you want a retention explanation for a particular record, send its account or payment reference.

Use the privacy or account-help contact shown after sign-in and mention that your request concerns the Privacy Policy. Add your account identifier and a short description, but do not send wallet passwords, banking credentials or unnecessary private data.