Reference

wangi4d Privacy Policy For Your Account

Our wangi4d Privacy Policy explains what we collect when you open an account, sign in from a phone, or use DANA and QRIS.

Account clarityWallet recordsDevice controlsPrivacy requests
wangi4d wangi4d Privacy Policy For Your Account
REQUEST HELP DIRECTLY

Check Privacy Questions Through Your Account

Privacy questions can be raised from the same account route used for login and wallet-status help, so we can connect your request to the correct record. Include the phone number linked to your account, the device path you used, and the subject of your request. We may ask for account details to confirm that a data request comes from you, but we do not ask you to send a full wallet password.

Team online

Account request

Use your signed-in account path to ask about stored details, correction requests, or account closure. We check the account step first so a privacy reply reaches the right record.

Wallet record

For DANA, OVO, GoPay, or QRIS questions, include the transaction reference and date. We use those details to locate the relevant payment record without requesting your wallet PIN.

Device access

If privacy settings look different on a phone and computer, tell us which device path you used. We can compare sign-in records and explain the account-access data connected with that session.

HOW RECORDS ARE HANDLED

Explore How We Protect Policy Requests

We keep privacy handling tied to practical account events rather than unrelated browsing. A sign-in, phone verification step, wallet status check, or request to change personal details creates a clear reason for…

Data collection

We collect account details you submit, verification results, device signals, and transaction references from DANA, OVO, GoPay, QRIS, bank transfer, or virtual account activity.

Cookie choices

Cookies can help keep your sign-in path connected and remember basic page settings. Our Privacy Policy explains their role and how your browser controls can limit them.

Account security

Phone verification comes before account access, and unusual sign-in details may be checked. Never send a password or wallet PIN when asking us about personal data.

Retention periods

We keep personal and transaction records for the period needed for account operation, security checks, disputes, or legal duties, then remove or de-identify them where appropriate.

Change requests

You can ask us to correct inaccurate account details or explain the data connected with your profile. Include your linked phone number so we can verify the request.

Contact route

Privacy matters go through our account support path, including questions about a QRIS receipt, device record, cookie setting, or the personal details attached to your account.

Browse Answers About Privacy Policy

These Privacy Policy answers address the account, device, wallet, and access questions we hear most often. Read them before opening an account, then use the support route if your request concerns a specific phone number, transaction reference, or stored record.

It covers account details, phone verification, device and browser signals, cookies, wallet transaction references, retention, security checks, and requests to access or correct your personal data.

Yes. We record the payment reference, date, amount status, and reconciliation details needed for DANA or QRIS activity. We do not need your wallet PIN to answer a privacy request.

Yes. Send a correction request through your account support path with the linked phone number and the detail that needs changing. We verify the request before updating the record.

Phone verification confirms that an account-access request is connected to you. We retain the verification result and related security record for the period needed for account protection and applicable legal duties.

We may record device, browser, session, and network details used during sign-in. These signals help investigate unusual access and explain differences between a phone session and a computer session.

Retention depends on the purpose: account operation, security, transaction reconciliation, disputes, or legal duties. When a record is no longer needed, we remove or de-identify it where appropriate.

You can contact us about access, correction, or deletion requests where local law permits. We first verify your account details, then explain which records can be supplied or changed.