Reference

facai toto Privacy Policy Explained

facai toto Privacy Policy shows how we collect, use and protect the details connected with your account, including phone verification and wallet status for DANA, OVO, GoPay and…

Clear data purposesCookie choicesAccount request pathIndonesia wallet context
facai toto facai toto Privacy Policy Explained
REQUEST HELP

Reach Us About Your Privacy Policy

A clear support path helps you ask what data we hold, why it is used, or how a correction request works.

Account privacy request Use the support route inside your account to ask for access, correction or deletion details. Include a clear request so we can match it with the correct phone verification record.
Wallet record question If your question concerns DANA, OVO, GoPay or QRIS data, mention the relevant transaction reference. We can then separate payment-status records from general account details.
Login data concern Tell us when a device, browser or login record looks unfamiliar. Our support path can check the account trail and explain the security steps linked with your Privacy Policy request.
DATA HANDLING

Browse How We Handle Your Details

We explain each handling step in plain terms because your account choices should not depend on guesswork.

Account details

We may hold your phone number, account credentials and verification status to let you sign in and protect the account. We use these details for the stated account purpose rather than unrelated messages.

Device signals

Your browser and device can send session data when you move from login to the lobby. We use these signals to recognise active access and investigate unusual sign-in behaviour.

Cookies

Cookies can keep selected settings and login sessions working on mobile or desktop. Your browser controls can restrict them, although some account functions may then need to be repeated.

Payment records

DANA, OVO, GoPay, QRIS, bank transfer and virtual account references help us identify a transaction status. We retain only the records needed for account support, security and stated legal duties.

Retention period

We keep personal data only for as long as the account purpose, security need or applicable legal duty requires. The period can differ by record type, and the policy explains the relevant basis.

Change requests

You can ask what we hold, request a correction, or ask about deletion through the account support path. We may request account details to confirm that the request is yours.

Find Privacy Policy Answers Quickly

These Privacy Policy questions cover the account steps you are most likely to check before opening access. Each answer points back to a practical action, from checking cookies on your phone to requesting a copy of personal data. If your situation is different, send the details through the support path shown in your account.

The facai toto Privacy Policy covers account details, phone verification, device signals, cookies, payment-status records and support requests. It also explains retention, security handling and the ways you can request changes.

We use your phone number to create and protect account access, confirm your identity during the account step and connect support requests with the correct record. We do not use it for an unrelated purpose.

Yes. The Privacy Policy explains how transaction references for DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity may be used to check payment status and answer account questions.

Open the support area linked to your account and request access or correction. Include your account reference and describe the record involved; we may confirm your identity before responding.

Cookies can keep your session and selected settings available as you move from login to the lobby on a phone. Browser controls can restrict cookies, so some steps may need repeating.

The retention period depends on the record, its account purpose, security needs and applicable legal duties. Our Privacy Policy explains why a category is retained and when removal may be requested.

Yes. Use the account support path and state when the device or login looked unfamiliar. We can check the relevant access trail and explain the security handling described in the Privacy Policy.