Reference

agenhoki Privacy Policy For Your Account

Our Privacy Policy explains how agenhoki handles the details connected with your account, wallet activity and device access.

Clear data purposesWallet record controlsPolicy access anytime
agenhoki agenhoki Privacy Policy For Your Account
PRIVACY HELP

Where To Ask About Your Privacy Policy

A clear support path matters when your account record or wallet reference needs attention. We ask you to contact us from the signed-in account route where possible, so we can connect the request with the correct profile. If access stalls, include the payment rail, device path and receipt reference without sending your password.

Team online

Account request

Open the support route from your account when you want to ask what personal data we hold, correct a phone detail, or request a copy of the account record linked to you.

Wallet reference

For DANA, OVO, GoPay or QRIS questions, include the payment reference and date. We use those details to locate the relevant record while avoiding a request for your wallet password.

Access concern

If a phone verification step or sign-in path prevents a privacy request, tell us which device you used and where the process stopped so we can check the account route.

DATA PRACTICES

Six Data Practices Behind Our Privacy Policy

We keep this policy practical by linking each data use to an account action you can recognise.

Account details

We collect details needed to create and maintain your account, including contact details used during phone verification. We use them to connect your sign-in, account requests and wallet references to one profile.

Payment records

A DANA, OVO, GoPay or QRIS reference can identify a transaction record without revealing your wallet password. Bank transfer and virtual account references may also be stored for reconciliation.

Cookie choices

Cookies can keep your session active and remember selected site settings on your phone or desktop browser. You can review cookie controls in the browser path, although some account steps may then need repeating.

Device signals

We may record device and browser signals linked to sign-in activity, such as the access path and security events. These checks help us notice unusual account access without asking for your private wallet credentials.

Retention purpose

We retain account and payment records only for stated operational, security or legal needs. When you ask about retention, we can explain the relevant record category and the reason it remains connected to your account.

Change requests

You can ask us to correct account details, explain a data use, or review a deletion request through support. We may first confirm account ownership so another person cannot change your privacy record.

Privacy Policy Answers For Your Account

These Privacy Policy answers address the account, device and payment questions we expect before you open an account. We keep the wording direct so you can understand what happens when you use DANA, QRIS, phone verification or the mobile sign-in path where local law permits.

It covers account details, phone verification, device signals, cookies, sign-in activity and payment references connected with DANA, OVO, GoPay, QRIS, bank transfer or virtual account use.

Phone verification helps connect account access to the correct person and supports security checks. We use the verified contact detail for account control and related requests, not as a substitute for your wallet password.

Yes. The Privacy Policy covers the references and status details associated with DANA and QRIS activity. We may retain those records to match an account action with the correct payment entry.

Yes. Use the signed-in account support route where possible and ask for a copy or explanation of your data. We may confirm account ownership before releasing details connected with your profile.

Send a correction request through account support and identify the detail that needs changing. If the request affects phone verification or payment records, we may ask for a confirming account step.

Cookies can remember your session and selected settings while you move from sign-in toward the lobby. Browser controls can remove or block them, but some account steps may need to be repeated.

You can ask us to review deletion of personal data through the account support route. We assess the request against active account, security and legal record needs, and explain any data that must remain.