Reference

Privacy Policy for wayang4d Accounts

Our wayang4d Privacy Policy shows what data we collect when you open an account, sign in from a mobile device, or connect DANA, OVO, GoPay or QRIS.

Clear collection reasonsWallet data boundariesAccount access controlsContact for data requests
wayang4d Privacy Policy for wayang4d Accounts
ASK OUR TEAM

Get Help With Privacy Policy Requests

A direct support route keeps your Privacy Policy questions separate from ordinary lobby enquiries.

Account privacy desk Send a request from the contact route connected with your wayang4d account.
Wallet status questions For DANA, OVO, GoPay or QRIS data questions, share the date, amount and transaction…
Access and correction help If a phone verification step blocks your account, ask support to explain the data…
DATA CONTROL

What We Do With Your Personal Data

Privacy Policy controls are practical account tools, not broad promises about the whole lobby.

Account creation

When you open an account, we record the contact details and login credentials needed to provide access.

Wallet references

DANA, OVO, GoPay and QRIS can return a payment reference, amount and status to match an account action.

Cookies and devices

Cookies can keep a session active and remember basic consent choices.

Account security

We use login events, verification results and account changes to protect your profile.

Retention period

We keep records for the period needed to operate the account, reconcile a bank transfer or virtual account, investigate security…

Your requests

You may ask what personal data we hold, request a correction, or ask how a Privacy Policy decision was reached.

Privacy Policy Answers For Your Account

These Privacy Policy answers address the account and wallet questions we expect before access is opened. We keep the wording practical: what is collected, why a device check appears, how payment references are handled, and where to send a request. If your case involves a particular transaction or sign-in, include its reference when you contact us so our team can examine the correct record.

The wayang4d Privacy Policy covers data connected with your account, login, phone verification, device session, support request and wallet transaction status. It explains our purposes, security checks, retention approach and request path. Access or eligibility depends on local law, so the policy does not replace local requirements.

We use your phone number to create an account contact, support sign-in checks and complete a clear verification step before account access. It also helps us identify your request when you ask about a record. We do not need your DANA, OVO or GoPay PIN for that process.

Our Privacy Policy describes transaction references and status, not your wallet PIN. When you use QRIS, DANA, OVO or GoPay, the account record may show a reference, amount and result needed for reconciliation. Keep your PIN inside the wallet service and do not send it to support.

Contact us through the account support route and label the message Privacy Policy data request. Provide your registered phone or email, describe the records you want, and include a transaction reference if relevant. We verify that you own the account before sharing account-linked data or explaining its handling.

Yes. Tell support which account detail is inaccurate and what the correct detail should be. For a phone, identity or payment-related change, we may request a verification step before making an update. We will explain whether the change can be made and why, based on account security and local law.

We keep a record only while it supports account operation, payment reconciliation, security review, dispute handling or a legal duty. A bank transfer, virtual account or QRIS reference may therefore remain after the related action. When the purpose ends, the record can be removed or separated through our retention process.

Use the support channel linked to your account and include Privacy Policy in the subject. Explain the concern without sending passwords, wallet PINs or full payment credentials. Our team can review a data, cookie, device or transaction-reference question and tell you the next step for a verified request.