Reference

Open avatar4d Privacy Policy Before Account Access

avatar4d Privacy Policy explains what we collect when you open an account, sign in from a mobile browser, or check DANA and QRIS status.

Clear data purposesCookie choicesAccount contact pathIndonesia access context
Explore Our Lobby Read FAQ
avatar4d Open avatar4d Privacy Policy Before Account Access
CONTACT ROUTES

Use Your Account Path for Privacy Help

A privacy question should reach the team with enough account context to act on it. Start from the support route connected to your account and include the email or phone detail used for access, the request you want handled, and any relevant transaction reference. We can then separate a cookie question from a wallet-status question without asking you to send a password.

Team online

Account data request

Use the account support path to ask which personal details we hold about you. Include your registered contact detail and a clear request for a copy, correction, or explanation of the record, while keeping passwords and one-time codes out of your message.

Wallet privacy question

If a DANA, OVO, GoPay, QRIS, bank transfer, or virtual account reference looks unfamiliar, send the transaction reference through account support. We use that reference to locate the record and can explain its purpose without requesting your wallet PIN.

Cookie or device concern

When a cookie setting or mobile-browser detail concerns you, tell us the device path you used, such as Android browser or desktop browser, and describe the page behaviour. We can connect the question to the right privacy record without asking for unrelated account details.

DATA PRACTICE

Check How avatar4d Handles Your Records

We keep this policy practical by describing the records created during ordinary account use and the controls around them.

Account data

We may hold your registration details, contact information, phone verification result, sign-in history, and messages related to account support. These records let us identify the correct account when you ask for a copy, correction, access explanation, or removal request.

Cookie controls

Cookies can retain a setting, support a sign-in session, or show us whether a page works correctly on your device. You can adjust available browser controls, and you can ask support what a cookie-related record is used for.

Account security

Phone verification and sign-in signals help us protect the account from access that does not match your normal activity. Never send a password, wallet PIN, or one-time code in a privacy request; we only need enough detail to identify the record.

Payment references

A DANA, OVO, GoPay, QRIS, bank transfer, or virtual account reference may be stored with account activity. We use it to reconcile status and investigate a question, not to request or display your private wallet credentials.

Record retention

We keep personal records while they support account operation, security checks, payment reconciliation, disputes, or legal duties. When a record no longer serves one of those purposes, we remove it or use a form that no longer identifies you.

Policy requests

To ask for access, correction, deletion, or a privacy explanation, use the support route linked with your account. State the request plainly and provide your registered contact detail so we can verify the account without collecting unnecessary new data.

Find Privacy Policy Answers for Your Account

These Privacy Policy answers address the account and device questions we expect from Indonesian customers before they open access. Each answer points to a practical next step, from checking cookies on a mobile browser to asking about a DANA or QRIS transaction reference. Where access or eligibility matters, it depends on local law.

The avatar4d Privacy Policy covers registration details, contact data, phone verification, sign-in events, device signals, cookies, payment references, support messages, and retention. It explains why we use each category, how we protect account access, and how you can ask about, correct, or remove records where local law permits.

Use the support route connected to your avatar4d account and request a copy of your personal records. Include the registered email or phone detail and describe the request clearly. Do not send a password, wallet PIN, or one-time code. We may need to verify account ownership before responding.

Yes. The Privacy Policy covers transaction references linked to DANA, QRIS, OVO, GoPay, bank transfer, or virtual account activity. We use those references to match status and investigate account questions. We do not need your wallet PIN, secret code, or full private wallet credentials for a privacy request.

Cookies can keep a sign-in session active, remember a selected setting, or help us identify whether an account page works on Android browser, another mobile browser, or desktop. You can adjust browser controls, and you can contact account support if you want a cookie-related use explained.

You can ask us to correct inaccurate account data through the support path linked to your account. State which record is wrong and provide the current detail. We may check phone verification or another account step before changing it, so the correction reaches the right account.

We retain personal data while it is needed for account operation, sign-in security, payment reconciliation, dispute handling, or legal duties. After that purpose ends, we remove the record or make it non-identifying. The period can depend on the record and local requirements, so support can explain a specific request.

You can send a deletion request through account support, and we will assess it under the Privacy Policy and applicable local requirements. Some records may need to remain for security, payment reconciliation, disputes, or legal duties. Access depends on local law, and we will explain the outcome for your request.

Related Pages

avatar4d Indonesia Sic Bo affabola About Us FAQ