Reference

agenasia88 Privacy Policy For Your Account

agenasia88 Privacy Policy explains how we handle the details connected with your account, device, wallet activity and support requests.

Account clarityWallet recordsDevice controlsPolicy access
agenasia88 agenasia88 Privacy Policy For Your Account
CONTACT YOUR WAY

Get Privacy Help Without Repeating Details

A privacy question should not become another login problem. We give you a clear route from the account area to a support request, so you can ask about a stored detail, a wallet reference or a device record in one place. Include the email or phone connected with your account, and we can locate the relevant case without asking for your wallet password. If you cannot access the account, use the available contact route and describe the last successful account step.

Team online

Account request

From your account support path, ask which personal details are linked to your agenasia88 profile. We use the contact detail already attached to the account to confirm the request before discussing records, helping prevent another person from receiving private account information.

Wallet question

For a DANA, OVO, GoPay or QRIS privacy question, include the payment reference and approximate date, but never send a wallet PIN. We can check the record connected with your account and explain why that reference appears in your payment history.

Access problem

If a device change blocks your account, tell us the device path you used, such as mobile browser or desktop browser. We can separate an access-security check from a Privacy Policy request and direct the case to the right support route.

DATA CONTROL ROOM

What We Do With Your Personal Details

Privacy work covers more than the form you complete when creating an account. We also consider cookies, sign-in events, wallet references, device changes, account security and the period for which records remain…

Account details

We use the name, phone or email you provide to create and maintain your account, send account notices and respond to support requests. A clear phone verification step helps us connect the request to you before we disclose or change personal account details.

Wallet references

A DANA, OVO, GoPay or QRIS transaction may leave a reference, amount and status connected with your account record. We use those details to reconcile a receipt or investigate a missing status, while avoiding requests for your wallet PIN or private wallet password.

Cookies and sessions

Cookies can remember a session choice and help us understand whether a sign-in request belongs to the same browser. You can manage browser cookie settings, although limiting them may require another account verification step when you return from a mobile device.

Device security

We may record device type, browser signals and login time to identify unusual account access. If you move from a mobile browser to a desktop browser, that change can trigger a security check before we allow sensitive account or wallet actions.

Retention period

We keep account, support and payment records only for the period needed for the stated service purpose, security work or a legal duty. When that period ends, records are deleted, anonymised or restricted from ordinary account use where the applicable rule requires it.

Change request

You can ask us to correct an inaccurate phone number, email or profile detail through the support path. Where local law permits, you may also ask about access, removal or restriction; we first verify the request so a third party cannot alter your account record.

Answers Before You Open An Account

These Privacy Policy answers address the searches we expect from someone checking agenasia88 before account access. They cover the data connected with local wallets, browser sessions, verification and support requests. If your question concerns a record not listed here, use the account support path and include enough detail for us to find the case without sending sensitive wallet credentials.

The agenasia88 Privacy Policy covers account details, phone verification, login events, browser cookies, device signals, payment references and support messages. It also explains how you can ask about your records, correct a detail or request another action where local law permits.

Yes. When your account uses DANA or QRIS, we may retain a transaction reference, status and related account details needed for reconciliation. We do not need your wallet PIN for a privacy request, and you should never include that PIN in a support message.

Device and browser records help us identify unusual sign-in activity and protect account access. A move from mobile browser to desktop browser may lead to an additional check. These signals are handled as security data rather than as permission to collect unrelated personal details.

Use the support route linked from your account area and ask for the personal data connected with your profile. Include your account email or phone so we can verify ownership. Where local law permits, we will explain the available access process and any required limits.

You can ask us to correct an inaccurate email or phone number through account support. We verify the request before changing the record, especially when the detail also protects wallet activity. If the change affects phone verification, another account step may be required.

We retain account, payment and support records for the period needed for their stated purpose, account security or an applicable legal duty. Once that period ends, we delete, anonymise or restrict the record according to the rule that applies to it.

Start with the support path in your account area and select the privacy-related reason for contact. If you cannot sign in, use the available contact route and provide your account email or phone, device path and request summary without sharing a password or wallet PIN.