Reference

aster123 Privacy Policy For Your Account

aster123 Privacy Policy explains how we handle the details connected with your account, device access and wallet activity before you enter the lobby.

Account dataWallet referencesDevice controlsPolicy requests
aster123 aster123 Privacy Policy For Your Account
CONTACT PATHS

Ask About Your Privacy Policy Records

A direct request helps us locate the right account record without exposing details to the wrong person.

Account request Send a Privacy Policy question from your signed-in account path when possible. Include the phone number linked to access and identify whether you want a copy, correction or explanation of a stored account detail. We check the request against the account before sharing personal data.
Wallet record For a DANA, OVO, GoPay or QRIS question, provide the payment reference and approximate transaction time rather than sending a full wallet screenshot. This lets us trace status, match the account and limit the personal material included in your request.
Access concern If a phone, browser or account session no longer opens, tell us which device path failed and whether the issue followed phone verification. We can review the security event and explain the next account step without asking for your password or wallet PIN.
DATA HANDLING

What Our Privacy Process Covers

Privacy work follows the same practical path as your account activity: we collect only what helps us provide access, reconcile a payment, protect a session or answer a request.

Account creation

When you open an account, we use the supplied contact details and phone verification result to create and protect your login. The account path may also record when verification succeeds or fails, helping us distinguish a genuine access request from repeated attempts on the same number.

Payment matching

Selecting DANA, OVO, GoPay, QRIS, bank transfer or a virtual account creates payment-related records such as reference, status and time. We use those records to reconcile the cashier request and investigate a missing status, while avoiding storage of your wallet PIN.

Cookie choices

Cookies and similar session tools help keep your signed-in path working, remember temporary settings and detect unusual activity. They can connect a browser session with an account event, but they do not replace your password or give us access to your personal wallet credentials.

Device security

A phone, tablet or desktop browser may produce device and session signals when you sign in. We use these signals to check account security, investigate an unexpected login and guide the next verification step; they are not used to request your private wallet PIN.

Retention periods

We retain account, payment and support records for as long as needed for the stated service purpose, security checks or legal duties. When a record is no longer needed for those purposes, our handling process removes it, anonymises it or restricts further use.

Change requests

You can ask us to explain, correct or update personal data held for your account where local law permits. Send the request through the account support path, identify the record concerned and complete any identity check needed to prevent another person from changing your details.

Privacy Policy Answers For Indonesia

These Privacy Policy answers address the account questions we expect before you use aster123 from Indonesia. They cover phone verification, wallet references, browser sessions, game records and requests to see or change stored data. Where a question involves eligibility or access, the answer depends on local law and the checks required for the account.

The Privacy Policy covers account details, phone verification, device and session signals, payment references, support messages and records connected with lobby activity. It explains why we use each category, how we protect it, when retention ends and how you can request access or correction.

We use phone verification to create an account, confirm that an access request matches the account holder and investigate repeated or unusual login attempts. The result and related security event may be retained as an account record, while your password and wallet PIN remain private.

No. When you use DANA, OVO, GoPay or QRIS, we handle the reference, status, time and account connection needed to reconcile the request. We do not need your wallet PIN to check a payment record, and you should never include it in a support message.

Device type, browser details and session signals help us keep your account path working and identify unusual access. If a mobile or desktop login changes unexpectedly, those records support an account check. They are used for access security and service operation, not for collecting wallet credentials.

Where local law permits, you may request an explanation, copy or correction of personal data connected with your account. Use the signed-in support path when possible, name the record or payment reference involved and complete an identity check before we disclose or change account information.

We retain payment references, support records and relevant game activity for the period needed to operate the account, resolve a status question, protect security or meet legal duties. Once those purposes end, we remove, anonymise or restrict the record according to our handling process.

Access and eligibility depends on local law. The Privacy Policy still explains our handling of account and payment data, but the account path may require location, phone or identity checks before access. If you are unsure, contact support through the available account route before submitting personal data.