Reference

wahanatoto2 Privacy Policy for Your Account

Our Privacy Policy explains what we collect when you create an account, verify your phone, open Andar Bahar or Fish Hunter, and use DANA or QRIS.

Account clarityWallet recordsCookie choicesPolicy requests
wahanatoto2 wahanatoto2 Privacy Policy for Your Account
CONTACT ROUTES

Privacy Help Beside Your Account

A clear contact route helps you ask about the Privacy Policy without explaining your whole account history. Tell us which account step, device path, or wallet record concerns you, and we will use the details you provide to locate the relevant entry. Our support path is for access questions, correction requests, and privacy concerns.

Team online

Account questions

Use the support route when your phone verification record, login event, or account detail appears incorrect. Include the account identifier so we can check the right record.

Wallet records

For DANA, OVO, GoPay, QRIS, bank transfer, or virtual account data, state the payment reference and account step involved. We use that detail to trace the stored entry.

Privacy requests

Ask us to explain, correct, or review personal data through the available support contact. We may verify account ownership before discussing records connected with your account.

HANDLING DETAILS

What We Do With Your Data

Our handling process follows the account event that created each record, rather than treating every visit alike. A phone verification, a QRIS receipt, and a mobile browser session can require different checks.

Account data

We may collect details needed for account creation and phone verification. These details help connect your login, account status, and privacy request to the correct account.

Device signals

Browser type, device path, session time, and security events can help us identify unusual access. We use these signals for account protection, not unrelated personal profiling.

Cookies

Cookies can remember session choices and help the account page load correctly. Your browser settings provide controls, although changing them may affect sign-in or policy access.

Wallet security

Payment references from DANA, OVO, GoPay, QRIS, bank transfer, or virtual account activity may support receipt matching and account checks without replacing your wallet provider.

Retention period

We retain account, security, and transaction records for the period needed for account operations, dispute checks, and applicable legal duties, then remove or restrict them when appropriate.

Change requests

You can ask us to correct account data, explain its use, or review a deletion request. We may request account verification before changing or disclosing personal records.

Privacy Policy Questions for Indonesia

These answers address the privacy searches we hear most often from Indonesian account holders. They explain how the Privacy Policy relates to account creation, phone verification, mobile access, wallet references, cookies, and requests for data changes. If your situation is not covered, use the support path with the account step or payment reference involved.

The Privacy Policy covers account details, phone verification, device and browser signals, cookies, security events, support messages, and payment references linked to DANA, OVO, GoPay, QRIS, bank transfer, or virtual account activity.

Phone verification connects account access to the correct account and helps us check unusual login activity. We may use the verification record when you ask about account data or request a correction.

Yes. The policy covers information created when you sign in from a mobile browser, including device type, session events, cookies, and security signals used to protect your account during lobby access.

We may retain payment references, receipt details, and status information needed to match a DANA or QRIS transaction with your account. Wallet credentials remain with the relevant payment provider.

Yes. Contact our support path with the account identifier and the specific detail you believe is wrong. We may verify account ownership before reviewing, correcting, restricting, or explaining that record.

We keep account, security, support, and transaction records only for operational needs, dispute checks, and applicable legal duties. When a record is no longer needed, we remove or restrict it where appropriate.

Yes. Ask through the privacy contact route if you want clarification about cookies or session storage. Your browser controls can limit cookies, though sign-in and policy access may then work differently.