Reference

Open wajan4d Privacy Policy for Account Clarity

Your account details, wallet records and device choices are explained in the wajan4d Privacy Policy, so you know what we collect before opening an account.

Account dataWallet recordsDevice choicesPolicy requests
wajan4d Open wajan4d Privacy Policy for Account Clarity
SUPPORT PATH

Ask Support About Privacy Requests

A clear support route helps when you need a copy, correction or explanation under the Privacy Policy.

Account access If phone verification or a mobile login leaves you unsure which data is connected…
Wallet status For a DANA, OVO, GoPay or QRIS record, share the payment reference and date.
Privacy change To request correction, deletion where available, or a copy of your stored details, state…
DATA PRACTICE

Explore How We Handle Your Data

The Privacy Policy is practical at each account touchpoint: we separate identity details from payment references where the process allows, use cookies to keep a session working, and apply account checks before…

Collection purpose

We collect account details to create access, complete phone verification and respond to account requests. Payment references from DANA or QRIS help us match a requested cashier action.

Cookies and sessions

Cookies can keep your mobile browser session active and remember basic access settings. You can clear browser data, although doing so may require phone verification again.

Account protection

Before discussing private account data, we may use the phone number and account step already on file. Do not send a password, wallet PIN or full payment credential through support.

Payment matching

A QRIS receipt, virtual account reference or bank transfer detail can help us trace payment status. We use the minimum transaction context needed for that request.

Retention choices

We retain records for the period needed for account operation, transaction checks, security review or legal duties. The Privacy Policy explains how to ask which category applies.

Data changes

You can ask us to correct account details or clarify stored records. Include your account phone number and the specific field, such as contact data or device access.

Ask What wajan4d Privacy Policy Covers

These Privacy Policy answers address the searches we hear most often before an account is opened. They cover payment references, cookies, phone verification, device access and requests to change stored details. If your question concerns a particular record, use the support path with the smallest useful amount of account information.

It explains account data, phone verification, cookies, device sessions, payment references and retention. It also describes how you can request access, correction or clarification through our support path.

Yes. The Privacy Policy covers transaction references from DANA, OVO, GoPay and QRIS, plus bank transfer and virtual account details used to match payment status.

Phone verification connects an account request to the correct account holder and helps protect private records. We may use that account step before discussing data with you.

Cookies can keep a mobile or desktop browser session working. Clearing them may remove session details and lead to another phone verification step when you return.

You can ask for a copy or explanation of stored account data through support. Include your linked phone number and the precise category, such as contact or payment reference data.

Yes, you can request a correction by identifying the field that appears wrong. We may check your linked phone number before changing account or contact details.

Yes. Access and eligibility depend on local law, and our Privacy Policy applies where local law permits. Contact support if you need clarification about a policy request.