Reference

Open aplikasi99 Privacy Policy Clearly

Our Privacy Policy explains what we collect when you open an aplikasi99 account, sign in on mobile, or connect DANA, OVO, GoPay and QRIS.

Account accessWallet recordsDevice choicesContact requests
aplikasi99 Open aplikasi99 Privacy Policy Clearly
CONTACT ROUTES

Reach Us About Your Privacy Policy

A clear contact path helps you act on the Privacy Policy without guessing which account team to reach.

Account request Ask us to explain the personal data connected with your aplikasi99 account.
Wallet query For a DANA, OVO, GoPay or QRIS record, provide the payment reference and approximate…
Access concern Tell us if a mobile sign-in, device change or verification step does not look…
DATA PRACTICE

Explore Our Privacy Handling Steps

The Privacy Policy is practical: it connects account access, payment references, device activity and contact requests to clear handling steps.

Data collected

We may receive account contact details, verification responses, sign-in events, device signals and payment references.

Cookie choices

Cookies and related session tools can help keep your sign-in path working between pages.

Account security

We use verification before giving account-specific privacy details or changing contact data.

Retention timing

We retain account, support and payment references only while they serve the stated account, security or legal purpose.

Correction requests

You can ask us to correct an inaccurate account detail by using the support route and identifying the field that…

Access requests

You may ask what personal data is linked to your account and why it is handled.

Browse Privacy Policy Answers

These Privacy Policy answers address the account and payment questions you are most likely to have before opening an aplikasi99 account. They explain how we connect a contact detail, device session or local wallet reference to your account without turning a privacy request into a general lobby conversation. If your case involves a specific receipt or sign-in event, include that detail when you contact us.

The Privacy Policy covers account details, verification responses, sign-in and device events, cookies, support messages and payment references. It applies when you open or use an account, check DANA, OVO, GoPay or QRIS status, or ask us to access or correct your data.

We use account contact and verification details to connect access to the right person, protect sign-in activity and answer account-specific requests. A payment reference from QRIS, bank transfer or virtual account can also help us match a receipt with the correct account.

Yes. The Privacy Policy covers relevant device and session signals created when you sign in from a phone or desktop browser. These signals help us identify repeated or unusual access and keep the account path working; browser settings can control some cookie activity.

Use the account support route and ask for the personal data connected with your profile. Include the account email or phone detail, but do not send a wallet password. We verify ownership before sharing account-specific records and explain any applicable access limit.

You can request a correction for an inaccurate contact or account detail through support. Tell us which field is wrong and provide the matching account identifier. After verification, we update the record where possible and explain any reason a change cannot be made.

We keep payment references only for the account, support, security or legal purpose they serve. A DANA, OVO, GoPay, QRIS, bank transfer or virtual account reference may remain while a status question or required record needs handling, subject to applicable law.

Yes. Account access and the way we handle some requests depends on local law. Where local law permits, you can ask for access, correction or clarification through support; we may limit disclosure when identity, security or a legal duty requires it.