Reference

Privacy Policy for Your tongwd Account

tongwd's Privacy Policy explains what we collect when you open an account, sign in from a phone, or use DANA, OVO, GoPay and QRIS.

Account recordsWallet statusCookie choicesSecurity requests
Browse Our Lobby Read FAQ
tongwd Privacy Policy for Your tongwd Account
CONTACT ROUTES

Privacy Help Beside Your Account

A clear contact path helps when you cannot identify a device record or payment reference.

Account request Ask us to locate, correct or explain personal details connected with your tongwd account.
Payment reference For a DANA, OVO, GoPay or QRIS privacy question, share the transaction reference and…
Access concern If a phone or browser keeps returning to a security check, tell us the…
DATA PRACTICES

What We Do With Your Account Details

Privacy controls work best when the account steps are clear. We use contact details to support sign-in and phone verification, device signals to help identify unusual sessions, and…

Account collection

When you create an account, we collect the details needed for account access and phone verification.

Payment matching

A DANA, OVO, GoPay or QRIS action can create a reference, status and timing record.

Device signals

Your phone or browser may provide session and device signals during login.

Cookie control

Cookies can retain a session choice and help security checks run across the account path.

Retention requests

We keep records only for the period needed for the stated account, payment, security or support purpose, subject to legal…

Changes and contact

To request access, correction or another privacy action, use the support route visible in your account and identify the relevant…

Privacy Policy Questions for tongwd

These Privacy Policy answers focus on the account actions you are most likely to question in Indonesia: sign-in, phone verification, wallet references, cookies, device checks and requests to change or access a record. If your situation is not covered, describe the exact account step through the support path and we will assess it where local law permits.

It covers account details, phone verification, sign-in and device signals, cookies, support messages, and payment references from DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity. It also explains how to ask about access, correction and retention for your records.

Phone verification connects the sign-in step to the correct account and helps us respond to account-access requests. We may use the verification status for security checks, but you should not send a one-time security code or wallet password through support.

Yes. The Privacy Policy covers the payment references and status details needed to match a DANA or QRIS action with your account. It can also cover comparable OVO, GoPay, bank transfer and virtual account references, without requiring your wallet password.

Use the support route shown after sign-in and name the account record you want checked, such as a phone verification entry, device session or payment reference. We may confirm account ownership before responding, and the request outcome depends on local law.

Yes. Send a correction request through the account support path and identify the field that is wrong. Explain the account step where it appears, such as sign-in or phone verification. We will assess the request and may need ownership checks before making a change.

Cookies can keep a session choice and help security checks work when you move through the account path on a phone. Browser controls let you clear or restrict them. After that, you may need to sign in again or repeat verification.

No record is described as permanent. We retain account, device, payment and support details for the stated operational or legal purpose, then assess them under our retention process. You can ask which category applies to your record and how local law affects that request.

Related Pages

tongwd Indonesia Access guide Terms Guide Indonesia FAQ Esports Mobile Legends