Reference

Privacy Policy for Your amper88 Account

Our Privacy Policy explains what we collect when you open an amper88 account, sign in from a mobile browser, verify your phone, or check DANA and QRIS wallet…

Account recordsWallet detailsCookie choicesAccess requests
amper88 Privacy Policy for Your amper88 Account
CONTACT OPTIONS

How To Ask About Your Privacy Policy

A direct support request gives you a practical way to ask what data we hold, why we use it, or how to correct an account record. Include the phone number linked to your account and a short description of the request, but do not send a wallet PIN or full payment credential. We use the account contact route for privacy questions, and we can check a payment reference when your DANA, OVO, GoPay, or QRIS record needs matching. Requests from Surabaya and other Indonesian locations follow the same privacy process.

Team online

Account contact

Send a privacy request from the contact path connected to your amper88 account. We use your phone verification status to distinguish an account request from an unrelated message, then respond about access, correction, deletion, or the reason a record is retained.

Payment reference

When your question concerns DANA, OVO, GoPay, QRIS, bank transfer, or a virtual account, provide the transaction reference rather than wallet login details. That lets us trace the relevant account record while limiting the payment data included in your request.

Access check

If you cannot sign in on a mobile browser, tell us the phone number on the account and the device path you used. We may ask for a fresh phone verification step before discussing personal data or changing an account contact detail.

DATA PRACTICE

How We Handle Account Privacy

We keep the Privacy Policy practical by tying each data use to an account, payment, support, or security task.

Account data

We use your phone number, verification result, login record, and account preferences to operate the account path. These details help us recognise the account you are asking about, send service-related replies, and prevent a privacy request from being attached to the wrong account.

Payment matching

A DANA, OVO, GoPay, or QRIS reference can be linked to an account record when we need to reconcile a payment status. Bank transfer and virtual account references serve the same purpose; we do not ask you to place wallet passwords in a support message.

Cookies and sessions

Cookies may preserve a sign-in state, remember a selected setting, or help us detect a session that does not look like your usual device path. Browser controls let you clear or restrict cookies, although changing them can require another login or phone verification.

Device signals

We may record browser type, operating system, approximate session timing, and security events when you open the lobby on mobile or desktop. These signals help investigate an access problem without treating your device fingerprint as a public profile or displaying it to other account holders.

Retention decisions

We retain account, payment, and support records while they are needed for service delivery, payment disputes, security checks, or a legal obligation. When a retention reason ends, we delete, aggregate, or anonymise the relevant material according to the record type.

Your requests

You can ask for a copy of personal data, a correction, an explanation of its use, or deletion where the request is permitted. We may verify your phone-linked account first, and some records can remain when a payment dispute, security matter, or legal duty requires retention.

Privacy Policy Questions About amper88

These Privacy Policy answers address the account and wallet questions we hear most often from Indonesian customers. They explain the practical steps for checking a record, changing a detail, managing cookies, and asking about a payment reference. When a request involves access or eligibility, it depends on local law, and our support team will apply the same policy process to mobile and desktop sessions.

We use the phone number attached to your account for account identification, phone verification, and service-related contact. It helps us confirm that a privacy request comes from the right account. We do not ask you to share a wallet PIN or payment password when you contact support.

Yes. The Privacy Policy covers payment references connected with DANA, OVO, GoPay, and QRIS, as well as bank transfer and virtual account references. We use them to match a payment status to the correct account and handle disputes, without requesting your private wallet credentials.

We may record browser type, operating system, session timing, and security events from a mobile or desktop browser. This supports sign-in checks and access investigations. The Privacy Policy treats these as technical account signals, not as a public profile shown to other customers.

Use the account contact route and state whether you want a copy, correction, use explanation, or deletion request. Include the phone number linked to your account, but leave out wallet passwords. We may complete a fresh phone verification step before discussing or changing personal data.

We keep records for the period needed for account service, payment matching, security checks, disputes, or a legal obligation. After that purpose ends, we delete, aggregate, or anonymise the relevant record. A request can be limited when retention is still required for one of those reasons.

You can clear or restrict cookies through your browser settings on mobile or desktop. Some cookie changes may end a saved login state and require you to sign in again or complete phone verification. Our Privacy Policy explains that technical session records support access and security checks.

The policy can be read regardless of your device, but account access and eligibility depend on local law. Where local law permits, you can use the account contact path to ask about your personal data, payment reference, cookie record, or another privacy request.