Reference

oki toto Privacy Policy For Your Account

Our Privacy Policy explains how oki toto handles the details you provide when you open an account, sign in, use DANA or QRIS, and browse Baccarat or Aviator.

Clear data purposesWallet record visibilityAccount access controlsCookie choices
oki toto oki toto Privacy Policy For Your Account
CONTACT PATHS

Privacy Questions Near Your Account

A direct support path helps when a Privacy Policy question concerns your own account rather than a general request.

Account data request Use the account help path to ask what personal details are linked to your profile. We may ask you to complete the account verification step before disclosing records, so another person cannot obtain your data through a simple message.
Wallet record check For DANA, OVO, GoPay or QRIS records, send the transaction date and reference rather than a wallet password. We use those details to locate the payment event and explain what account data was connected with it.
Login privacy help If a sign-in alert or device record looks unfamiliar, contact us through the login support route. We can check the account event, ask for identity confirmation and explain the next access step without requesting your secret code.
DATA CONTROLS

Inside oki toto Privacy Handling

We handle Privacy Policy requests through practical account checks rather than broad promises. Account details, wallet references and device events are separated by purpose, while cookies help remember selected settings and understand…

Purpose-based records

We connect your phone or email detail to account creation and access, while payment references are used to trace a specific wallet or bank event. This separation helps us answer a Privacy Policy request without treating every record as one broad profile.

Cookie choices

Cookies can remember a sign-in preference and help us see whether a page loads correctly on your device. You can manage cookie settings through your browser, although changing them may affect account access steps or saved page preferences.

Device signals

We may record browser type, operating system, IP address and sign-in time to identify unusual access. These signals help us protect your account when a new phone or desktop reaches the lobby from a different connection.

Account protection

Before we discuss private account records, we may ask you to complete the clear phone verification step attached to your profile. Never send us your password, wallet PIN or one-time code in a support message.

Retention approach

We keep records for the period needed for the stated account, payment or security purpose, then remove or anonymise them when no valid reason remains. A legal, dispute or payment-tracing need may require a longer period.

Change request route

Ask us to access, correct or remove eligible details through the account support path. Include your profile contact and the specific record involved; we will confirm identity and explain the result or any reason a change cannot be made.

Privacy Policy Answers For Indonesian Accounts

These Privacy Policy answers focus on the questions you may have before opening an oki toto account or checking an existing record. They cover what we collect, why wallet references appear, how cookies and device signals work, and how to request a change. If your question concerns access or eligibility in Indonesia, the answer depends on local law and the details of your account.

It covers details you submit for an account, verification records, payment references, cookies, device signals and support messages. The Privacy Policy also explains why we use each category, how long records may remain and how you can request access or correction.

A DANA or QRIS reference lets us match a payment event with the correct account and investigate a receipt or status question. We do not need your wallet password for this check. The reference is used for tracing, support and account security.

Yes. Contact us through the account support route and describe the records you want, such as profile details, device events or payment references. We may complete phone verification first, then explain what can be supplied under the Privacy Policy and local law.

Send a correction request through account support with the affected profile field and the accurate replacement. We may ask you to confirm the account before changing it. For a DANA, OVO, GoPay or QRIS record, include its date and reference.

Yes. Cookies can remember selected settings and help us understand whether the login page works on your phone or desktop. Your browser controls cookie removal, but disabling certain cookies may require you to repeat account access steps.

The period depends on the purpose: account access, payment tracing, security review or a support case. We remove or anonymise records when no valid need remains, unless a dispute, legal duty or payment question requires continued retention.

Use the support route beside the account and cashier areas, and include your profile contact plus a clear description of the request. Do not send passwords, wallet PINs or one-time codes. Access and eligibility depend on local law.