Reference

Privacy Policy for DANA and Account Data

Our Privacy Policy explains how alexsisslot handles your account details, device signals and wallet records when you open an account or access the lobby.

Account dataWallet recordsDevice choicesPolicy requests
alexsisslot Privacy Policy for DANA and Account Data
CONTACT ROUTES

Policy Help for Account Access

A clear contact route matters when you want to understand a privacy choice or an account record.

Account request Use the account help route when you want to ask what personal data is connected with your sign-in. Include the account phone number and the subject of your Privacy Policy request so we can check the correct record before replying.
Wallet record For a DANA, OVO, GoPay or QRIS question, share the payment reference rather than a wallet password or one-time code. We use the reference to check status and keep sensitive wallet credentials outside the support exchange.
Device session If a mobile or desktop session looks unfamiliar, contact account support and mention the device path and sign-in time. We can use those details to review access activity and explain the security step required before changes are made.
SIX DATA CONTROLS

Six Data Controls Inside alexsisslot

We handle privacy through specific account routines rather than broad promises. The controls below explain what happens around sign-in, cookies, payment references, retention and change requests.

Account security

Before we discuss account data or change a phone detail, we may ask you to complete the clear phone verification step. This helps separate the account holder from an unapproved request and keeps sign-in records tied to the correct profile.

Cookie controls

Cookies and similar device signals help keep a signed-in session working and remember selected access settings. You can manage browser permissions on your phone or desktop, although switching them off may require you to verify the account again.

Payment references

When you use DANA, OVO, GoPay or QRIS, we use transaction references and status details to connect the payment event with your account. We do not ask support to receive your wallet password, PIN or one-time code.

Device activity

A login from a new browser or mobile device can create a security record such as time, browser type and general device signal. These details help us investigate an access question without treating your device identity as a public profile.

Data retention

We keep account and transaction records only for the period needed for account operation, security checks, dispute handling and applicable legal duties. When a record no longer serves those purposes, our retention process removes or de-identifies it where appropriate.

Change requests

You can ask us to correct eligible account data, explain a recorded detail or remove data where local law permits. Send the request through account support; we may verify ownership, describe any required exception and confirm the action taken.

Privacy Policy Questions About Your Account

These answers address the privacy questions we expect you to ask before opening an account or linking an Indonesian wallet. They focus on the records created by sign-in, phone verification, lobby access and payment status checks. If your situation is not listed, use the policy contact route and include enough account detail for us to locate the correct record.

It covers account details, phone verification, device signals, cookie settings, support messages and payment references connected with your use of the site. It also explains retention, security checks and how to request correction or removal where local law permits.

Your phone number supports the account path and the verification step before access or account changes. It helps us identify the correct profile when you ask about a wallet status, a device session or a Privacy Policy request.

Yes. The Privacy Policy covers the transaction references and status details created when you use DANA, OVO, GoPay or QRIS. Those records help match a payment event to your account; support should never receive your wallet password, PIN or one-time code.

You can contact account support with your account phone number and ask for a data access explanation. We may verify ownership first. Where local law permits, we will describe the eligible records and explain any legal or security reason for withholding a detail.

Send a policy request through the account support route and identify the detail you believe is wrong, such as a phone record or profile entry. After ownership checks, we will review the request and confirm whether the correction can be made.

We retain records for account operation, security review, dispute handling and applicable legal duties. The period depends on the record and its purpose. When retention is no longer needed, we remove or de-identify the data where appropriate.

The policy applies to your account while access depends on local law. If a local rule affects eligibility, data handling or a request, we will explain the relevant restriction through the account support route rather than asking you to guess.