Reference

Privacy Policy for ipx994 Accounts

Our Privacy Policy explains how we collect, use and protect the details you provide when opening an ipx994 account or accessing the lobby.

Clear data purposesWallet status explainedAccount request pathIndonesia access wording
ipx994 Privacy Policy for ipx994 Accounts
REQUEST HELP SAFELY

Three Ways To Raise A Privacy Request

A clear request helps us locate the right account record without asking you to send unnecessary personal details. Use the account support path when your question concerns phone verification, a login record or data linked to your profile. If a wallet status appears beside a transaction, include the relevant DANA, OVO, GoPay or QRIS reference rather than sending a full wallet history. We will use the information you provide to check the request, protect the account from an unauthorised change and explain the next step where local law permits.

Team online

Account support path

Open the support path from your signed-in account when you want to ask about stored profile details, phone verification or an access record. We may ask for account identifiers so we can distinguish your request from an unrelated profile without exposing personal data.

Payment reference check

For a privacy question connected with DANA, OVO, GoPay or QRIS, share the transaction reference and approximate date shown in your account. We use those details to trace the relevant record while avoiding a request for your wallet PIN or full payment credentials.

Access concern

If you believe another device accessed your account, tell us through the account support route and change your password before continuing. We can review sign-in signals, request additional phone verification and explain the action available where local law permits.

ACCOUNT DATA PRACTICE

Six Practical Privacy Controls We Use

Privacy controls are tied to real account actions rather than a general statement about security.

Phone verification

Before account access is completed, we may use your phone verification result to confirm that the person requesting entry can receive the required account message. This record helps us investigate repeated access attempts and prevents a privacy request from being attached to the wrong profile.

Device and session signals

A browser or mobile device can provide session, language and security signals when you sign in. We use these signals to detect unusual account access, not to ask for unrelated files from your device. Clearing browser data may require you to verify the account again.

Cookies and storage

Cookies can keep a sign-in session working and help us understand whether the privacy page or account path loads properly. You can remove or restrict them in your browser settings, although doing so may interrupt saved preferences or require another sign-in.

Payment matching

Transaction references from DANA, OVO, GoPay, QRIS, bank transfer or a virtual account can be matched with your profile to confirm payment status. We do not need your wallet PIN for that check, and you should not include a PIN in a privacy request.

Retention decisions

We retain account and transaction records for as long as they serve account security, dispute handling, payment reconciliation or a legal requirement that applies to the service. When a record is no longer needed for those purposes, we remove it or reduce its direct link to your account where practical.

Change or removal request

You can ask us to correct inaccurate profile data or request removal of data that no longer needs to be retained. Send the request through account support with the affected account detail; we may verify ownership first and explain any record that must remain for a valid operational reason.

Privacy Policy Answers For Your Account

These questions address the privacy issues you are most likely to check before opening or using an ipx994 account. The answers focus on account records, local wallet references, device access, cookies and requests for correction or removal. If your situation is not covered, contact us through the signed-in account support path and give only the details needed to identify the matter.

The ipx994 Privacy Policy covers information used for account creation, phone verification, sign-in security, cookies, payment matching and support requests. It also explains retention, correction and removal requests. Access or eligibility depends on local law, so the policy should be read together with any access notice shown for your location.

We may collect your contact details, phone verification result, sign-in records, device and session signals, support messages and payment references connected with your account. We use these details to authenticate access, protect the profile, reconcile account status and answer privacy requests, rather than requesting unrelated device content.

Yes. The Privacy Policy covers references needed to match a DANA or QRIS action with the correct account, as well as related OVO, GoPay, bank transfer or virtual account status. Send a reference when asking for help, but never include a wallet PIN, password or full payment credential.

Use the support path inside your signed-in account and state whether you want access to stored data or correction of a specific detail. Include the account identifier needed for verification. We may confirm ownership by phone before responding, and the available action depends on local law.

You can submit a removal request through account support and identify the profile concerned. We first verify ownership, then explain what can be removed. Some account, payment or security records may need to remain for dispute handling, reconciliation or a legal reason that applies where local law permits.

On a phone or tablet, cookies and device storage can retain a session and help us see whether the account and Privacy Policy pages load correctly. You can restrict them in browser settings. Removing them may sign you out, clear preferences or trigger phone verification at the next access.

Change your account password, avoid sharing wallet credentials and contact us through the signed-in support route as soon as possible. Tell us which device or sign-in event looks unusual. We can check available session signals, secure the profile and describe the next step where local law permits.