Reference

agen77 Privacy Policy For Your Account

The agen77 Privacy Policy explains how we handle the details connected with your account, from phone verification to wallet status for DANA, OVO, GoPay and QRIS.

Account detailsWallet recordsCookie choicesPolicy requests
agen77 agen77 Privacy Policy For Your Account
HELP WITH PRIVACY

Get Clear Answers About Your Data

A privacy question should not interrupt your account path. We give you a direct route to ask what a record means, why phone verification is requested or how a wallet reference is connected to your account. Include the phone number or account identifier you use with us, but never send a password or full payment credential. When a question concerns DANA, OVO, GoPay, QRIS or a bank transfer, the relevant reference helps us locate the correct record.

Team online

Policy request

Ask us to explain a Privacy Policy point through the account support route. We can clarify what data is collected during phone verification, which purpose applies to a wallet reference and what details we need before discussing your account.

Access concern

If your account path stalls after verification, tell us the device type and the step where access stopped. We use those details to separate a session issue from a privacy request, while keeping your password and one-time codes private.

Wallet record

For a DANA, OVO, GoPay, QRIS, bank transfer or virtual account question, send the transaction reference rather than a full wallet credential. This lets us check status records and respond without asking you to expose unnecessary financial details.

OUR DATA ROUTINE

What Your Privacy Policy Covers

We handle privacy as part of the account routine, not as a separate page you have to search for after a problem.

Data collected

We may handle account details, phone verification records, session data, cookie preferences and support messages. Payment references from DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity are used to connect a request with the correct account process.

Cookie choices

Necessary cookies help keep your account session working across the login path and lobby pages. Other browser storage can be controlled through the available cookie setting on your device, so you can decide whether optional usage signals remain active.

Account protection

Phone verification is an account step before access, and we may use device or session signals when checking an unusual sign-in. Do not share your password or one-time code with support; send only the details needed to identify the issue.

Retention timing

We keep records for as long as their stated purpose requires, including account access, payment status checks, support handling or legal duties where applicable. When a purpose ends, handling follows our retention process rather than keeping every record indefinitely.

Change requests

You can ask us to correct account details, explain a data use, provide a copy where applicable or remove eligible records. Include your account phone number and the exact request, then complete any identity check needed to protect the account.

Policy contact

Use the account support route for Privacy Policy questions, including cookie choices, retention, phone verification and wallet references. We may ask you to confirm account ownership before discussing personal data or changing details connected with access.

Privacy Policy Answers For agen77

These Privacy Policy answers focus on the questions we expect you to ask before opening an account or requesting help. They cover the practical points around personal data, cookies, phone verification, payment references and access from Indonesia. If your situation is not listed, use the policy contact path and describe the account step involved. Access depends on local law, so eligibility and handling can vary by location.

The agen77 Privacy Policy covers account details, phone verification, session and device signals, cookie choices, support messages and payment references. It explains why we handle each category, how it supports account access or status checks, and how you can ask about correction, copying or removal.

Phone verification connects your account with an access step and helps us investigate sign-in problems or unusual activity. We may ask you to confirm ownership before discussing personal data or changing account details. Never send your password or one-time code through a support request.

Yes. The Privacy Policy covers payment references connected with DANA, OVO, GoPay and QRIS, along with bank transfer and virtual account status records. We use the reference to match a cashier request or investigate a mismatch, rather than asking for your full wallet credential.

Use the account support route and state whether you want a correction, a copy where applicable, an explanation or removal of eligible data. Include the phone number linked to your account and the exact record involved. We may complete an ownership check before making changes.

Necessary cookies support the login session and movement between account pages. Optional browser storage can relate to page-use signals and may be controlled through the cookie setting available on your device. Removing necessary cookies can interrupt access steps until the session is created again.

Retention depends on the purpose of the record, such as account access, phone verification, wallet status, support handling or applicable legal duties. We do not keep every record without an end point. Ask through the policy contact path if you need the retention purpose for a specific item.

Access depends on local law and the eligibility rules that apply to your location. The Privacy Policy explains data handling when you use the account path, but it does not change local requirements. Check your position before opening access, and contact us if a policy question remains.