Reference

luna33 Privacy Policy For Your Account

luna33 Privacy Policy explains how we handle the details needed for account access, wallet checks and your activity across Speed Blackjack, Aviator and other lobby areas.

Account dataWallet recordsCookie choicesAccess requests
luna33 luna33 Privacy Policy For Your Account
CONTACT PATHS

Get Privacy Policy Help Near Account Access

A direct request helps us locate the right record without asking you to repeat your account history. When a Privacy Policy question concerns a login, phone verification or wallet status, include the account contact and the relevant date, but never send a password or full payment credential. We route questions about DANA, QRIS, bank transfer and virtual account records to the account-help path so the answer stays connected to the correct transaction.

Team online

Account privacy desk

Ask us to explain the personal data linked with your account, including the phone verification step used before access. Send the request through the account-help path and include your registered contact so we can match the enquiry without requesting your password.

Wallet record check

If a DANA, OVO, GoPay or QRIS entry looks unfamiliar, tell us the payment name, date and displayed status. For bank transfer or virtual account records, add the reference shown in your account; keep card, PIN and full wallet credentials out of the message.

Policy change request

You can ask us to correct, access or remove eligible account details through the same support route. We may need a phone verification step before releasing data, and we will explain any limit that depends on local law or a required record period.

HANDLING DETAILS

Inside luna33 Privacy Policy Controls

Privacy Policy is connected to the real account steps you take, not treated as a separate message.

Data we receive

We may receive your account contact, phone verification result, device and browser details, support content, selected lobby actions and payment status. DANA, OVO, GoPay, QRIS, bank transfer and virtual account records help us match an account event, rather than giving us your private wallet password.

Why we use it

We use account data to create access, confirm a requested account step, display wallet status, protect against unusual access and answer your messages. Activity connected with Speed Blackjack, eurorogel or Aviator can help us identify the correct session when you ask about a record.

Cookies and devices

Cookies and similar device signals help keep a session connected to the right account and remember settings needed for the mobile path. You can manage browser permissions, although changing them may affect login continuity or the way a policy request is matched to your session.

Account security

We limit account-data access to the operational purpose that needs it and use phone verification before selected account actions. If your device changes or a login looks unusual, we may ask for another account check before discussing wallet records or releasing information.

Retention periods

We keep information for as long as it supports the stated account, security, dispute or legal purpose. When that purpose ends, we remove or anonymise the record where practical. A request can be made through support, and we will explain if a period still applies.

Your request route

Ask to access, correct or delete eligible data by using the policy contact path and naming the account contact involved. We may verify ownership before responding. If the request concerns Indonesia access, our explanation will note where local law affects the available action.

Privacy Policy Questions About luna33

These Privacy Policy answers cover the account and wallet situations you are most likely to encounter before or after access. We have kept the wording tied to actual steps, from phone verification and cookie settings to a DANA receipt or a QRIS status. If your case is not listed, send the account contact and the specific record through support so we can respond to the right question.

It covers account details, phone verification, device and browser signals, cookies, support messages, lobby activity and payment-status records. That includes DANA, OVO, GoPay, QRIS, bank transfer and virtual account events when they are connected with your account or a requested support response.

Phone verification helps connect an account request with the person making it and supports account protection before selected access steps. It can also help us confirm ownership when you ask for Privacy Policy data, wallet records or a correction to your account details.

Yes. The policy covers payment-status details received for DANA and QRIS, as well as OVO, GoPay, bank transfer and virtual account activity linked to your account. We use the displayed status and reference needed for account support, not your private wallet PIN or password.

Use the policy contact path and state that you want an account-data request. Include your registered contact and the type of record, such as phone verification, cookie settings or an Aviator session. We may complete an ownership check before sharing data or describing the result.

You can request a correction or removal of eligible information through support. Tell us which account detail is wrong or no longer needed, and we will check the relevant record. Some information may remain for a stated security, dispute or legal period where local law requires it.

The same Privacy Policy applies when you use a phone or tablet to move from login to the lobby. Cookies and device signals may keep the session connected, while changed browser permissions can interrupt continuity. We may repeat phone verification before discussing data from that device.

Yes. Access and eligibility depend on local law. Our Privacy Policy still explains how we handle account and wallet records for a permitted request, but the available service or data action can vary by Indonesian legal requirements. Contact support if you need the current account-specific explanation.