Reference

agung 711 Privacy Policy for Your Account

Your agung 711 Privacy Policy explains what account details we collect, why we use them, and how you can ask for access or changes.

Account dataWallet recordsCookie choicesRequest access
agung 711 agung 711 Privacy Policy for Your Account
REQUEST HELP PATH

Contact Routes for Privacy Requests

A clear contact path helps you act on this Privacy Policy without searching through account screens.

Account support chat Open the support chat from your signed-in account and ask for a Privacy Policy request. We may check your phone verification before discussing account-linked data or payment references.
Privacy contact form Use the contact form when you cannot reach the account screen. State whether you want access, correction or deletion review, and include the email or phone connected to your account.
Payment record check For a wallet or bank discrepancy, share the transaction reference and rail, such as QRIS, DANA, BCA or Mandiri. We use those details to locate the relevant record.
ACCOUNT DATA PRACTICE

Account Security and Data Choices

We apply this Privacy Policy through ordinary account controls rather than vague promises. Phone verification comes before account access, payment references are separated from wallet credentials, and your request is checked before…

Collection boundaries

We collect details that support account access, payment matching, security checks and customer support. We do not need your wallet PIN or full bank password to confirm a DANA, QRIS or bank transfer reference.

Cookie controls

Cookies can preserve your signed-in session, remember basic settings and help us detect unusual access. You can clear them in your browser, although clearing session cookies may require phone verification again.

Mobile device path

On a phone, our account page may record device type, browser details and login time for security checks. The same Privacy Policy applies when you move from mobile login to the lobby.

Account protection

We use phone verification, login event checks and limited staff access to reduce unauthorised account handling. Never place a password, wallet PIN or one-time code inside a support request.

Retention approach

We retain account, payment and support records only for the period needed for account operation, dispute handling, security checks and legal duties. When a record is no longer needed, our process removes or restricts it.

Change requests

You may ask us to correct an outdated phone number, clarify a processing purpose or provide account data held about you. We verify the requester first, then respond through the account contact route.

Privacy Policy Questions for Indonesia

These Privacy Policy answers address the account questions you are most likely to have before opening an account or sending a support request. They cover stored data, wallet references, cookies, device access, correction requests and local availability, with the same account checks used by our support team.

It covers account details, phone verification, login events, device signals, cookies, support messages and payment references from DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity.

We use your phone number to create the account, complete verification before account access, protect sign-ins and locate account requests. Keep it current so correction or access requests can be checked.

Yes. We may receive a payment status, amount reference and transaction identifier for DANA or QRIS activity. These details help match your account request without requiring your wallet PIN.

Yes. Contact us through signed-in account support or the contact form, choose an access request, and provide the connected phone or email. We verify your identity before releasing account-linked data.

Send a correction request through the account support route or contact form. Tell us which detail is outdated, such as a phone number, and we will check the account before changing it.

Session cookies can keep your login active and remember basic settings. You can clear them in your browser, but doing so may end the session and require phone verification when you return.

Account access and eligibility depends on local law. Where local law permits, you can use the stated contact routes to ask about stored data, processing purposes, corrections or retention.