Reference

luxury login Privacy Policy for Indonesia

The luxury login Privacy Policy tells you what account, device and wallet details we collect, why we use them, and how you can ask about them.

Account clarityWallet recordsCookie choicesPrivacy requests
luxury login luxury login Privacy Policy for Indonesia
PRIVACY HELP ROUTES

Privacy support beside wallet status

A clear support route helps when you want to ask about a record rather than a wallet result.

Account data request Use the support link inside your account area to ask which personal details we hold. Include your account email or verified phone number, and we will use that detail to locate the request without requesting your wallet PIN.
Wallet reference query For DANA, OVO, GoPay, QRIS, bank transfer or virtual account records, share the transaction reference and date only. We can check the privacy record connected to the status while keeping your password and wallet credentials out of the message.
Access problem If you cannot reach the account page, mention whether you used a mobile browser or desktop browser and explain the privacy issue in plain words. We will use the support path available on the site to route your request for follow-up.
RECORDS AND CONTROLS

How we handle account privacy

Privacy work is tied to practical account events: phone verification, sign-in checks, wallet references and messages sent to support.

Data we receive

We may receive your account contact details, phone verification result, sign-in time, device signals, support messages and payment references. DANA, OVO, GoPay, QRIS and bank transfer names help us connect a status update with the correct account.

Why records are used

We use account and access records to provide sign-in, answer support questions, check unusual activity and connect wallet status to your account. We do not use a QRIS reference as a reason to request your private wallet password.

Cookies and devices

Cookies and device signals can keep a session working and help identify repeated sign-in attempts. Your mobile browser and desktop browser may create different session records, so tell support which path you used when asking about a cookie.

Account protection

Phone verification is part of the access record before you enter the account area. Keep your sign-in details private and contact support if a device, phone number or session appears unfamiliar; we can then review the related access trail.

How long we keep data

We retain records for the period needed to provide account support, resolve payment references, protect access or meet a legal duty. When a record is no longer needed for those purposes, our handling process moves it toward deletion or restriction.

Changes and requests

You may ask for a copy, correction or eligible removal of personal details through the support route. Identify your account with its email or verified phone number, describe the requested change, and we will respond through the contact path you provide.

Privacy Policy answers for luxury login

These Privacy Policy answers focus on the searches we expect from an Indonesian account holder: what is collected, how wallet references are handled, how cookies affect a mobile session, and how to request a change. We keep the route practical, so you can prepare the account email, verified phone number or transaction reference needed for a useful reply.

It covers account details, phone verification, device signals, cookies, support messages, access records and payment references. The notice explains why we use each type, how long we may retain it, and how you can ask about, correct or remove eligible personal details.

No. Our Privacy Policy distinguishes a wallet status or transaction reference from your private credential. When you ask about DANA, OVO, GoPay or QRIS activity, send the reference and date only; do not send a PIN, password or full security code.

Use the support link in your account area and provide the email or verified phone number connected to the account. State that you are making a data request and specify whether you want access, correction or another eligible action under the Privacy Policy.

Cookies can keep a mobile browser session active and help us identify repeated access attempts. They may differ from desktop records. You can ask support what cookie or device detail relates to your session and request clarification about its use under the Privacy Policy.

We keep payment references only for the operational, security or legal purpose connected with them, such as matching a wallet status or resolving an account question. Retention can vary by record type, and you can ask support to explain the period applying to your details.

Yes, you can ask us to correct an eligible account detail through the support route. Include the existing email or verified phone number, describe the correction, and tell us how to reach you. We may need an account check before changing the record.

Yes. Account access and eligibility depends on local law, and we apply this Privacy Policy where local law permits. If a legal rule affects a request or account record, support can explain the applicable route without asking for unnecessary wallet information.