Reference

amd388 Privacy Policy For Your Account

amd388 Privacy Policy explains what account details we collect, why we use them, and how you can ask us to check or change those records.

Clear data purposesWallet record controlsPhone verification detailsIndonesia access wording
amd388 amd388 Privacy Policy For Your Account
CONTACT PATHS

Privacy Help For Wallet Questions

A direct contact path helps you ask about Privacy Policy records without explaining the same issue repeatedly. Start from the account support route and include the phone number linked to your account, the relevant date, and the payment reference if your question concerns DANA, OVO, GoPay or QRIS. We use those details to locate the correct record, while you should avoid sending a password or full payment credentials.

Team online

Account data request

Use the support contact path linked from your account area to ask what personal details we hold. Include your registered phone number and the specific record you want checked, such as a phone verification event or a sign-in device entry.

Wallet record query

For a DANA, OVO, GoPay or QRIS question, attach the payment date and visible reference rather than a password or complete wallet credentials. We can compare the account record with the receipt status and explain what was stored for reconciliation.

Policy correction route

If a Privacy Policy record looks incorrect, tell us which field needs attention and why. We may ask for a fresh phone verification step before changing account data, helping us avoid applying a request to the wrong amd388 account.

DATA PRACTICES

Account Records And Cookie Choices

Privacy work is practical: we separate account administration from the activity needed to keep sign-in and payment records consistent.

Data we collect

When you open an account, we may collect your phone number, account details, verification events, device information, sign-in activity and…

Why records are used

A phone verification record supports account security, while a DANA or QRIS reference helps us identify a payment status.

Cookies and sessions

Cookies may keep your session active, remember a selected setting or help us understand whether a sign-in step completed.

Account protection

We use sign-in events, device signals and phone verification to help detect an account access problem.

Retention approach

We keep account, payment and support records for as long as they serve account administration, security, dispute handling or a…

Change or deletion request

You can ask us to correct an inaccurate detail, explain a stored record or consider a deletion request through support.

Privacy Policy Answers For amd388

These Privacy Policy answers address the account questions you are most likely to have before opening an account or checking a wallet record. They explain how to contact us, what may be stored during mobile and desktop use, and why a verification step can be necessary. If your situation is not covered, use the account support route with the smallest useful set of details.

The amd388 Privacy Policy covers account details, phone verification, sign-in and device events, cookies, support messages, and payment references linked to DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity. It also explains purposes, retention, security handling and ways to request a correction.

We use your phone number to identify the account you are asking about and to complete phone verification before account access. It can also help us investigate a sign-in problem or apply a Privacy Policy correction to the right record instead of another account.

We may store payment references, status information and account links needed to reconcile a DANA or QRIS transaction. The same approach can apply to OVO, GoPay, bank transfer and virtual account records. Do not send a password or complete wallet credentials in a support message.

Use the support contact path linked from your account area and state whether you want a record explained, copied where available, or corrected. Include your registered phone number and the relevant date. We may request phone verification before discussing account-specific Privacy Policy data.

Retention depends on why the record exists. Account, payment and support details may remain for administration, security checks, disputes or legal duties. When those purposes end, we aim to remove the data or reduce its identifying detail where practical under the applicable rules.

Cookies may maintain a session or remember a setting when you use a mobile browser to open Aviator Mobile Play or another lobby area. Clearing them through your browser can remove that session choice, so you may need to sign in and complete phone verification again.

Yes. Send your question through the account support route and explain the access or eligibility concern. Our handling of the request and the service itself depends on local law, and access is provided where local law permits. We will use the details needed to answer your request.