Reference

Open the wijaya99 Privacy Policy

The wijaya99 Privacy Policy explains what we collect when you open an account, sign in from a phone, or connect DANA, OVO, GoPay and QRIS.

Account dataWallet recordsDevice accessYour privacy choices
wijaya99 Open the wijaya99 Privacy Policy
PRIVACY HELP ROUTES

Contact us about your policy questions

A clear contact route matters when an account record or wallet reference looks unfamiliar.

Account message route Use the support link after login to ask what account details we hold, why…
Wallet reference check For DANA, OVO, GoPay, QRIS, bank transfer or virtual account questions, provide the payment…
Access request path If you cannot sign in, explain that your request concerns the Privacy Policy and…
HANDLING YOUR RECORDS

Browse how wijaya99 manages privacy

Privacy work is part of each account step, from the first phone check to a later wallet status question.

Account data

We may use your account identifier, phone verification result and sign-in history to recognise the correct account. This helps us respond to a privacy request without exposing another account's records.

Payment records

A DANA, OVO, GoPay or QRIS reference can connect a transaction status to your account. We do not need your wallet password to investigate whether that reference matches an account action.

Device signals

When you move from a mobile login to a desktop browser, we may record device and browser signals for account protection. These signals help identify unusual access during a support check.

Cookies

Cookies and similar browser storage may keep a session active or remember a privacy choice. You can manage browser storage through your device settings, although some account steps may then require another login.

Retention

We retain account, support and transaction references only for the period needed for service records, security checks, dispute handling or legal duties. The applicable period can depend on the record type.

Change requests

To request access, correction or deletion where available, contact us through the signed-in support route and identify the specific record. We may ask for account verification before making a change.

Find Privacy Policy answers quickly

These Privacy Policy answers cover the account, device and payment questions you may have before opening an account. If your situation is not listed, use the signed-in support path and describe the record or account step involved.

It covers account details, phone verification, sign-in and device signals, cookies, support records, and payment references from DANA, OVO, GoPay, QRIS, bank transfer and virtual account use.

We use the verification result to connect you with the correct account and help protect account access. It also lets support handle a privacy request without confusing your record with another account.

No. For DANA, OVO, GoPay and QRIS questions, we use the payment reference and status needed to match an account action. Do not send wallet passwords through support.

After login, use the available support link and state that you want a data access request under the Privacy Policy. Identify your account and the records you want us to locate.

Yes, where the request is available under applicable rules. Use the signed-in support route, explain which detail is incorrect, and complete any account verification needed before we update the record.

Retention depends on the record and the reason it is needed, including account security, transaction checks, disputes or legal duties. Ask support about a specific DANA, QRIS or bank reference.

Yes. The policy covers access through a phone or desktop browser. Device and browser signals may differ between paths, while cookies can preserve a session or your privacy choice.