Reference

Privacy Policy For Your avatar66 Account

The avatar66 Privacy Policy explains how we collect, use and protect details connected with your account, device and wallet activity.

Clear data purposesWallet status checksAccount access controlsCookie choices
avatar66 Privacy Policy For Your avatar66 Account
PRIVACY HELP

Get Help With Account Data Requests

A clear contact path matters when your account data or wallet status needs attention.

Account support path Use the signed-in support route when you want to ask about your Privacy Policy…
Wallet status check If a DANA, OVO, GoPay or QRIS reference appears incorrectly, contact us through the…
Access concern When sign-in or phone verification stops you from reaching your privacy settings, tell us…
DATA CONTROLS

What We Do With Your Account Details

Privacy at avatar66 is managed through ordinary account controls rather than vague promises. We separate details needed for sign-in, wallet matching, security review and support handling, then limit use to the stated…

Data we receive

We may receive your account contact details, phone verification result, sign-in events, device or browser signals, support messages and payment references. For DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity, we use the reference needed to identify the related account action.

Why we use it

We use account data to open and secure your profile, connect a wallet status to the correct request, answer support messages and identify activity that may put an account at risk. We do not treat a payment reference as a reason to collect unrelated personal details.

Cookies and browser choices

Cookies and similar browser storage can remember sign-in preferences, security steps and page choices. You can adjust browser controls or clear stored data, although doing so may require phone verification again before account access continues.

Account security

We may compare a new device, sign-in pattern or phone verification result with earlier account activity. If a signal needs checking, we may pause the requested account action until the identity details are consistent. Never share your password, PIN or one-time code with anyone.

Retention periods

We keep different records for different periods, based on their purpose, security needs and applicable legal duties. Payment matching records may need to remain available longer than a temporary browser preference. The Privacy Policy explains the current retention approach and its limits.

Your requested changes

You can ask us to access, correct or clarify personal data connected with your account through the signed-in support route. Tell us which record is wrong and provide enough account detail for verification; we may need to confirm your identity before making a change.

Privacy Policy Answers For Indonesia

These Privacy Policy answers cover the searches we hear most often from people preparing an avatar66 account. Each answer stays focused on personal data, cookies, payment references, account access and contact steps. If a request depends on a local eligibility rule, we will apply the relevant requirement where local law permits and explain the next account step.

The avatar66 Privacy Policy covers account details, phone verification, device and browser signals, cookies, support messages and payment references. It explains why we use each category, how security checks work, how long records may remain and how you can request access or correction.

We may record references connected with DANA, OVO, GoPay, QRIS, bank transfer or a virtual account when they relate to an account action. We use those references for matching, status checks, security and support; we do not need your wallet PIN or password.

Sign in and use the account support route, then identify the record you believe is wrong. Include the phone number linked to your account and a clear correction request. We may confirm your identity first, so changes are made against the correct profile.

Yes. The Privacy Policy explains how cookies or browser storage can remember security steps and page choices on a mobile browser. You can clear or restrict them through your browser controls, but a later sign-in may require phone verification again.

You can request access to personal data connected with your avatar66 account through the signed-in support path. Describe the records you need, such as account details or payment references. We may limit or format the response where a legal or security rule requires it.

Retention depends on the purpose of the record, security needs and applicable legal duties. A payment reference used to match DANA, QRIS, bank transfer or virtual account activity may remain longer than a temporary cookie. The current Privacy Policy sets out the relevant approach.

Use the support route from the sign-in or account page and explain whether the issue is the mobile browser, desktop browser or phone verification step. Do not send a password, PIN or one-time code. Account access depends on local law and where local law permits.