Reference

alexis5000 Privacy Policy for Your Account

Clear records help you understand what happens when you verify a phone, open Live Baccarat Elite, or use DANA, OVO, GoPay and QRIS through your account.

Phone verificationWallet recordsCookie choicesIndonesia access
alexis5000 alexis5000 Privacy Policy for Your Account
CONTACT PATHS

Get Policy Help Beside Cashier Access

A clear contact route matters when you want to ask what data we hold or why an account record appears. Open the account help path beside the cashier area and include the phone number linked to your account, the relevant date, and your request in plain English. We use those details to locate the right record without asking you to send a password or full wallet credentials.

Team online

Account data request

Use the support contact shown inside your account to ask for a copy, correction or explanation of personal data. Include your verified phone number and the subject of your request so we can match it to the correct account record.

Wallet record question

If a DANA, OVO, GoPay or QRIS reference looks unfamiliar, send the receipt reference and date through account help. We can check the related account event while keeping your wallet PIN, password and complete payment credentials out of the message.

Access concern

When a phone verification or login record needs attention, use the help path near the cashier area rather than opening another account. We may ask for account identifiers to confirm the request before discussing private account details.

DATA PRACTICE

How We Handle Account Data

Privacy work follows the same account steps you see in the lobby: identify the account, check the relevant event, and limit the response to what is needed.

Account details

We use contact and verification details to create the correct account record, confirm ownership during support, and connect your account with its own lobby and wallet history. We do not need your password or wallet PIN when handling an ordinary privacy question.

Device and cookies

Your browser may store cookies or similar signals that remember a session, support security checks and help us understand whether a login comes from a familiar device. You can manage browser cookie settings, though some account steps may then need to run again.

Account security

Phone verification, login records and device signals help us check unusual access before private account details are discussed. Never place a password, wallet PIN or complete card or bank credential in a support message; we use account identifiers instead.

Retention approach

We retain account, support and transaction records only while they serve an account, security, dispute or legal purpose. When a record is no longer needed for those purposes, our handling process is to remove it or separate it from direct account identification.

Change request

You can ask us to correct outdated contact details or clarify a record through the support contact inside your account. We may verify your phone number first, then explain the result, any required step, and whether another service provider controls part of the record.

Disclosure boundaries

We share data only when needed for an account service, security response, payment record check or legal obligation. A DANA, OVO, GoPay, QRIS, bank transfer or virtual account provider may handle its own transaction data under its separate privacy terms.

Privacy Policy Questions for Indonesia

These answers address the searches we hear most often before an account is opened. They focus on alexis5000 account records, Indonesian wallet references, phone verification, device activity and requests sent through the available account support path. For a case involving local eligibility, the applicable answer depends on local law.

It covers personal details, phone verification, login and device signals, cookies, lobby activity, support messages and transaction references connected with your account. It also explains why we use those records, how long we retain them, and how you can ask for access or correction.

Yes, it explains how we handle references created when you use DANA, QRIS, OVO, GoPay, bank transfer or a virtual account. The payment provider may separately control parts of the transaction record, so its own privacy terms can apply alongside our policy.

Phone verification helps us connect a request or login to the correct account before private details are discussed. It also supports account security when device or login activity looks unusual. We do not ask you to place a password or wallet PIN in support messages.

Open the support contact shown inside your account and state whether you want access, correction or an explanation. Add your verified phone number and the relevant date or transaction reference. We may confirm ownership first, then respond through the account support route.

Cookies and similar device signals can support a mobile session, security checks and account continuity from login to the lobby. You can change browser settings, but removing cookies may require phone verification or another login step when you return.

We keep records while they are needed for account operation, security checks, payment questions, disputes or legal duties. The period can differ by record type. When the purpose ends, we remove the record or separate it from direct account identification where practical.

Access and eligibility depends on local law. Where local law permits, you can read the policy and use the account path available for your location. If your access is restricted, contact support through the account route for a privacy question rather than opening another account.