Reference

tarung toto Privacy Policy for Your Account

Our tarung toto Privacy Policy explains what account, wallet and device details we collect, why we use them, and how you can ask about your records.

Account clarityWallet recordsDevice controlsLocal-law access
tarung toto tarung toto Privacy Policy for Your Account
REQUEST ROUTES

Contact Us About Privacy Requests

A clear contact route helps you ask about the Privacy Policy without describing your concern repeatedly. Start from the support path linked in your account area and include the phone number or wallet reference connected to the request. We use those details to locate the right record, while you should avoid sending a wallet password or full payment credential.

Team online

Account privacy path

Use the support route beside your account area for a copy request, correction request, or question about phone verification records. Include your registered contact detail so we can identify the relevant account.

Wallet status question

For DANA, OVO, GoPay or QRIS records, send the transaction reference and displayed status rather than secret wallet credentials. We can then check which account event the Privacy Policy request concerns.

Device access concern

If a sign-in alert or device record looks unfamiliar, contact us through the account support path and describe the device type and approximate time. We can direct the privacy and account-security response.

DATA PRACTICE

Data Handling Across Your Account Path

Privacy decisions follow the same account steps you see on screen: account creation, phone verification, sign-in, wallet selection and support contact.

Account creation

When you open an account, we use the submitted contact details to create the account record and support sign-in checks. A clear phone verification step helps connect later requests to the correct account.

Wallet references

A DANA, OVO, GoPay or QRIS transaction can leave a reference, amount status and time in the account record. These details help us match a wallet event without requesting your private wallet password.

Cookies and sessions

Cookies and session storage can keep sign-in state and remember device choices during your account visit. You can manage cookie permissions through your browser, although changing them may affect the sign-in path.

Account security

We may record device type, sign-in time and related signals when checking unusual account activity. These records support an account-security response and are handled under the purposes stated in our Privacy Policy.

Retention period

We retain records only for the operational, dispute, security or legal purpose that requires them. When a record no longer has a stated purpose, our handling process moves it toward deletion or anonymisation.

Changes and questions

You can ask us to correct account details, explain a wallet record, or clarify a cookie setting through the support route. We may request account details before changing a record to protect your privacy.

Privacy Policy Questions for Indonesia

These Privacy Policy answers address the account and wallet questions you may have before opening an account. We keep the route practical: check the current policy page, use the support path, and include only the record details needed to locate your request.

It covers account details, phone verification, sign-in and device signals, cookie use, support messages, and wallet records linked to DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity.

Phone verification helps connect account access and privacy requests to the correct account. We use the verification record for sign-in and account-security checks, according to the purposes described in the Privacy Policy.

Yes. The Privacy Policy covers transaction references and displayed status details connected with DANA and QRIS, as well as OVO, GoPay, bank transfer and virtual account routes.

Use the support route linked in your account area and ask for a data copy under the Privacy Policy. Include your registered contact detail, but never send a wallet password or full payment credential.

Yes. Send a correction request through the account support path and identify the incorrect field. We may verify account ownership before changing it, so another person cannot alter your records.

Cookies and session storage can retain sign-in state and device choices on your mobile browser. Browser controls let you change cookie permissions, though some account access steps may then work differently.

Contact us through the support route and name the record type, such as a QRIS reference, phone verification event or support message. We can explain its stated purpose and retention handling.