Reference

sanji toto Privacy Policy Explained Clearly

Our sanji toto Privacy Policy shows what we collect, why we use it and how you can ask for changes before opening an account.

Account dataCookie choicesWallet referencesPrivacy requests
sanji toto sanji toto Privacy Policy Explained Clearly
REQUEST A HAND

Privacy Help Beside Your Account Route

A clear support path helps when you want to ask about a data record, cookie setting or wallet reference. Start from your signed-in account area and send the request through our support contact route, using the same phone or email linked to your account. We may ask for a verification step before discussing account data. This keeps a request connected to the right record without asking you to send a wallet password or full payment credential.

Team online

Account request

Use the support route inside your account to ask what personal data is held, why it is used or which record relates to a DANA, OVO, GoPay or QRIS transaction. We may confirm your phone number before replying.

Wallet query

If a payment reference looks unfamiliar, include the date, rail name and visible reference only. For bank transfer or virtual account questions, we can check the matching account record without requesting your banking password or complete card details.

Access concern

When login access stalls, contact support from the account path and describe the device and browser used. We can review the security event, explain the next verification step and avoid exposing private details in an open message.

DATA PRACTICE

Six Practical Privacy Controls We Apply

Our privacy process follows the way an Indonesian account actually works: you enter account details, complete phone verification, choose a device path and then view wallet status.

Account collection

We collect details needed for account access, including the contact information you enter and the phone verification result. Optional preferences can help remember your lobby choices, but they are separate from the core account record used for login.

Device signals

A mobile browser may send device and session signals so we can keep your login connected while you move from the account page to the lobby. Desktop and mobile paths can create different session records for security checks.

Cookie control

Cookies can retain a session, language setting or security state. You can clear them in your browser, although doing so may sign you out and require the phone verification step again before account access.

Payment matching

DANA, OVO, GoPay, QRIS, bank transfer and virtual account references help us match a cashier event to your account. We use the visible transaction details required for checking and do not ask for wallet passwords.

Retention checks

We keep account, security and payment records for the period needed to provide access, investigate a query or meet an applicable legal duty. After that period, records are removed or changed so they no longer identify you where practical.

Change requests

You can request a correction, ask about stored data or question a processing purpose through account support. Use your linked contact route and provide enough detail for us to locate the record without sending a password.

Privacy Policy Answers For Your Account

These Privacy Policy answers address the searches we hear before account access: what sanji toto records, how wallet references are handled, how cookies affect a mobile login and where to send a request. Read them with the full policy above, especially if your access or eligibility depends on local law.

It covers account details, phone verification, device and session signals, cookies, support messages and payment references. It explains why we use each category, who may need access for operations and how you can request correction or clarification through your account support route.

No. The Privacy Policy separates wallet credentials from transaction references. We may receive a visible status, date, amount or reference needed to match DANA or OVO activity with your account, but you should never send a wallet password through support.

A QRIS payment can create a reference, status and timing record linked to the account that started the request. We use those details to check a pending cashier event. If the reference is wrong, contact support with the visible code only.

Yes. Send a request through the signed-in account support route using your linked phone or email. Tell us whether you want a data copy, correction or purpose clarification. We may complete an identity check before releasing or changing account records.

Cookies can keep your mobile session active and retain a security setting while you move from login to the lobby. Clearing browser cookies can end that session, so you may need to sign in again and complete phone verification.

We keep them only for the operational, dispute-handling or legal period that applies to the record. Retention can differ between a wallet reference, support message and security event. When the period ends, we remove or anonymise the record where practical.

Yes. Ask through account support and name the record or processing purpose you want clarified. We can explain sharing needed for account security, payment matching or service operations. Access and eligibility still depend on local law and applicable requirements.