Reference

Privacy Policy for apk2x Accounts

Our Privacy Policy explains how we handle the details connected with your apk2x account, including contact data, phone verification, wallet activity and device access.

Account recordsWallet activityDevice accessPolicy requests
apk2x Privacy Policy for apk2x Accounts
HELP WITH REQUESTS

Privacy Questions Near Your Account

A clear contact path matters when you want to ask about the Privacy Policy or correct an account detail. Start from the support route beside the account and cashier area, then include the phone number or account identifier linked to your request. We use the submitted context to locate the relevant record, check a payment reference and reply with the next available step. Please do not send a wallet PIN, login password or full card credentials when asking for help.

Team online

Account access request

If your phone verification does not match your account, contact us through the account support path and state what changed. We can use the account identifier, sign-in event and device context to assess the request without asking you to reveal your password.

Wallet record question

For a DANA, OVO, GoPay or QRIS record, include the payment reference, amount shown in your account and approximate time. We use those details to trace the status while keeping your wallet PIN and private authentication details out of the support message.

Policy change request

To request access, correction or removal of eligible personal data, use the same support route and identify the account record concerned. We may ask for an account verification step before making a change, so another person cannot alter your details.

DATA HANDLING PATH

What We Do With Your Account Data

Our handling process follows the account activity you can see: registration creates an account record, phone verification confirms access, and wallet references help us reconcile payment status.

Registration details

When you open an account, we collect the details needed to create and maintain that account, such as your contact information and verification state. We use them to identify your account, provide access and respond when you ask about a Privacy Policy request.

Phone verification

Phone verification links account access to the contact detail you provide. We record the result and related security event rather than treating a successful check as permission to view unrelated phone content. Tell us through support if your number or access device changes.

Cookies and sessions

Cookies can keep your sign-in session and security preferences available as you move from the account page to the lobby. You can manage cookies through your browser settings, although blocking required session cookies may prevent the account path from working correctly.

Payment references

DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity can create references that we use to match account entries. We store the reference and status needed for reconciliation, not your wallet PIN. A receipt or reference helps us answer a payment-data request.

Account security

Sign-in time, device context and verification events help us investigate unusual access. If you see an unfamiliar session, contact us through the account support path and avoid sharing your password. We may pause a requested change until we can confirm that you control the account.

Retention and changes

You can ask which eligible data we hold, request a correction or ask about deletion through support. We retain some records when needed for a dispute, security investigation or legal duty. After the relevant period, we remove, anonymise or restrict the record as appropriate.

Privacy Policy Questions About apk2x

These answers address the practical Privacy Policy questions you may have before opening an account or returning to the apk2x lobby. They cover the data connected with phone verification, cookies, local wallet references, device access, account corrections and deletion requests. If your situation is different, use the account support route and provide only the details needed to locate your record.

The apk2x Privacy Policy covers account details, phone verification results, sign-in and device events, cookie-based session data, support messages and payment references. It explains why we use those records for access, security, reconciliation and legal duties, including activity connected with DANA, OVO, GoPay and QRIS.

We collect the account and contact details needed to create your record, plus the result of the phone verification step. We can also record sign-in time, device context, support messages and payment references. We do not need a wallet PIN to identify a DANA or QRIS transaction.

Yes. The Privacy Policy covers references and statuses returned through DANA and QRIS, as well as OVO, GoPay, bank transfer and virtual account records. We use those details to match an account entry and answer a status request. Keep wallet passwords and PINs out of every support message.

Use the support route beside your account area and state whether you want access to an eligible record or a correction. Include your account identifier and the detail concerned. We may complete an account verification step before responding so another person cannot obtain or change your information.

You can send a deletion request through the account support path. We assess which records can be removed and which must remain for a dispute, security check or legal duty. Where removal is possible, we delete, anonymise or restrict the relevant data after verification.

Cookies can preserve your session and security preferences while you move between account pages and the lobby. Browser settings let you manage them. If you block required session cookies, phone verification or sign-in may not continue, so check those settings before reporting an access problem.

Yes. Account access and eligibility depends on local law, and we provide access only where local law permits. Your location can also affect how an account or payment request is handled. If you need a location-specific privacy answer, contact us through the account support path.