Reference

telagatoto Privacy Policy for Indonesia

telagatoto Privacy Policy explains what we collect when you open an account, sign in from a phone, browse Live Roulette, or use DANA and QRIS.

Account dataWallet recordsDevice cookiesAccess requests
telagatoto telagatoto Privacy Policy for Indonesia
CONTACT ROUTES

Privacy Help When Account Details Stall

A clear contact route matters when a login record, wallet reference or account detail looks wrong.

Account privacy request Use the account support path to ask what personal data we hold, why a field is needed, or whether a stored detail can be corrected. We may confirm your login identity before responding, so another person cannot request changes to your telagatoto profile.
Wallet record check If a DANA, OVO, GoPay or QRIS reference appears beside the wrong account activity, send the transaction date and reference through account support. We compare the wallet record with the account ledger before explaining the result or correcting an eligible detail.
Access concern Tell us through the account support route if a new device, repeated login prompt or verification request does not look familiar. We can review the session details, protect the profile and explain which account step is needed before access resumes.
HANDLING PRACTICE

Six Ways We Handle Your Data

We keep this policy practical by linking each data use to an account task you can recognise.

Account creation

We collect the contact and verification details needed to create your account and confirm that a requested change comes from you. Before account access is completed, we may match the submitted phone or email with the profile record and keep the result for security handling.

Device and cookies

A phone or desktop browser can store cookies or session identifiers that keep your login path working and help us detect unusual access. If you clear browser data, you may need to repeat the account step; the lobby may also ask for verification again.

Wallet matching

For DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity, we use transaction references to match a wallet event with the correct account. This supports receipt checks and correction requests without treating a payment reference as a public profile detail.

Account security

We use login events, device signals and verification results to protect your profile from access that does not match your normal account path. When a session appears unusual, we may pause a change or ask you to confirm the account before proceeding.

Retention periods

We keep account, wallet and security records only for as long as needed for the stated account purpose, dispute handling, security checks or a legal requirement. When a record is no longer needed, our process removes it or separates it from direct account identification.

Change requests

You can ask us to correct account data, explain its use, provide an accessible copy where available, or raise a deletion request. We assess the request under applicable rules, verify account ownership and explain any record that must remain for security or legal reasons.

Privacy Policy Questions Before Account Access

These answers address the searches we receive about the telagatoto Privacy Policy, account records and Indonesian wallet activity. They are written for the moment before you open an account or when you need to check an existing profile. If your situation is not covered, use the account support path and include only the details needed to identify your request.

The telagatoto Privacy Policy covers account details, verification results, login events, device cookies, wallet references and game activity linked to your profile. It explains why we use each category, how we protect it and how you can ask about correction, access or removal.

We store the transaction references and account-matching details needed to reconcile DANA, OVO, GoPay and QRIS activity. The record helps us check a receipt or wallet status. We do not use a payment reference as a public profile detail or for unrelated advertising.

Phone verification helps us connect an account step to the person requesting access or a profile change. It can also protect your account when a new device or unusual login appears. We retain the verification result for security handling under the Privacy Policy.

Yes. Send a request through the account support path and identify the email or phone linked to your profile. We may confirm ownership before responding. We can explain available records, correct eligible details and assess a copy request under applicable rules.

Cookies and session identifiers help keep your mobile login connected while you move from the account page to the lobby. Clearing them can end the session and trigger another verification step. The Privacy Policy explains this device use without treating cookies as a separate account.

Retention depends on the purpose of the record, including account security, wallet reconciliation, dispute handling and legal requirements. We remove or separate records when they are no longer needed for those purposes. A specific request can be assessed after account ownership is confirmed.

You can raise a deletion request through account support. We first verify that the request comes from you, then assess which records can be removed. Some account, wallet or security records may need to remain where local law permits or requires continued retention.