Reference

Privacy Policy for koi toto login

koi toto login Privacy Policy explains what we collect during phone verification, how we use account and wallet records, and how you can request changes.

Phone verification clarityDANA and QRIS recordsCookie choicesContact request path
koi toto login Privacy Policy for koi toto login
CONTACT PATHS

Where To Ask About Privacy Policy

A clear contact route matters when you want to question a record rather than troubleshoot a wallet.

Account privacy request Use the support contact shown after account access and state whether you want to inspect, correct, restrict, or remove personal data. Add your registered phone number so we can match the request without asking for your password.
Wallet record question For DANA, OVO, GoPay, QRIS, bank transfer, or virtual account data, include the payment reference and date. We can then separate a wallet-status question from a request about the personal information attached to that transaction.
Login or device concern If a phone, browser, or sign-in event looks unfamiliar, contact us through the account support route and describe the device path. We can review the related access record and explain which security step applies next.
DATA HANDLING

What Our Privacy Policy Covers In Practice

Privacy Policy details are useful when they connect to an action you can take. We explain how account records move through phone verification, how cookies support a returning browser, and how payment…

Account data

We may hold the details needed to create and maintain your account, including contact data, verification status, login events, and support history. Our Privacy Policy explains why each category is used and which request route applies.

Cookie controls

Cookies can remember a session, support sign-in continuity, and help us understand technical errors on your browser. The policy distinguishes necessary cookies from measurement tools and explains how you can adjust browser settings.

Payment references

A DANA, OVO, GoPay, or QRIS transaction may create a reference, timestamp, amount status, and account link. We use these details to reconcile records and answer a specific wallet question, not to request your private wallet password.

Mobile security

When you move from the mobile login screen to the lobby, we can record device and access signals used for account protection. If a new device appears, phone verification may be needed before access continues.

Retention requests

Our Privacy Policy explains how long different records may be retained for account operations, security checks, payment reconciliation, or legal duties. You can ask which category applies to your data and whether removal is available.

Change contact

To request a correction, access copy, or deletion where applicable, contact us through the support route connected to your account. We may ask for verification so a data change is not made by someone else.

Privacy Policy Questions For Your Account

These Privacy Policy answers address the searches we expect before account access: what we collect, how wallet records are handled, what happens on a mobile device, and how you can contact us. If your situation is not covered, use the account support route and include only the details needed to identify the request.

It covers account creation, phone verification, login events, device signals, cookies, support messages, and payment references. It also explains how we use, retain, protect, and disclose those records, plus the steps available when you request access, correction, restriction, or deletion where applicable.

DANA and QRIS activity can create transaction references linked to your account, such as a status, date, or reconciliation detail. Our Privacy Policy explains how those records support payment checks and how to ask about the personal data connected with a transaction.

We may collect contact details, phone verification status, login timestamps, device signals, browser data, support correspondence, and wallet references. The exact categories depend on the action you take, and the Privacy Policy explains the purpose connected with each category.

Yes, you can contact us through the account support route to ask what personal data we hold or to correct an inaccurate record. Include your registered phone number and a clear request; we may verify your identity before making any change.

On a mobile browser, cookies may support session continuity, sign-in handling, and technical error checks. Our Privacy Policy explains necessary and optional uses, while your browser settings provide a way to restrict or remove cookies that are not required.

Retention depends on the record type and the reason it was created, such as account operation, security, payment reconciliation, or legal duties. The Privacy Policy describes these categories, and you can ask support which retention basis applies to your request.

You can submit a deletion request through the account support route where local law permits. We will explain whether the record can be removed or must remain for a stated operational, security, payment, or legal reason, then confirm the next step.