Reference

Open wings138 With Privacy Clarity

Our Privacy Policy explains what we collect when you create an account, sign in from a phone or desktop, and use DANA, OVO, GoPay or QRIS.

Account choicesWallet dataDevice accessContact path
Explore Our Lobby Read FAQ
wings138 Open wings138 With Privacy Clarity
CONTACT THE POLICY TEAM

Ask About Your wings138 Privacy Policy

A clear contact route matters when you want to understand a record or change an account detail. Our support path handles privacy questions alongside login and wallet-status checks, so you can explain the issue without repeating the full account story. Include your registered contact detail, the device path you used, and any relevant DANA, OVO, GoPay or QRIS reference. Do not send a password or wallet PIN. We use the details in your request to locate the right account event and reply with the next policy step.

Team online

Account questions

Ask us which account details we hold, why a verification step appeared, or how to correct a contact record. We first confirm that the request comes from the account holder before discussing personal data or making an account change.

Wallet records

If a DANA, OVO, GoPay or QRIS receipt does not match your account status, send the transaction reference through the support route. We use that reference to trace the payment event without asking for your wallet PIN.

Access concerns

Tell us if a phone, desktop browser or familiar sign-in path no longer matches your account activity. We can review the access details, protect the account and explain which privacy step applies before further action.

HOW WE HANDLE RECORDS

Check How Privacy Works Inside wings138

Privacy decisions are tied to real account events rather than broad platform statements. We separate sign-in details, payment references and support messages so each request can be checked against the relevant record.

Account creation

When you open an account, we collect the contact and verification details needed to establish access. Clear phone verification helps us distinguish your request from an unknown sign-in and gives us a reliable route for privacy replies.

Device signals

A phone or desktop browser can provide sign-in time, browser type and related security signals. We use these details to compare access patterns and investigate an account alert, not to ask for your device passcode.

Cookie choices

Cookies and similar browser storage can keep the account path working and remember a selected session. You can review browser controls to remove them, although clearing session data may require you to sign in again.

Payment matching

DANA, OVO, GoPay, QRIS, bank transfer and virtual account records may include a reference, amount status or account link. We use the minimum payment detail needed to reconcile the event and answer a receipt question.

Security checks

We may compare phone verification, sign-in activity and wallet status before allowing an account action to continue. These checks help us respond to unusual access while keeping your password, PIN and private wallet credentials out of support messages.

Retention requests

We keep records for the period needed to secure the account, resolve a payment question or meet a valid legal requirement. You can contact us to ask what remains, request a correction or ask why a record still needs to stay.

Search Your wings138 Privacy Policy Questions

These Privacy Policy answers focus on the account steps you are most likely to check before access. They cover personal data, device activity, wallet references, cookies and requests for changes. If your situation involves a particular DANA, OVO, GoPay or QRIS event, include its reference when you contact us. Access depends on local law, so the available response can vary by your location.

The Privacy Policy covers data connected with your account, phone verification, sign-in device signals, cookies, payment references and support requests. It also explains why we use those records, how long they may remain and how you can ask about correction or access where local law permits.

We may collect the contact and verification details required for account access, together with sign-in activity and support messages. The exact record depends on the account step you take. We do not need your wallet PIN to check a DANA, OVO, GoPay or QRIS receipt.

Yes. The Privacy Policy covers payment references and status details connected with DANA, OVO, GoPay and QRIS, as well as bank transfer and virtual account events. We use those details to match an account action, investigate a receipt issue and respond without requesting private wallet credentials.

We use limited device and browser signals, such as access time and browser type, to protect the account and review unusual sign-ins. A phone session and desktop session may look different in our security records, while both can connect to your verified account.

Where local law permits, you can contact us to request correction of an inaccurate account detail or ask what record supports a particular account action. Include your registered contact detail and the relevant event, but leave out passwords, PINs and full wallet credentials.

We retain account, payment and support records only while they are needed for access security, payment matching, dispute handling or a valid legal requirement. The period can differ by record type. Contact us if you want the reason for continued retention explained.

Use our support route for a Privacy Policy request and describe whether it concerns account access, device activity, cookies or a DANA, OVO, GoPay or QRIS reference. We may confirm your account details first so personal data is discussed with the correct account holder.

Related Pages

wings138 Indonesia Auto Roulette About Us Register League of Legends