Reference

Privacy Policy For Your landak toto Account

Our Privacy Policy explains what we collect when you open a landak toto account, sign in, use Live Baccarat or check a wallet record, and why each detail…

Account dataCookie choicesPayment recordsAccess requests
landak toto Privacy Policy For Your landak toto Account
CONTACT YOUR WAY

Privacy Help For Login And Wallet Questions

A clear contact path matters when a privacy question affects your account access or a wallet record. We ask you to include the account phone number, the request you are making and any relevant payment reference, while leaving out passwords and wallet PINs. Our team uses those details to locate the right record, confirm that the request comes from you and explain the next step. If you are checking access from Jakarta, use the same account route shown on this page; the handling of a request depends on local law.

Team online

Account request

Send a privacy request through the contact route connected to your landak toto account. Include your phone number and the type of action you need, such as access, correction or removal. We may ask for an account step to confirm your identity before sharing personal records.

Payment record

For DANA, OVO, GoPay or QRIS questions, provide the transaction reference and approximate time rather than a wallet PIN. We compare the reference with the account record, explain what we hold and separate payment status data from credentials managed by the wallet provider.

Access concern

If a phone verification prompt or unfamiliar device signal blocks your request, tell us which sign-in step stopped. We use the account history and device details to protect your data, then explain whether the requested action can proceed where local law permits.

DATA HANDLING

What We Do With Account And Device Data

We handle privacy as an operating task rather than a label placed at the bottom of a page.

Account identity

We use your account details and phone verification result to distinguish your request from another person using the same device. This reduces the chance of sending account data to the wrong contact. We do not ask you to place a password or wallet PIN inside a privacy message.

Device signals

Browser type, device markers, login time and related security signals can be recorded when you access the account. These details help us investigate an unfamiliar sign-in or repeated verification failure. They are considered alongside account information, not treated as a public profile.

Cookies

Cookies can keep an account session active, remember a consent choice and help us understand whether a page request completed. You can manage them in your browser. If you block required cookies, login or the privacy request path may ask you to repeat a step.

Payment references

Our records may show that a DANA, OVO, GoPay, QRIS, bank transfer or virtual account transaction was submitted, including its status and reference. We use this to reconcile account activity. Wallet credentials and banking login details remain outside the fields we request from you.

Retention period

We keep each category only while it supports account access, security checks, dispute handling or a legal requirement. When a retention reason ends, the record is removed, anonymised or restricted according to the process that applies. A deletion request depends on local law and the record involved.

Change request

To ask for a copy, correction or eligible removal, use the account contact route and describe the exact data involved. We may verify your phone before responding. Our reply explains what action was taken, what cannot change and why, where local law permits that explanation.

Privacy Policy Questions For Indonesia Accounts

These Privacy Policy answers cover the questions we expect when you are deciding whether to open an account or checking an existing record. We focus on practical points: the phone step, wallet references, cookies, device activity and requests for access or correction. The same policy applies whether you connect from a mobile browser in Indonesia or return to the account from another supported device. Eligibility and data rights depend on local law.

It covers account details, phone verification, sign-in and device signals, cookies, payment references and activity records linked to your account. It also explains why we use each category, how long we may retain it and how you can request access or correction where local law permits.

No. When you use DANA or OVO, our records can include a transaction reference, status, amount and time for account reconciliation. We do not ask for your wallet password or PIN. If a message requests either one, do not send it through the privacy contact route.

Phone verification helps connect an access request to the correct account and reduces mistaken disclosure when several people use one device. It can also support account recovery and security checks. We use the result for those purposes, subject to the requirements that depend on local law.

Yes, send a correction request through the account contact path and identify the field that is wrong. We may confirm your phone number before changing it. Some records must remain accurate for security, payment reconciliation or legal reasons, so the outcome depends on local law.

Required cookies can maintain a login session and preserve your consent choice, while other cookies help us understand page completion. You can change browser settings or clear stored cookies. After that, you may need to repeat phone verification or another account step to continue.

We retain QRIS, bank transfer and virtual account references while they are needed for account matching, payment questions, security work or a legal obligation. The period can differ by record type. You can ask what we hold, but removal depends on local law and the reason for retention.

Use the contact route linked to your account and state that you want a copy of your personal data. Include your account phone number, but never include a password or wallet PIN. We verify the requester, locate eligible records and explain the response where local law permits.