Reference

Open wd333 Privacy Policy Before Account Access

Our Privacy Policy explains what wd333 collects, why we use it and how you can ask about your account data before opening an account.

Clear data purposesWallet record contextAccount request pathMobile policy access
wd333 Open wd333 Privacy Policy Before Account Access
ASK OUR TEAM

Contact Support About Privacy Requests

A direct support route helps when you want to understand a data record, correct an account detail or ask why a wallet status appears in your account history.

Account data questions Use the account support route when you want to ask what personal data is held for your profile. Include your registered phone number and a clear request, while leaving out your password, one-time codes and complete DANA, OVO or GoPay credentials.
Wallet record checks For a privacy question about QRIS, bank transfer or virtual account records, share the transaction date and reference fragment visible in your account. We use those details to find the relevant record without requesting your wallet PIN or full banking information.
Correction requests If your name, phone detail or account record needs correction, contact support through the route displayed after login. We may ask for an account verification step before changing data, so a request cannot be made by someone using your device without permission.
DATA HANDLING

Explore How wd333 Handles Your Data

Privacy decisions should be understandable at the point where you open an account, check a wallet record or return to the lobby from a mobile device.

Account details

We use your phone number and account details to create access, complete phone verification and connect your profile with the account activity you request. The Privacy Policy explains which fields are needed and which details are optional when you contact us.

Cookie choices

Cookies can help remember a signed-in session and support the path from login to a mobile lobby. Our Privacy Policy explains their purpose and how browser settings can affect access, so you can decide whether to keep or remove them.

Account security

We may check phone verification, login details and unusual account activity before discussing private data or changing account records. Keep one-time codes private and sign out on shared devices, especially after checking QRIS or bank transfer status.

Payment references

DANA, OVO, GoPay and QRIS references help us match a wallet event with the correct account request. We do not need your wallet PIN or complete banking password for a Privacy Policy question or a receipt-status check.

Retention periods

We retain account and transaction-related records only for the purposes and periods described in the Privacy Policy, including operational, security and legal needs. The policy route explains what may remain after an account request and why deletion can have limits.

Change requests

You can ask us to access, correct or clarify personal data through the support path shown in your account area. Give enough detail to identify the request, and we may verify account ownership before providing or changing any private record.

Find Privacy Policy Answers Before Joining

These Privacy Policy questions reflect the account steps Indonesian customers usually want clarified before they proceed. Each answer points back to a practical action, from checking cookies on a phone to asking about a DANA or QRIS reference. If your situation is not covered, use the support route in your account area and describe the specific record or request.

The wd333 Privacy Policy covers account details, phone verification, login activity, cookies, payment references, security checks, retention and requests to access or correct data. It also explains how records connected with DANA, OVO, GoPay, QRIS and account activity may be handled.

We use your phone number to create and identify your account, complete the phone verification step and help protect private account discussions. The Privacy Policy explains the purpose of this data and the support route if your number needs correction.

Yes. The Privacy Policy covers references connected with DANA and QRIS, along with OVO, GoPay, bank transfer and virtual account activity when those records are linked to your account. Share a date or reference fragment for a focused support request.

Use the support contact shown in your account area and ask for an account data access request. Include your linked phone number and enough detail to identify the profile, but never send your password, one-time code, wallet PIN or full banking credentials.

You can request a correction through the account support route when your phone detail, name or another account record is inaccurate. We may complete an ownership check before making a change, and the Privacy Policy explains how that request is processed.

Cookies can remember a login session and help the mobile path return you to the account or lobby. Browser settings may remove or restrict them, which can require another login. The Privacy Policy explains cookie purposes and the available browser controls.

Yes. Account access and eligibility depend on local law. The Privacy Policy should be read together with the access conditions shown for your region. If you need clarification about a location or account record, contact support through the route available after login.