Reference

Open alexsi Privacy Policy before account access

alexsi Privacy Policy explains how we use account, device and payment details when you open an account or access the lobby.

Account dataWallet recordsCookie choicesPhone verification
Explore Our Lobby Read FAQ
alexsi Open alexsi Privacy Policy before account access
CONTACT ROUTE

Check policy help beside account support

A clear contact route helps when a Privacy Policy question meets a login or wallet-status issue. Start from account help and include the email or phone detail linked to your account, the relevant date, and a payment reference if your question concerns DANA or QRIS. We use those details to locate the correct record without asking you to send a password or full wallet credentials. If you are in Semarang, the same policy contact path applies as elsewhere in Indonesia.

Team online

Policy questions

Use the account help route to ask how we collect, use or retain your data. Include the account contact detail you can verify so we can match the request safely without requesting your password.

Wallet records

For DANA, OVO, GoPay or QRIS questions, provide the payment date and visible reference number. We can check the account record and status without asking you to share a PIN, one-time code or complete wallet credentials.

Access concerns

If a phone verification or sign-in check blocks a privacy request, tell us the device path and account contact detail. We may ask for a safe account step before changing data or releasing account-specific details.

DATA PRACTICE

Secure your alexsi data choices

We treat the Privacy Policy as an account control, not a page to read once and forget. Our handling follows the purpose of each record: account security, wallet reconciliation, service support or…

Purpose-based use

We connect account details to clear tasks such as phone verification, sign-in protection, payment matching and support. We do not need a broad explanation from you; each request is assessed against the record and purpose involved.

Cookie controls

Cookies and browser storage can keep a session active and support security checks. You can adjust browser settings, but switching them off may require another sign-in or remove saved preferences during your next account visit.

Account security

Keep your phone, password and one-time codes private. Before we discuss account-specific data or change a contact detail, we may use the existing phone verification step to confirm that the request comes from you.

Retention periods

We keep each category only for the period needed for its stated purpose, payment matching, dispute handling, security review or a legal duty. When that period ends, the record is removed or kept without direct account use where required.

Correction requests

If your name, phone detail or another account field is inaccurate, contact us through account help and identify the field you want changed. We may request a matching account step before applying the correction.

Data access requests

You may ask what account or transaction data is connected with your profile and why it is used. Send the request through the policy contact path; we will confirm ownership before sharing account-specific material.

Find Privacy Policy answers for your account

These Privacy Policy answers cover the account questions we expect before phone verification, a wallet check or a request to change personal data. We keep each answer tied to an actual alexsi step, including browser access, payment references and account help. If your situation is not covered, use the policy contact route and avoid sending passwords, wallet PINs or one-time codes in your message.

It covers account details, phone verification, sign-in events, device signals, cookies and payment references connected with DANA, OVO, GoPay, QRIS, bank transfer or a virtual account. It also explains purposes, retention, security steps and ways to request access or correction.

Phone verification helps connect an account request to you and reduces the chance that another person changes contact details or asks for account data. We may use that step before discussing account-specific records or completing a data-change request.

Yes. The Privacy Policy covers payment references and status details needed to match a DANA or QRIS transaction with your account, investigate a receipt question and resolve a wallet-status issue. We do not ask you to send a wallet PIN or one-time code.

Use the account help or policy contact route and state that you want access to your personal data. Include the account email or phone detail you can verify. We may ask for an account security step before sharing records connected with your profile.

Yes. Send the correction request through account help, identify the field that is wrong and provide the accurate replacement. We may confirm ownership through phone verification, then assess the request against the Privacy Policy and applicable local requirements.

The period depends on the purpose and applicable requirement. Payment references may be retained for matching, disputes or legal duties, while device and cookie records support security for their useful period. The Privacy Policy explains that records are removed or restricted when that period ends.

Use the policy contact path linked from account help and mention that your question concerns Privacy Policy access in Indonesia. Eligibility depends on local law. Add your verified account contact detail and avoid including passwords, wallet PINs or one-time codes.

Related Pages

alexsi Indonesia esportbet Live Roulette Account information Access guide