Reference

Privacy Policy For Your tototix Account

Your account details, wallet records and device access stay at the centre of our Privacy Policy.

Clear data purposesWallet record contextPhone verification detailsCookie choices
tototix Privacy Policy For Your tototix Account
HELP WITH PRIVACY

A Clear Route For Data Requests

Questions about your Privacy Policy rights should start with the support path inside your account, especially when a wallet reference or login record needs checking. Tell us which account step concerns you, such as phone verification, a QRIS receipt or a device sign-in, and provide only the details needed to locate the request. We use the same route for access, correction and deletion questions where local law permits.

Team online

Account data request

Use the account support path to ask what personal details are linked to your tototix profile. We may ask for a phone verification step before discussing records, so account data is not disclosed to the wrong person.

Wallet record check

If a DANA, OVO, GoPay or QRIS reference appears incorrectly, include the payment rail and approximate transaction time. We compare the submitted reference with the account record before explaining what can be corrected.

Access concern

Report an unfamiliar sign-in with the device path you used, such as mobile browser or desktop browser. We can review the security signal, protect the account and explain which Privacy Policy records support the check.

DATA CONTROL PATH

What Our Privacy Process Covers

We keep the Privacy Policy practical by linking each data use to an account, security or support task.

Account creation

When you open an account, we use the details you submit to create your profile and support phone verification. We do not need unrelated personal details for the account path, and you can ask support which fields are held.

Phone verification

A phone check connects account access to the contact detail you supplied. If you cannot complete that step, support can explain the next security check without asking you to send a full wallet password or private code.

Device security

Login activity from a mobile browser, desktop browser or another device may create security records. These signals help us investigate an unfamiliar session and are handled as part of the account protection process.

Cookie handling

Cookies can keep a session active and help pages load in the right state. You can manage browser cookie settings, although removing necessary cookies may interrupt login, phone verification or the path into the lobby.

Retention timing

We retain account, wallet and support records for as long as needed for the stated purpose or applicable legal requirements. A retention question can be sent through support with the relevant account step named clearly.

Change requests

You may ask to access, correct or remove eligible personal data where local law permits. We first confirm account ownership, then explain the result, any required limitation and the records affected by the request.

Privacy Policy Answers For tototix

These Privacy Policy answers address the account questions you are most likely to have before using tototix from Indonesia. They cover payment references, cookies, phone checks, device records, retention and the route for requesting a change. If your situation is different, contact support through the account path and describe the specific record involved.

The Privacy Policy covers account details, phone verification, login and device signals, cookies, support requests and payment references. It explains why we use each category, how long records may remain and how you can ask about access or changes where local law permits.

Yes. When you use DANA or QRIS, we may retain the reference, status, amount-related transaction detail and account connection needed to check the request. OVO, GoPay, bank transfer and virtual account records follow the same account-linked purpose.

Phone verification helps connect account access to the contact detail you supplied and helps us investigate an unfamiliar sign-in. It can also be required before discussing account data. We do not ask you to share a private password or one-time security code.

Cookies can preserve a login session and help us understand whether pages work correctly on mobile or desktop. You can adjust cookie controls in your browser. Necessary cookies may still be required for account access, phone verification and secure page movement.

You can contact support through the account path and ask for access to eligible personal data. We may verify ownership before responding. The result depends on local law and may exclude records that must remain for security, dispute handling or legal reasons.

We keep payment and account records for the period needed to process status checks, resolve support questions, protect accounts or meet applicable legal needs. The exact period can differ by record type, and support can explain the basis for a retention question.

Send a correction request through the account support path and name the field or payment reference that appears wrong. We confirm account ownership, compare the request with our records and explain whether the change is available where local law permits.