Reference

01toto Privacy Policy In Plain English

The 01toto Privacy Policy explains what we collect when you open an account, sign in from a phone or desktop, and use DANA, OVO, GoPay or QRIS.

Account dataPayment recordsCookie choicesContact path
01toto 01toto Privacy Policy In Plain English
CONTACT THE TEAM

Where To Ask About Privacy Policy

A clear contact path helps you act on the Privacy Policy without guessing which team to reach.

Account help Ask about the Privacy Policy through the account-help route when you need to correct your name, phone detail or email record. We may request a phone verification step before discussing account data, so your request is connected to the right account rather than a copied message.
Wallet status For DANA, OVO, GoPay or QRIS questions, share the payment reference and time shown in your account history. We use that reference to check the status without asking for your wallet PIN, login password or one-time security code.
Privacy request Use the privacy contact path to ask how your information is used, request a correction or ask about retention. Tell us which account detail concerns you; we will explain any identity check and the action available where local law permits.
DATA HANDLING

Six Practical Privacy Controls We Use

Privacy Policy decisions affect the account journey from the first phone check to a later wallet-status question.

Account collection

When you open an account, we collect the contact and verification details needed to create that account and confirm access. We do not need your wallet password to match DANA, OVO, GoPay or QRIS activity, and support should never ask you to disclose it.

Payment references

A payment record can include a rail name, reference, amount status and time needed to reconcile the account ledger. These details help us investigate a QRIS scan, bank transfer or virtual account query while keeping wallet credentials outside the support conversation.

Cookie controls

Cookies and similar device signals can remember sign-in preferences, help maintain a session and show whether a page loads correctly. Your browser settings let you remove or restrict them, although some account pages may then require another sign-in.

Device security

We may record device type, browser details, approximate access signals and sign-in events to identify unusual account activity. If a phone is lost or a session looks unfamiliar, change your account password and contact account help from a safer device.

Retention periods

We keep account, support and payment records only for the period needed for account operation, dispute checking, security work or a legal requirement that applies where local law permits. A retention question can be sent through the privacy contact path.

Change requests

You can ask us to correct inaccurate contact details, explain a data use or clarify a stored payment reference. Include the account email or phone detail, avoid passwords and codes, and complete any identity check needed before we make a change.

Privacy Policy Questions From Indonesia

These Privacy Policy answers address the account, device and payment questions we expect before you open an account. We keep the wording practical so you can understand what happens when you sign in on mobile, verify a phone number, connect a local wallet or ask for a record change. If your situation is not covered, send the details through the privacy contact path without including a password or security code.

The 01toto Privacy Policy covers account details, phone verification, device and sign-in records, cookie signals, support messages and payment references. It explains why we use those records, how we protect them, how long we may retain them and how you can ask about a correction.

Phone verification helps connect account access to the person who opened the account and reduces confusion when a sign-in or privacy request arrives. We may ask for that check before discussing stored details, but you should never send us your wallet PIN or one-time code.

Yes. The Privacy Policy covers payment references connected with DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity. We use a rail name, reference and status to trace an account entry; we do not need your wallet password to check that record.

We may collect device type, browser details, sign-in events and approximate access signals when you use the account page on a phone or desktop. These details help identify unusual access and diagnose a session problem. Your device data does not replace your account password.

You can request a correction to the contact details linked with your account through the privacy contact path. Include the account email or phone detail and explain what is wrong. We may complete an identity check before changing the record where local law permits.

We retain account, support and payment records for the period needed for account operation, security checks, dispute handling or a legal requirement that applies where local law permits. Contact us if you need the retention basis for a particular record or account event.

Yes, access and eligibility depend on local law. Location or account checks may apply where local law permits, and the Privacy Policy explains how related access signals are handled. Check the policy before opening an account and contact support if a location question blocks your request.