Reference

Privacy Policy for Your agung11 Account

Our Privacy Policy explains how agung11 handles the account, device and payment details you provide when you open an account or enter the lobby.

Account dataWallet checksDevice accessYour requests
agung11 Privacy Policy for Your agung11 Account
CONTACT PATH

Ask About Your Privacy Policy

A clear support route helps you ask about the Privacy Policy without guessing which account screen to use.

Account request Use the account support path to ask what personal details we hold, why a…
Wallet record For a privacy question about DANA, OVO, GoPay, QRIS, bank transfer or virtual account…
Access concern If a phone, browser or login change affects your data request, tell us which…
HANDLING DETAILS

What We Do With Policy Data

The Privacy Policy is practical: it connects each data category with an account task you can recognise.

Account data

When you open an account, we collect the details needed for the account path and phone verification. We use them to identify your profile, respond to account questions and keep separate accounts from being confused during a support request.

Cookie choices

Cookies and similar device storage can remember a session or help us understand whether a login page loads correctly. Your browser settings can restrict them, although changing those settings may affect account access or require you to sign in again.

Device security

A phone or desktop browser may produce technical signals such as browser type, session time and sign-in pattern. We use these signals to investigate unusual access, not to request your password. Review your device session and contact support if a sign-in looks unfamiliar.

Wallet records

A DANA, OVO, GoPay or QRIS reference can be retained with the account transaction record so we can match a receipt to the correct status. Bank transfer and virtual account records may contain similar references supplied during the payment step.

Retention periods

We retain account, security and transaction records only for the period needed for the stated account, support, security or legal purpose. When a retention period ends, records are deleted, anonymised or isolated according to the process that applies to that data.

Your changes

You can ask us to access, correct or delete eligible personal data through the account support path. We may request phone verification or another account step before acting, and we explain any limit when a record must remain for security or legal reasons.

Privacy Policy Questions for Indonesia

These Privacy Policy answers address the account and wallet questions you may have before opening an agung11 account. They explain what to prepare, how device activity is treated and how to request a change. If your question concerns a specific record, use the account support path and refer to the relevant payment or login event.

The agung11 Privacy Policy covers account details, phone verification, device signals, cookies, support messages and payment status records. It also explains how we use those details for account access, security, wallet reconciliation and requests to access, correct or delete eligible data.

Phone verification helps us connect an account request with the correct account and reduce confusion during login or support. We may use the verified contact detail before discussing private records. Access to the service depends on local law and applies where local law permits.

Yes. The Privacy Policy explains how we handle the transaction references and status details connected with DANA, OVO, GoPay and QRIS. The payment provider may process part of the transaction under its own terms, while we keep the account-side record needed for reconciliation.

Use the account support path and state which detail is incorrect, such as a contact field or account record. Include the account-linked phone or email detail, but never send your password. We may complete a verification step before changing information attached to your profile.

You can submit a deletion request through the account support path. We assess which records can be removed under the Privacy Policy and applicable law. Transaction, security or legal records may need to remain for a stated period, and we explain that reason in our response.

We may receive technical details such as browser type, device signals, session time and sign-in pattern. The Privacy Policy describes their use for session function and security checks. You can review browser cookie controls, though restricting them may require another login.

Start with the support path connected to your account and identify the request as a Privacy Policy matter. For a wallet record, include the payment reference and date; for device access, name the device path. We may verify ownership before sharing or changing private information.