Reference

apk3x Privacy Policy for Indonesia

apk3x Privacy Policy explains how we handle the details connected to your account, including contact data, access records and payment references for DANA, OVO, GoPay and QRIS.

Clear data purposesWallet record contextAccount request pathPolicy access anytime
apk3x apk3x Privacy Policy for Indonesia
CONTACT ROUTES

Three Ways To Ask About Privacy

Privacy questions should reach the team with enough account context to identify the right record without exposing unnecessary details.

Account support path Use the support route beside your account access when you want to ask about…
Policy contact option The contact option on this Privacy Policy page is for questions about collection, cookies…
Wallet record check For a DANA, OVO, GoPay, QRIS, bank transfer or virtual account query, mention the…
DATA PRACTICES

How apk3x Handles Privacy Requests

We treat privacy as an account operation, not a decorative page. Our process connects phone verification, session security, wallet references and support requests so we can investigate a…

Data handling

We collect account details for identified purposes such as access, phone verification, security checks and support.

Cookies and sessions

Cookies and similar session signals can help keep your login path working and help us identify unusual access.

Account security

Phone verification and login event checks help connect account activity to the correct account.

Retention periods

We retain records only for the purposes and periods explained in the Privacy Policy, including security, support and transaction tracing…

Correction requests

If your contact detail or account record is inaccurate, send a correction request through the account support path.

Disclosure questions

Questions about who may receive data should identify the relevant section or event, such as a security review or wallet…

Privacy Policy Answers For Your Account

These Privacy Policy answers address the searches we hear most often before account access: what apk3x records, how wallet references are used, whether cookies affect a mobile session and where to send a request. Read the relevant answer first, then use the policy contact route when your situation needs account-specific checking. Our response and any action depend on local law.

The apk3x Privacy Policy covers account details, phone verification, device and session signals, cookies, support records and payment references. It explains why we use each category, how retention works and how you can request access, correction or deletion where local law permits.

Our policy distinguishes payment references from wallet credentials. A DANA or QRIS request may create a reference needed for account support and transaction tracing, but you should not send wallet passwords, one-time codes or private access details through a privacy request.

Use the support path linked to your account or the contact option shown on the Privacy Policy page. State that you want a data copy and provide the requested account identifier. We may verify control of the account before responding, and timing depends on local law.

Yes, you can send a correction request through account support and identify the detail that is inaccurate. We may ask for phone verification or another account check before changing it. The request is handled under the Privacy Policy and applicable local law.

Cookies and session signals can keep your mobile login path active, remember necessary settings and help identify unusual access. Browser controls can limit cookies, but some account functions may not work as intended when required session storage is blocked.

Retention depends on the purpose of the record, such as security checks, support history or tracing a DANA, OVO, GoPay, QRIS, bank transfer or virtual account request. The Privacy Policy explains the applicable period and any legal reason for continued retention.

Start with the account support path for a request involving your own data. For a general question about cookies, retention or disclosure, use the contact option on this Privacy Policy page. Do not include your password or one-time code in either message.