Reference

amavid5d Privacy Policy For Your Account

Our Privacy Policy explains how we collect, use and protect the details connected with your amavid5d account, including phone verification, device access and wallet activity.

Account clarityWallet recordsDevice controlsPolicy requests
amavid5d amavid5d Privacy Policy For Your Account
CONTACT PATH

Ask About Your Privacy Policy

A direct support request gives you a practical route when a privacy question concerns your login, wallet status or account record.

Account request Use the contact path attached to your account when you want to ask what…
Correction request If your name, phone detail or account setting needs correction, tell us which field…
Wallet query For a privacy question tied to a payment record, send the rail name and…
DATA HANDLING

How We Handle Account Records

We keep this policy practical by connecting each data use to an account step you can recognise.

Account security

Phone verification is used before account access so we can connect a sign-in with the account holder’s registered contact.

Payment references

A wallet or bank record normally contains a reference, amount status and account link rather than your secret credential.

Cookies

Browser cookies can keep a session active, remember a language or preserve a page setting.

Device access

We record limited device and browser signals when you open the account on a phone, tablet or desktop.

Retention choices

We keep account, contact and transaction records only while they support account service, dispute handling, security checks or duties that…

Your request

You may ask us to access, correct or delete eligible personal data through the account contact path.

Privacy Policy Answers For Indonesia

These Privacy Policy answers address the account and device questions we expect from people opening amavid5d in Indonesia. They focus on the records you create through phone verification, wallet checks and support contact, rather than describing unrelated lobby functions. If your question is not covered, use the account contact path and describe the exact record or access event you want us to check.

The Privacy Policy covers account details, phone verification, login and device signals, cookie preferences, support messages and payment references. It explains why we use those records, how long they may remain and how you can ask for access, correction or deletion where local law permits.

Yes. The Privacy Policy covers the transaction references connected with DANA, OVO, GoPay and QRIS activity. We may use a reference and status to match a payment step, but you should not send us a wallet password, PIN or one-time code through support.

We use the phone number linked to your account for phone verification, account access checks and support ownership checks. If you ask us to change or remove it, we may first confirm that you control the account so another person cannot take over your records.

You can request a correction through the account contact path. Tell us which account field is inaccurate and provide the replacement detail. We may retain the earlier entry when it is needed for a transaction trail, security check or duty that applies where local law permits.

It does. Cookies can maintain a session or remember a setting when you use the mobile browser path. Browser controls let you clear or block them. After that change, you may need to sign in again, and some saved preferences may not return.

We retain each record while it supports account service, a support query, a payment dispute, an access check or an applicable legal duty. You can ask which data remains and the reason. We assess older records when those purposes no longer apply.

Send a deletion request through the account contact path and identify the phone detail linked to your account. We may verify ownership before acting. Some account, payment or security records may need to remain for a defined period, and we will explain that limit.