Reference

Privacy Policy For Your wild4d Account

wild4d Privacy Policy explains what we collect when you create an account, use the mobile lobby, or connect DANA, OVO, GoPay and QRIS.

Clear data purposesWallet checks explainedYour contact choicesMobile access covered
Explore Our Lobby Read FAQ
wild4d Privacy Policy For Your wild4d Account
CONTACT PATHS

Privacy Help Beside Your Account

A clear contact route matters when a login record, wallet check or privacy request needs attention. We keep policy support close to the account and cashier paths, so you can explain the issue without guessing which team should receive it. Include the contact detail linked to your account, the device path you used and the relevant payment reference; never send a password or full wallet credentials. Our team can then locate the request and explain the next account step.

Team online

Account privacy request

Use the support path connected to your wild4d account when you want to ask what data we hold, correct a contact detail or understand a verification record. Tell us whether the request began on mobile or desktop so we can match it to the right access event.

Wallet record question

For a DANA, OVO, GoPay or QRIS record, provide the payment reference and approximate time shown in your wallet. We use that detail to locate the related account event, while you should keep wallet PINs, passwords and one-time codes private.

Security concern

If your account opens unexpectedly, a session looks unfamiliar or a phone has been lost, contact us through the account support route immediately. We may ask for account identifiers and verification details before discussing records or helping protect access.

SIX DATA CONTROLS

Inside wild4d Privacy Handling

Privacy is part of the account flow, not a separate promise shown after a wallet action. We record only the details needed to operate access, protect sessions, process account-linked payment checks and…

Account creation

When you open an account, we use the contact details and verification step you provide to create a distinct login record. Clear phone verification can help separate your account from another session and lets us respond to access questions without exposing another person’s data.

Cookie settings

Cookies can help remember a session, maintain sign-in flow and connect the page you opened with the account action you requested. You can manage browser cookie controls, although turning them off may interrupt login continuity or require another verification step.

Wallet matching

A DANA, OVO, GoPay or QRIS status is handled as an account-linked payment event. We use the reference needed to identify that event, check its state and answer a receipt question; wallet passwords and PINs are not requested through support.

Session security

We use account and device signals to help identify unusual sign-in behaviour, including a change between mobile browser and desktop access. If a session does not look familiar, we may pause a request and ask for an account verification step before sharing personal data.

Retention choices

We retain records for as long as they serve account operation, security checks, dispute handling or a legal requirement. The period can differ by record type. Ask us about a specific login, wallet reference or verification record and we will explain the applicable retention reason.

Change requests

You can ask us to correct account data, explain its use or clarify whether a record can be removed. Send the request through the support route with enough detail to locate your account, but do not include your password, wallet PIN or one-time code.

Privacy Policy Answers For wild4d

These Privacy Policy answers address the account, device, cookie and wallet questions we expect from Indonesian customers before they create an account. Each answer stays focused on data handling and the steps available when you need clarification. If your question concerns a particular record, include its account reference through the support path rather than posting personal details in a public channel.

It covers data connected with your account, login sessions, phone verification, cookies, wallet references and support requests. It also explains why we use those records, how security checks affect access, how retention can work and how you can ask for correction or clarification.

We may collect the contact and verification details you submit, account activity needed to operate access, device or session signals used for security, and payment references from DANA, OVO, GoPay, QRIS, bank transfer or virtual account actions.

Wallet records are linked to the account action they support, such as a deposit status or receipt check. We use the reference and status needed to trace that event. We do not ask you to share a wallet PIN, password or one-time code.

Yes. Send a correction request through the account support route and identify the record or contact detail that needs changing. We may ask for an account verification step before making a change, so another person cannot alter your account data.

Retention depends on the type of record and whether it supports account operation, security checks, payment clarification, dispute handling or a legal requirement. Ask about a specific login, verification event or wallet reference and we will explain the reason for its retention.

Cookies can support sign-in continuity, session protection and the connection between a page and your requested account action. You can adjust browser controls, but disabling cookies may require repeated login or verification and may prevent part of the account path from working.

Use the support route connected to your account and describe whether you need access, correction, deletion clarification or a retention explanation. Add the relevant device path or payment reference when useful, and remove passwords, PINs and one-time codes before sending.

Related Pages

wild4d Indonesia Andar Bahar macaupool About Us Access guide