Reference

Privacy Policy For Your tanduktoto1 Account

Our Privacy Policy explains how we handle the account details you provide before access to the lobby, including your phone number, verification records and wallet activity.

Account dataWallet recordsDevice accessPolicy requests
tanduktoto1 Privacy Policy For Your tanduktoto1 Account
CONTACT PATHS

Get Privacy Help From Your Account

A clear contact route helps you act on this Privacy Policy without searching through unrelated pages.

Account privacy request Send your privacy question through the account support path and identify the phone number…
Wallet record check If your request concerns DANA, OVO, GoPay or QRIS activity, include the relevant transaction…
Access concern Tell us if a login alert or device session seems unfamiliar.
DATA PRACTICES

Six Ways We Handle Your Data

We keep this policy practical by linking each data practice to a point you can recognise in your account journey.

Phone verification

Before we discuss private account details, we may use the phone verification step attached to your profile. This helps us separate a genuine request about your data from a message sent by someone who cannot confirm control of the account.

Payment references

A DANA, OVO, GoPay or QRIS reference can be connected with account activity so we can trace status questions. We use the reference for that operational purpose and do not need the wallet PIN to respond to a policy request.

Browser cookies

Cookies may keep a browser preference or session setting available when you return to the lobby. You can clear them through your browser controls; doing so may require you to sign in again before viewing account areas.

Device signals

We may record device type, browser details and login time to identify unusual access patterns. These signals support account protection and investigation; they are handled as access data rather than presented as a public profile about you.

Retention checks

We keep personal and transaction records only while they serve the stated account, support, security or legal purpose. When a retention period ends, we assess the record for deletion, restriction or continued storage where a lawful reason still applies.

Change requests

Ask us to correct an inaccurate detail, explain a stored record or address a deletion request through the account support path. We first verify the requester, then assess the request under the Privacy Policy and local law.

Privacy Policy Questions About tanduktoto1

These Privacy Policy answers focus on the account actions you are most likely to question before access. They explain what information may be collected, why phone verification matters, how wallet records are handled and where to send a request. For a case involving your own account, use the account support path and provide only the details needed to locate the record. Access and eligibility depends on local law.

It covers account details, phone verification, login and device signals, cookies, support messages and payment references linked to DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity. It also explains retention, security handling and how you can request access or correction.

Phone verification helps us confirm that a request about your Privacy Policy record comes from the person controlling the account. We may require that step before discussing private details, changing account data or responding to an access request.

Yes. The policy covers references and status details connected with DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity. These records help us trace an account transaction, while your wallet PIN or private wallet credential is not needed for a policy request.

We may use device type, browser details and login timestamps to investigate unusual access and protect account sessions. The Privacy Policy treats these as access and security signals. They are not presented as a public profile, and you can ask what record relates to your account.

You can send a request through the account support path and identify the phone number linked to your profile. After verification, we assess access or correction requests against the Privacy Policy and local law, then explain the available response for your account.

We retain information while it serves the account, support, security or legal purpose described in the Privacy Policy. When that purpose ends, we assess deletion, restriction or continued storage where a lawful reason applies. Ask support about a particular record rather than sending unnecessary private details.

Use the account support path for questions about stored data, cookies, device access, phone verification or wallet references. Include a concise description and the relevant account identifier. We may verify control of the account before sharing private information or processing a change request.