Reference

Open the agenmenang Privacy Policy

The agenmenang Privacy Policy explains what we collect when you create an account, verify your phone and use the lobby from a mobile browser or desktop.

Account dataWallet recordsCookie choicesAccess requests
agenmenang Open the agenmenang Privacy Policy
CONTACT ROUTES

Ask about DANA data or access

A direct support route helps you resolve a privacy question without guessing which account screen to use. We keep policy questions separate from lobby activity, so you can ask about a phone verification record, a wallet reference or a device sign-in from the account and cashier support paths. Include the account identifier you can safely share, the date of the event and the specific change you want us to check.

Team online

Account privacy request

Use the account support path to ask what phone, verification or sign-in data is connected with your profile. We may ask for an account step that confirms you are requesting access to your own records.

Wallet record question

For DANA, OVO, GoPay or QRIS questions, share the payment reference and status shown on your account. We use that detail to locate the relevant record without asking for your wallet password or private wallet credentials.

Change or deletion request

If you want a correction, restriction or deletion request checked, send the request through the policy contact route linked with account support. We will explain any identity check and any record we must retain for legal or security reasons.

HANDLING PRACTICE

Protect your mobile login and records

Privacy controls work best when the account steps are clear. We limit internal access to data according to the task being performed, keep security events available for investigation and use cookie settings…

Data we collect

We may collect your account details, phone verification result, sign-in time, device or browser signals, support correspondence and payment references. For DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity, the record is used to identify status rather than expose private wallet credentials.

Cookie controls

Cookies and similar browser storage can keep your session connected while you move between account pages and the lobby. You can manage browser permissions on your device, although restricting essential storage may prevent phone verification or require another sign-in.

Account security

Phone verification is used before account access, while device and sign-in signals help us examine unusual activity. Keep your phone and account details private, and contact support if a sign-in or payment reference does not match an action you made.

Retention periods

We keep personal and payment-related records only for the period needed for account operation, security checks, dispute handling and legal duties. When a retention period ends, records are removed, anonymised or securely restricted according to the applicable requirement.

Requesting changes

You can ask us to correct inaccurate account data, explain a processing purpose or provide details about records connected with your profile. Include the relevant account step and the change requested; we may verify your identity before making an adjustment.

Where to contact us

Privacy questions belong in the account support path, while a wallet status question can be raised beside the cashier record. We use the reference you provide to locate the right event and will state when access depends on local law or another legal condition.

Find Privacy Policy answers for your account

These Privacy Policy answers address the account and payment questions you are most likely to have before opening an agenmenang account. They cover collection, access, cookies, wallet references, retention and the steps for requesting a change. If your case involves a particular DANA, OVO, GoPay or QRIS event, use the account support route with its reference and date.

It covers account creation, phone verification, sign-in activity, device signals, cookies, support messages and payment references. It explains why we use each type of data, how security checks work, how long records may remain and how you can ask about access or correction.

Yes. The Privacy Policy covers references and status details connected with DANA, OVO, GoPay and QRIS, along with bank transfer and virtual account records. We use these details to match account activity and investigate status questions, not to request or store your wallet password.

Phone verification helps connect an account request with the person trying to access it and supports account security. The result may be stored with your profile so we can check later access events. We may ask for another identity check before releasing personal records.

You can ask for details about personal data connected with your account, including verification records, sign-in events, support messages and payment references. Send the request through account support with the relevant account step. We will explain the identity check and any legal limits.

Cookies or browser storage can keep a session active and help account pages remember necessary settings. If you block essential storage on your phone, you may need to sign in again or repeat phone verification. Optional browser controls can be changed from your device settings.

Use the policy contact route linked with account support and state which record is inaccurate, such as a phone detail, verification result or payment reference. Provide the account step and supporting context. We may verify ownership before correcting the record.

Retention depends on the purpose of the record, including account security, dispute handling and legal duties. When the applicable period ends, we remove, anonymise or restrict the data. You can ask support about a particular record and the reason it remains available.