Reference

Privacy Policy For Your agen77 Account

Our Privacy Policy explains how agen77 handles the details connected to your account, including phone verification, wallet records and device access.

Clear data choicesWallet record contextAccount access steps
agen77 Privacy Policy For Your agen77 Account
CONTACT YOUR WAY

Three Paths For Privacy Questions

A clear contact path helps you ask about Privacy Policy matters without placing sensitive details in the wrong channel.

Account support Use the signed-in account support path for Privacy Policy requests about your phone number, login record, device details or stored contact information. We can ask for an account step to confirm that the request comes from you before discussing personal data.
Wallet receipt check For DANA, OVO, GoPay or QRIS records, send the transaction reference and date through account support. We use those details to locate the relevant payment entry while keeping your PIN, password and full wallet credentials out of the message.
GoPay Payout Help When your question concerns a GoPay-related payout record, choose GoPay Payout Help where it appears in the lobby, then follow the support path. Privacy Policy questions still go to account support so the request can be tied to your verified account.
DATA HANDLING DETAILS

Six Ways We Handle Your Records

Privacy Policy choices are easier to use when each data action has a practical account step.

Account details

We use the account details you submit, such as your phone number and chosen login information, to create access and respond to account requests. Phone verification helps us connect a Privacy Policy request with the correct account before we disclose stored details.

Device signals

When you sign in from a mobile browser or computer, we may record device and session signals linked to that access. These details help us spot unusual login activity and investigate an account concern without needing your wallet PIN.

Cookie choices

Cookies can remember session state and basic preferences so your account path does not restart at every page. Your browser controls whether cookies are accepted; changing them may affect sign-in continuity, while account records remain handled under this Privacy Policy.

Payment references

A payment record may show a rail such as QRIS, DANA, OVO, GoPay, bank transfer or virtual account, along with a reference and status. We use those fields to trace a receipt, not to request your private wallet password or PIN.

Retention requests

We keep personal data only while it supports account access, payment checks, security needs or legal duties. Ask through account support what applies to your record, and we will explain whether a correction or removal request can be completed under local requirements.

Policy changes

If this Privacy Policy changes, we will place the updated wording on this page and show the effective context near the policy text. Check this page before opening an account, especially when you use a new device or change your payment rail.

Privacy Policy Questions About agen77

These Privacy Policy answers focus on the account actions you are most likely to take before opening access. They cover what we collect, how payment references are used, how to request a copy or correction, and what happens when you change devices. If your question is not listed, use the signed-in support path and mention the relevant account step without sending a password or wallet PIN.

The agen77 Privacy Policy covers account details, phone verification, login and device signals, cookie preferences, support messages and payment references. It explains why we use each category, how long records may be retained and how you can request access, correction or removal where local law permits.

Yes. Privacy Policy treatment includes transaction references and status details connected with DANA, OVO, GoPay and QRIS, as well as bank transfer or virtual account entries. We use those fields to check an account record and do not need your wallet PIN or password.

Sign in and open the account support path, then ask for a copy of the personal data connected with your account. Include your account phone number or another account identifier, but never send a password, one-time code or complete wallet credential in the request.

You can ask us to correct inaccurate account details through account support. State which field needs changing and provide the account step requested by support for identity confirmation. We assess the request against the Privacy Policy and applicable local requirements before changing the record.

We use cookies and similar session signals to keep sign-in state, remember basic preferences and help investigate unusual access. Your mobile browser or computer settings can control cookies. If you remove them, you may need to complete the account access step again.

Retention depends on why a record exists, such as account access, payment checking, security or a legal duty. Privacy Policy requests about a specific record should go through account support. We can explain the applicable period and whether removal is available where local law permits.

Yes, access depends on local law. We apply this Privacy Policy where local law permits and may need to restrict account access or a data request when a local requirement applies. Contact account support from your signed-in session if you need a location-specific explanation.