Reference

Open agam99 Privacy Policy Before Account Access

agam99 Privacy Policy shows what we collect when you create an account, sign in, use the lobby, or connect DANA, OVO, GoPay and QRIS.

Clear collection reasonsWallet data contextAccount request stepsIndonesia access terms

Explore Our Lobby Read FAQ

Browse How Your Payment Data Is Used

agam99 Service availability depends on jurisdiction. Users are responsible for checking local law before access.

Our Privacy Policy separates account details from payment references so you can see what is needed for each action. During registration, we use your submitted contact details and phone verification status to create and protect the account. When you choose DANA, OVO, GoPay or QRIS, we

1
may receive transaction references, status results and timing details needed to match a wallet action with your account; we do not treat a payment reference as your wallet password. Bank transfer and virtual account records may be retained for reconciliation, security checks and required account queries.
2
We also record device, browser and sign-in events to detect unusual access, including repeated attempts from a new phone. Access depends on local law and is available where local law permits. The policy explains retention, permitted service providers, your request path and changes we may publish
3
on this page.

Service availability depends on jurisdiction. Users are responsible for checking local law before access.

CONTACT YOUR WAY

Check Your Privacy Contact Path

A clear contact route helps you manage Privacy Policy questions without explaining your whole account history. Tell us whether your request concerns a phone number, sign-in record, cookie setting, payment reference or deletion request. We may ask for account details to confirm that the request comes from you, but you should never send a wallet PIN or password. If you are in Jakarta and a QRIS status needs checking, include the reference and date so our support team can locate the relevant record.

Team online

Account data requests

Ask us to review, correct or explain personal details connected with your agam99 account. Include the account contact and the specific field you want changed, then complete our identity check before we act on the request.

Wallet reference checks

For DANA, OVO, GoPay or QRIS questions, send the payment reference rather than private wallet credentials. We use that reference to trace a status record and keep the request limited to the relevant transaction detail.

Cookie and device help

If a phone or desktop keeps a sign-in cookie after you expected it to clear, contact our support path with the device type and browser. We can explain the setting, sign-out step and any account-security action available.

CONTROL THE RECORD

Switch On Clear Data Controls

Privacy Policy choices are easier to use when each control has a practical purpose. We limit account data to tasks such as sign-in, phone verification, wallet reconciliation and security checks, while cookies…

Account details

We use the details you enter for account creation, phone verification and account support. Check your contact information before requesting a wallet action, because an accurate account record helps us match the request without exposing unrelated details.

Cookies on devices

Cookies can keep a session active, remember a selected language or help identify unusual sign-in behaviour. On a shared phone or desktop, sign out and clear site data through your browser settings when you finish using the account.

Sign-in protection

We may record device type, browser details, approximate connection data and sign-in time to investigate unusual access. If a new device triggers a check, complete the account step yourself and do not share your password with support.

Payment records

A DANA, OVO, GoPay, QRIS, bank transfer or virtual account action can create a reference, amount status and processing time in our records. We use those details to reconcile the account action, investigate a query and protect against misuse.

Retention choices

We keep records only while they serve account operation, security, reconciliation or a legal need described in the Privacy Policy. When you ask about deletion, we explain which data can be removed and which record may need to remain.

Requesting a change

Send a specific request for access, correction, deletion or a cookie explanation through our support route. We confirm your identity first, answer the request in context and tell you if local law affects what we can change.

Ask About Privacy Policy and agam99

These Privacy Policy answers focus on the account moments that matter before you open an account: phone verification, wallet activity, device sessions, cookies and requests for changes. We keep the wording practical so you can decide what to share and where to contact us. If your question is not covered, use the support path with a precise account or payment reference. Account access depends on local law and applies where local law permits.

The Privacy Policy covers data collected during account creation, phone verification, sign-in, wallet activity, cookie use and support requests. It also explains retention, security checks, permitted data handling and the steps you can use to ask for access, correction or deletion where available.

We use phone verification to confirm the account contact, support sign-in protection and reduce confusion when you request account help. The verification status is separate from your DANA, OVO or GoPay credential, and you should never send a wallet PIN to us.

Yes. Privacy Policy treatment includes QRIS, bank transfer and virtual account references created when you use those routes. We may keep the reference, status and timing needed to reconcile an account action, answer a payment query and investigate unusual activity.

Contact our support path and state that you want an account data request. Name the data area, such as phone verification, cookie records or payment references, and provide the account contact. We confirm your identity before explaining what can be supplied.

You can ask us to correct inaccurate details or delete eligible data through the contact route. We review the request against account security, reconciliation needs and local law, then explain what changes, what remains and why any record must be retained.

Cookies may keep your session active, remember a setting or help identify unusual access. You can clear them through your mobile browser, although this may sign you out. If a cookie issue continues, tell support your device and browser without sending credentials.

The policy is written for account access connected with Indonesia, including wallet references from DANA, OVO, GoPay and QRIS. Eligibility depends on local law, so access is provided where local law permits. Contact us if your location creates a policy question.

Open agam99 Privacy Policy Before Account Access

Check Your Privacy Contact Path

Account data requests

Wallet reference checks

Cookie and device help

Switch On Clear Data Controls

Account details

Cookies on devices

Sign-in protection

Payment records

Retention choices

Requesting a change

Ask About Privacy Policy and agam99

01 What does the agam99 Privacy Policy cover?

02 Why does agam99 need phone verification data?

03 Does Privacy Policy cover QRIS and bank transfer records?

04 How can I request my agam99 account data?

05 Can I ask agam99 to correct or delete my data?

06 How does Privacy Policy handle cookies on my phone?

07 Where does agam99 Privacy Policy apply in Indonesia?

Related Pages