Reference

agan4d Privacy Policy For Indonesia

Our Privacy Policy explains how agan4d handles the account, wallet and device details connected with your access.

Account dataWallet recordsDevice choicesCookie controls
agan4d agan4d Privacy Policy For Indonesia
PRIVACY HELP PATH

Contact Help For Wallet Data Questions

Questions about the Privacy Policy should reach the same account-help route used for login and cashier status concerns.

Account contact Use the support contact linked from your account area when you need to ask…
Cashier reference For DANA, OVO, GoPay, QRIS, bank transfer or virtual account questions, include the cashier…
Change request Ask us to correct, access or remove eligible personal details through the support path.
SECURITY AND COOKIES

Account Security And Cookie Choices

Privacy Policy controls are practical at each point where your account creates a record.

Account records

We may hold your name or contact identifier, verification result, sign-in events and account preferences so we can connect the…

Wallet records

A cashier reference, selected payment rail, amount status and processing time can remain linked to your account record.

Device signals

Browser type, operating system, session details and security signals may be collected when you sign in.

Cookie settings

Cookies can remember sign-in preferences, session choices and policy selections across the mobile lobby and desktop pages.

Retention period

We keep personal records for the period needed to operate the account, reconcile a wallet request, protect access or meet…

Policy requests

You can ask what personal details we hold, request a correction, raise a concern or ask whether deletion is available.

Privacy Policy Questions About Your Account

These Privacy Policy answers focus on the requests we expect from an Indonesian account holder before or after access. They explain why wallet references, phone verification, cookies and device signals appear in our records. If your question is not covered, contact us from the account or sign-in support path and mention the exact record you want us to check.

The Privacy Policy covers account identifiers, phone verification, sign-in and device signals, cookies, wallet references and support requests. It explains why we use each category, how it supports account access or reconciliation, how retention is handled and how you can contact us about your records.

When you select DANA or QRIS, we record the payment rail, reference, status and time needed to match the cashier request with your account. OVO, GoPay, bank transfer and virtual account requests follow the same Privacy Policy approach for reconciliation and status checks.

Phone verification confirms that the contact route belongs to the person seeking account access. We may use the verification result and related sign-in event to protect the account and answer a privacy request. Do not send your password or one-time code to support.

Yes. Send a correction request through account support and identify the field that appears wrong. We may verify ownership through the phone or account contact already recorded, then assess the request under the Privacy Policy and where local law permits.

We retain records for the period needed to operate your account, reconcile wallet activity, protect sign-in access or meet an applicable legal need. The period can differ by record type. You can ask support whether a particular record remains required or can be restricted.

Yes. The Privacy Policy covers cookies and similar session details used on mobile and desktop pages. They can remember policy choices and access settings. You can adjust browser controls, but blocking necessary cookies may interrupt sign-in or require the policy prompt again.

Use the contact route in your account area, or the sign-in support path if you cannot access the account. Include the request type and any safe reference, such as a cashier status code. Access depends on local law, and we verify ownership before responding.