Reference

wonder4d Privacy Policy For Your Account

wonder4d Privacy Policy explains how we collect, use and protect the details connected with your account, wallet activity and device access.

Account dataWallet recordsCookie choicesSecurity requests
wonder4d wonder4d Privacy Policy For Your Account
CONTACT ROUTES

Privacy Questions And Account Requests

A direct request helps us locate the right account record without asking you to repeat the same details. When you contact our support route about this Privacy Policy, include your registered phone number, the request type and any relevant wallet reference, but do not send a password or full payment credentials. We use the account details you provide to confirm identity before discussing a correction, access request or deletion request. If a wallet status stalls, the same route can connect the privacy question with the account record.

Team online

Data access request

Ask us which personal details are connected with your wonder4d account and why they are used. We may request phone verification before releasing account-specific information, so the response reaches the person who controls the account rather than an unrelated contact.

Correction request

Send the inaccurate field, the corrected value and your registered phone number. We can review account details such as contact data or wallet status references, then apply an eligible change after identity checks and any records that must remain for legal or security reasons.

Wallet record query

For a DANA, OVO, GoPay, QRIS, bank transfer or virtual account question, share the transaction reference and date. We use that limited detail to trace the status, while payment credentials remain outside the support message and are never requested in full.

DATA PRACTICES

What We Do With Your Personal Details

Privacy at wonder4d is managed through practical account controls rather than vague promises. We separate sign-in details from payment references where our systems allow, limit internal access to work needs and inspect…

Account collection

We collect the details needed to create and maintain your account, including contact information, phone verification status and sign-in events. If you choose DANA, OVO, GoPay or QRIS, we also receive the transaction reference and status needed to match the wallet action.

Device signals

Your browser or phone can send technical signals such as device type, session time, language preference and security events. These signals help us recognise an unusual login and protect the account; they are not used as a substitute for the phone verification step.

Cookie controls

Cookies can keep your signed-in session active and preserve selected settings between pages. You can adjust cookie controls in your browser, although blocking necessary cookies may interrupt the path from login to the lobby or require you to verify the account again.

Security handling

We use access controls and verification checks around account records. We do not ask you to place a password or complete wallet credential into a support message. When a login or payment status looks unusual, additional account checks may be required before details are discussed.

Retention choices

We retain account, support and transaction references only for the period needed to provide the requested service, investigate security events or meet a legal duty. A deletion request can be assessed, but some records may need to remain when a lawful retention reason applies.

Policy changes

If our handling of personal details changes, we will place the revised Privacy Policy at this page and update its effective wording. Before opening an account, check this page again so you understand the current use of data, cookies and wallet references.

Privacy Policy Answers For wonder4d

These Privacy Policy answers focus on the account questions Indonesian customers commonly ask before opening an account. They explain the records linked with phone verification, device sessions and local wallet activity without turning the policy into a general lobby description. If your situation is personal or involves a specific transaction, use the support route and include only the reference needed to locate the record. Account access depends on local law and the details shown here may be updated when our data practices change.

The wonder4d Privacy Policy covers account details, phone verification, sign-in events, device signals, cookies, support messages and payment references. It explains why we use each category, how we protect it and how you can request access, correction or deletion where local law permits.

Phone verification helps connect account access with the person who controls the registered contact. We may use that step before discussing personal records, correcting an account field or responding to a wallet query involving DANA, OVO, GoPay or QRIS.

Yes. The Privacy Policy includes transaction references and status information linked with DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity. We use those records to trace a request or answer a status question, without asking you to send full payment credentials.

We may handle device type, browser details, session time, language settings and security signals from the phone or computer used to sign in. These details help protect your account and keep the login path working; they do not replace phone verification.

Contact our account support route with your registered phone number, the request you want to make and the specific field or record involved. We may verify your identity first, then assess the request under the Privacy Policy and applicable local law.

You can submit a deletion request through the support route. We will assess which details can be removed, but account, security or payment references may need to remain for a lawful retention period. We will explain the outcome using the contact details on your account.

The current Privacy Policy remains available at this page, including its handling of cookies, account records and wallet references. If you need clarification about a change, contact support with the section or wording that concerns you and avoid sending passwords or full payment credentials.