Reference

agung4d Privacy Policy, Explained Clearly

The agung4d Privacy Policy explains what we collect when you open an account, sign in from a mobile device, or use DANA, OVO, GoPay and QRIS for wallet…

Account dataWallet statusCookie choicesAccess requests
agung4d agung4d Privacy Policy, Explained Clearly
CONTACT ROUTES

Get Help With Privacy Requests

A clear contact route helps you ask about the Privacy Policy without sending sensitive details through an unsuitable channel. Start with our account support route when you need a copy of your stored account data, an explanation of a device record, or help identifying a wallet reference. We ask you to confirm enough account information to protect your request, while avoiding requests for a wallet PIN or full payment password. If access is available where local law permits, support can connect a policy question with the correct account step.

Team online

Account support

Use the account support channel for Privacy Policy questions about phone verification, sign-in records, profile details or a request to correct your account data. Include your registered contact detail and a short description of the change you need; we will not ask you to disclose a wallet PIN.

Wallet status help

If a DANA, OVO, GoPay or QRIS reference appears incorrectly in your account, send the transaction reference and date through support. We use those details to locate the status record, while you should hide passwords, security codes and unrelated wallet information before sending a receipt.

Privacy request path

For access, correction, deletion or cookie questions, state the request clearly and identify the account email or verified phone path. We may ask for an account step to confirm your identity before discussing personal data, which helps keep another person from receiving your records.

DATA CONTROLS

How We Handle Account Privacy

Privacy work is connected to practical account operations: we record the checks needed to let you sign in, match wallet activity and investigate support requests.

Account records

We may hold your name or contact detail, phone verification result, account settings and sign-in history so we can maintain the account path. We use this information for access checks and support handling, not as a reason to request your wallet password or private security code.

Device signals

A mobile browser or desktop session can provide device, browser, language and connection signals. These records help us recognise unusual sign-in activity and investigate access from Indonesia, including a session that changes between a phone and a desktop browser.

Cookie choices

Cookies may remember session state, security preferences and basic page settings. You can restrict or clear cookies in your browser, although removing essential session cookies may require you to sign in again before the account path works normally.

Payment references

For DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity, we use references and status results to connect a payment event with the correct account. We do not need your wallet PIN to check whether a reference is pending, matched or unresolved.

Retention checks

We keep personal data only while it supports account security, payment reconciliation, support history, dispute handling or a legal duty. When a record no longer serves one of those purposes, we review it for deletion, anonymisation or restricted storage.

Change requests

You can ask us to access, correct, delete or limit use of personal data by contacting support through your verified account route. We may request identity confirmation, explain any legal or security reason for a limitation and update you after the request is assessed.

Privacy Policy Questions For agung4d

These Privacy Policy answers cover the account and wallet questions you are most likely to ask before opening an account or contacting support. We keep the examples specific so you can understand why a record exists, what we need to verify a request and how browser or payment details fit into the data process. Where an access decision is involved, it depends on local law.

The Privacy Policy covers account details, phone verification, sign-in and device records, cookies, support messages and payment references from DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity. It also explains retention, security controls and how to request access or correction.

Phone verification helps us connect an account request with the person attempting access and helps reduce mistaken or unauthorised account changes. We record the verification result and related security event, but you should never send your one-time code or wallet PIN to support.

No. The Privacy Policy describes our use of payment references, status results and reconciliation details for DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity. Wallet passwords, PINs and security codes should remain with your payment provider and should not be sent to us.

Contact support through your verified account route and ask for an account data access request. Include the registered contact detail and explain the records you want, such as sign-in history or profile data. We may confirm your identity before releasing information to the correct person.

Yes, you can request correction or deletion through support, subject to identity checks and any security, dispute or legal retention need. Tell us which account detail is wrong or which record you want removed. We will explain if a specific record must remain temporarily.

Cookies can preserve a session, remember security preferences and support basic browser settings. You can clear or restrict them through your phone or desktop browser. If essential cookies are blocked, you may need to sign in again and some account access steps may not work.

The Privacy Policy is written for account and support activity connected with Indonesia access, including sessions from Medan and other locations. Availability and eligibility depends on local law. If you have a location-specific question, contact support before sharing payment or identity documents.