Reference

Legal clarity for your agam88 account

agam88 Legal sets out how we handle account access, wallet activity, personal data and requests to change your details.

Account termsData controlsPayment recordsLocal-law access
agam88 Legal clarity for your agam88 account
CONTACT ROUTES

Where to raise a Legal question

A clear contact route helps you resolve a policy question without guessing which team to reach. We ask you to include the account phone number, the subject of your request and any relevant payment reference, while leaving passwords and wallet PINs out of the message. Our support path can help with account access, data requests, policy wording and payment status records. If you are in Makassar or elsewhere in Indonesia, the same account-focused route applies when local access or eligibility needs clarification.

Team online

Account access

When phone verification or a login check stops your account path, contact support with the registered phone number and a short description of the issue. We use those details to locate the relevant account record without asking you to disclose a password or wallet PIN.

Payment records

For a DANA, OVO, GoPay or QRIS receipt question, send the transaction reference, amount and payment date through the support route. Bank transfer and virtual account queries should include the bank name, such as BCA, BRI, Mandiri or BNI, when that detail is relevant.

Policy requests

If you want a Legal explanation, data correction or account-record request, state the exact action you want us to take. We confirm the request scope first, then explain any identity check or local-law condition needed before making a change.

DATA AND SECURITY

What we do with policy-related records

Legal handling is practical: we connect the account details you submit with security, payment and access records needed to operate the requested account path.

Personal data

We use registration details and the verified phone number to identify the account involved in a Legal request. When you ask us to correct a detail, we may compare the request with the account record before applying a change, so the correction reaches the right account.

Cookies

Cookies and related session data can help keep your login path connected to the correct account on your browser. You can clear browser data or adjust browser settings, but doing so may require another phone verification step before account access continues.

Account security

We treat passwords, phone checks and wallet credentials as separate security details. Do not send a password, PIN or one-time code in a support message. If a login looks unfamiliar, contact us with the time and device path so we can examine the account event.

Payment matching

A payment record is easier to trace when the account name, phone detail and transaction reference align. This applies to DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity; mismatched details may require clarification before the record is updated.

Record retention

We retain account, security and transaction records for the period needed for account administration, legal requests and record checks. If you ask how a particular record is handled, identify its date and type so we can explain the applicable retention process.

Change requests

To request a data correction or ask about account information, contact support from the account-linked route and describe the requested change. We may ask for a phone verification step before action, and access decisions remain dependent on local law.

Answers about agam88 Legal terms

These Legal answers cover the questions we expect you to ask before opening an account or sending a policy request. They focus on account identity, Indonesian payment records, security checks, stored data and access wording. If your situation does not fit these answers, send the specific account or transaction detail through support so we can assess the correct path.

agam88 Legal covers account registration details, phone verification, payment records, data handling, cookies, security checks, retention and requests to correct account information. It also explains that account access depends on local law and may require clarification before the requested account path continues.

Yes. Our Legal wording explains that access depends on local law and that we may apply an account check where local law permits. If you are in Indonesia and need a direct answer about eligibility or access, contact support with the account-linked phone detail.

DANA and QRIS records are treated as transaction references connected to the relevant account path. For a record question, provide the payment date, reference and account-linked phone detail. Do not send your wallet PIN, password or one-time code in a support message.

You can ask us to correct account data by contacting support and naming the exact field that needs review. We may compare your request with the registered phone detail or request a phone verification step before changing the record linked to your account.

Clearing cookies, changing browser data or moving between devices can end a stored session. When that happens, we may require phone verification before account access resumes. This helps connect the new session to the correct account without relying on an old browser record.

Send the payment method, transaction reference, date and amount, using the support route. For OVO, GoPay, bank transfer or a virtual account, include the relevant rail; BCA, BRI, Mandiri and BNI details can help trace a bank record.

Contact support with the account-linked phone detail and identify the record you want us to explain, such as a login event, payment reference or registration field. We can describe the applicable handling process, while any access or change remains subject to local law.