Reference

totolagi Privacy Policy for Your Account Data

Our Privacy Policy explains what we collect when you open an account, sign in from an Android or iPhone browser, and use DANA, OVO, GoPay or QRIS.

Clear data purposesWallet status checksAccount access choicesPrivacy contact path
totolagi totolagi Privacy Policy for Your Account Data
ACCOUNT HELP PATH

Where To Ask About Privacy

A direct support route helps you ask about the Privacy Policy without guessing which team handles your request.

Account support Use the signed-in support path for a copy of your stored account details, a correction request or clarification about phone verification data. Include your account identifier so we can avoid matching the wrong record.
Wallet status If a DANA, OVO, GoPay or QRIS reference appears incorrectly, send the receipt reference rather than your wallet password. We can compare the payment status with the account record linked to that transaction.
Privacy request For access, correction or deletion questions, use the privacy route shown in your account area. We may ask for an account step or phone verification detail before making a change to protect your data.
DEVICE DATA PRACTICE

How We Handle Data At totolagi

Our handling practices follow the actions you take rather than collecting details without a purpose.

Account records

We use your account identifier, phone verification result and sign-in history to confirm which account is requesting access. This helps us separate your request from another account using a shared device or network.

Payment references

DANA, OVO, GoPay, QRIS, bank transfer and virtual account references may be stored with transaction status. We use those references to reconcile the account step, not to collect your wallet password.

Browser signals

When you move from login to a lobby such as Live Casino or Great Rhino on an Android or iPhone browser, device and browser signals can help detect unusual access and keep the session connected.

Cookies

Cookies can remember a session, preserve selected settings and help us understand whether a page request came from your active account. You can manage cookies through your browser settings, though some account steps may then need repeating.

Account security

We limit internal access to personal records and use verification before discussing account data. If you contact us about a Counter-Strike 2 or Rocket Crash activity record, we still confirm the account first.

Retention and changes

We retain records only as long as needed for account operation, payment reconciliation, dispute handling or legal duties. To request correction, deletion or a copy, use the privacy contact path and explain the change clearly.

Privacy Policy Questions For Indonesia

These answers address the searches we hear before an account is opened or a wallet is connected. The Privacy Policy applies to account data, device access, cookies, payment references and support requests, including activity connected with Live Casino, Super Bingo or Mega Fishing. If your situation is unusual, contact us through the account privacy route.

It covers data collected during account creation, phone verification, login, wallet activity, browser access, support messages and privacy requests. It also explains cookies, retention, account protection and how to ask for changes.

We use the verification result to connect account access and privacy requests to the correct person. It can also help us investigate unusual login activity without asking you to share a wallet password.

Yes. The policy covers payment references and status linked to DANA, QRIS, OVO, GoPay, bank transfer and virtual account activity. We use those records to reconcile an account action and address disputes.

Yes. Use the privacy route shown after signing in, describe the field that needs correction and provide the account identifier used during verification. We may confirm the request before changing the record.

Send an access request through the account support path and specify the records you want, such as login details, payment references or support messages. We will use account checks before releasing data.

Retention depends on the type of record and whether it is needed for account operation, payment reconciliation, dispute handling or legal duties. We remove or restrict records when the relevant need ends.

Access and eligibility depends on local law. If local rules limit account access or data handling in your area, those rules apply, and you should check the Privacy Policy before opening an account.