Reference

Open the lux88 Privacy Policy

Clear choices about your account data come first in the lux88 Privacy Policy.

Account clarityWallet dataCookie choicesAccess requests

Explore How Wallet Data Is Used

lux88 Service availability depends on jurisdiction. Users are responsible for checking local law before access.

Your payment record helps us match an account action with the wallet or bank route you selected. The Privacy Policy covers details entered during account creation, phone verification, sign-in records, device and browser signals, support messages, and transaction references for DANA, OVO, GoPay, QRIS, bank transfer,

1
and virtual account activity. We use these records to process requests, investigate mismatched status, protect account access, and meet applicable legal duties. We do not ask you to send a wallet password through support. Access to lux88 and any related activity depends on local law; where
2
local law permits, you can use the contact path below to ask what data we hold, why it is used, or whether a correction is available. The policy may apply differently when a legal requirement sets a longer retention period.

Service availability depends on jurisdiction. Users are responsible for checking local law before access.

CONTACT PATH

Browse Your Privacy Support Route

A clear contact route makes a privacy request easier to track. Start from your signed-in account help area and describe whether you need a copy of…

DATA PRACTICE

Switch Through Your Privacy Choices

We keep this policy practical by linking each data category to an account action. Sign-in and phone verification records help us confirm account access; browser signals help remember session preferences; payment references…

Account details

When you open an account, we collect the details needed to create and maintain that account. Phone verification can be requested before account access, and we use the result to help protect the correct account.

Cookies and browser signals

Cookies and similar browser signals can keep a session active, remember language or display preferences, and help detect unusual sign-in patterns. You can manage browser cookie settings, though some account functions may then need repeated sign-in.

Wallet references

We retain transaction references rather than wallet passwords. A DANA, OVO, GoPay, QRIS, bank transfer, or virtual account reference can connect a status question to the correct account record.

Account protection

We use phone checks, sign-in records, and device signals to help identify unusual account access. Keep your password and verification codes private; support will not need your wallet PIN to handle a policy request.

Retention periods

We keep data only as long as needed for the purpose described in this Privacy Policy, account support, dispute handling, or a legal duty. A legal requirement may require certain records to remain longer.

Requesting changes

You can ask for access, correction, or clarification through the signed-in support path. Tell us which account detail or payment reference is involved, and we may verify your phone before responding.

Check Common Privacy Policy Answers

These questions address the practical points Indonesian account holders usually check before sending a request. Each answer follows our Privacy Policy scope, including account creation, mobile sign-in, cookies, payment references, and the steps used to confirm a request.

It covers account details, phone verification, sign-in and device records, cookies, support messages, and payment references connected with DANA, OVO, GoPay, QRIS, bank transfer, or virtual account activity.

We use your phone detail to create or verify account access and to help confirm that a privacy request comes from you. We do not ask for your wallet PIN or password through support.

Open the signed-in account help path and ask for a data copy. State the registered phone detail and the categories you want checked; we may complete an identity check before replying.

Yes, you can ask for a correction through account help. Name the specific account field or payment reference, explain the needed change, and provide supporting context without sharing secret wallet credentials.

Yes. The policy covers references linked to DANA, QRIS, OVO, GoPay, bank transfer, and virtual account activity, so we can match a payment status question with the correct account record.

Cookies and browser signals can remember session preferences and help identify unusual sign-ins. If you block them in your mobile browser, you may need to sign in again or confirm certain account steps.

Account access and related activity depends on local law. Where local law permits, you can use our signed-in support path to ask about data access, correction, retention, or the purpose of a record.

Open the lux88 Privacy Policy

Browse Your Privacy Support Route

Switch Through Your Privacy Choices

Account details

Cookies and browser signals

Wallet references

Account protection

Retention periods

Requesting changes

Check Common Privacy Policy Answers

01 What does the lux88 Privacy Policy cover?

02 Why does lux88 need my phone number?

03 How can I request my lux88 account data?

04 Can I correct data held under the Privacy Policy?

05 Does the Privacy Policy cover DANA and QRIS records?

06 How do cookies affect my lux88 mobile session?

07 Where does the Privacy Policy apply in Indonesia?

Related Pages