Reference

Privacy Policy for amavi88 Account Access

Dragon Tiger, Rocket Crash and Fish Hunter are covered by a clear Privacy Policy that explains what we collect before you reach the lobby.

Clear data purposesPhone check detailsWallet record accessCookie choices
amavi88 Privacy Policy for amavi88 Account Access
POLICY HELP

Privacy Questions Around Login and Wallets

A clear contact route helps when a Privacy Policy question is tied to a login, phone check or wallet receipt. We ask you to contact support from the account path shown on amavi88, so our team can match your request with the correct account record. If you are in Jakarta, include the wallet name, device path and approximate transaction time; access remains where local law permits.

Team online

Account contact path

Use the support route connected to your account when asking what phone, device or login details are held. This lets us check the request against your account without asking you to post private data publicly.

Wallet record request

For a DANA, OVO, GoPay or QRIS query, share the visible receipt reference and wallet name through support. We can then explain the stored status and the purpose attached to that record.

Access assistance

If policy access stalls after phone verification, tell us whether you used a mobile browser or desktop path. Support can direct the request while keeping eligibility subject to local law.

DATA PRACTICE

How We Protect Your Account Data

We keep the Privacy Policy practical by linking each data use to an account action: access, verification, wallet matching or support.

Data handling

We use account, phone and transaction details for the stated service purpose, such as checking access or matching a QRIS receipt. We avoid asking for unrelated details through the account contact route.

Cookie controls

Cookies and similar browser storage can keep your session path consistent and help us understand security events. You can review browser controls on mobile or desktop if you want to limit stored preferences.

Account security

Phone verification and device signals help us identify an account request before access is granted. Keep your login details private and contact support if a device path appears unfamiliar.

Retention timing

We retain account and wallet records only for the period needed for the stated service, security checks and account queries. A request can ask us to explain why a record remains available.

Who to contact

Our support contact route handles Privacy Policy questions about account fields, cookies, phone checks and DANA, OVO, GoPay or QRIS records. Include enough context for us to locate the correct entry.

Requesting changes

You can ask us to correct an inaccurate account detail or clarify a stored transaction reference through support. We may need phone verification before changing records linked to your access.

Privacy Policy Answers for Indonesian Accounts

These Privacy Policy answers focus on the searches we hear around account creation, wallet records and device access. Each response describes the practical step you can take, while availability and eligibility remain where local law permits. If your case involves a specific receipt or phone check, use the account-linked support path.

It covers account details, phone verification, cookies, device signals, wallet references and support requests. It also explains why transaction records from DANA, OVO, GoPay or QRIS may be retained.

Phone verification helps connect an access request with the correct account and supports account recovery. We may use the result as a security signal before allowing the requested account path.

Yes. The Privacy Policy covers wallet references, receipt details, status and timing used to match DANA or QRIS activity with your account and answer a support request.

You can request a correction through the account-linked support route. We may ask for phone verification before changing details, especially where the requested change affects login or wallet records.

Cookies can preserve your session path and support security checks on a mobile browser. Your browser settings provide controls for stored preferences, while essential access may still require session data.

We retain wallet records for the period needed for the stated service, account security and receipt questions. Support can explain the reason for a particular record when you provide its reference.

Use the support contact path connected to your account and state whether your request concerns access, correction, cookies or deletion. We will assess it under the applicable local law.