Reference

aster88 Privacy Policy, Clearly Explained

aster88 Privacy Policy sets out how we collect, use and protect the account details connected with your access, including login records and DANA, OVO, GoPay or QRIS payment…

Account dataWallet referencesCookie choicesAccess requests
aster88 aster88 Privacy Policy, Clearly Explained
CONTACT ROUTES

Get Privacy Help Beside Account Support

A privacy question should not require you to search through the cashier or lobby. We keep a direct support route available for requests about stored data, cookie settings, phone verification or a wallet reference. When you contact us, include the account identifier and the subject of your request; we may ask for an account step that helps confirm you are asking about your own records.

Team online

Privacy request

Use the contact route shown on our site to ask what account or device data we hold. Include your registered phone detail where possible so we can locate the correct record.

Wallet question

If a DANA, OVO, GoPay or QRIS reference appears incorrectly, send the transaction reference and approximate date. We use those details to trace the record without requesting your wallet password.

Access check

For a correction or copy request, we may confirm your signed-in account or phone verification step. This protects your records when the request comes from an unfamiliar browser or device.

DATA PRACTICES

Inside aster88 Data Handling

We handle privacy as an account operation, not a separate page that sits away from your daily access.

Account details

We use your account identifier and verified phone detail to sign you in, connect account requests and prevent mistaken changes. We do not need your DANA, OVO, GoPay or QRIS wallet password.

Device signals

A mobile browser or desktop session can create device, browser and security-log details. We use these signals to recognise unusual access and investigate a login that does not match your normal account path.

Cookies

Cookies and similar storage can remember session state, language choices and security steps. You can manage browser storage through your device settings, although clearing it may require phone verification again.

Payment references

Payment-status records may show a rail such as QRIS, DANA or bank transfer, plus a reference and status. These records help reconcile account activity without giving us access to your wallet credentials.

Retention

We retain records for as long as needed for account security, dispute handling, payment reconciliation and legal duties that depend on local law. Retention can vary by record type and request status.

Change requests

You can ask us to correct inaccurate account data, explain a stored record or review a deletion request. Contact support through the site route and we will assess the request under applicable local law.

Questions About Privacy Policy Access

These Privacy Policy answers cover the searches we hear most often before an account is opened or a wallet status is checked. They focus on your records, your device and the steps available through our support route. If your situation is unusual, send the account reference and we will assess the request where local law permits.

The aster88 Privacy Policy covers account details, phone verification, browser and device signals, cookies, support messages, security logs and payment references connected with your account access.

No. We may retain a DANA or QRIS transaction reference and status for reconciliation, but we do not need your wallet password. The same approach applies to OVO, GoPay and bank transfer records.

Device and browser details help us recognise a sign-in pattern, protect phone verification and investigate unusual access. A mobile browser session may create security logs even when you do not save cookies.

Send a request through the contact route on our site with your account identifier and the records you want. We may confirm your signed-in session or phone verification before responding.

Yes. Tell us which account detail is inaccurate and provide the corrected value through support. We may ask for an account step to confirm ownership before changing records where local law permits.

Retention depends on the record and the reason it exists. Security logs, payment references and support messages may remain for account safety, dispute handling or legal duties that depend on local law.

Clearing cookies can remove session preferences and may require you to sign in or complete phone verification again. It does not automatically erase account records held for security or payment reconciliation.