Reference

Privacy Policy For Your eli toto Account

eli toto Privacy Policy explains what we collect when you open an account, sign in from a phone or desktop, and use the lobby from Indonesia.

Account dataWallet recordsCookie choicesData requests
eli toto Privacy Policy For Your eli toto Account
HELP WITH YOUR REQUEST

Get Privacy Policy Help Through Account Support

A clear support path helps when you want to ask what data we hold or correct an account detail. Contact our account support through the available help channel linked from the signed-in area, and include the email or phone connected with your account. If your question concerns a DANA, OVO, GoPay or QRIS record, attach the payment reference rather than sending a wallet password. We use those details to locate the right record and reduce back-and-forth. Requests about access still depend on local law.

Team online

Data request

Ask our account support what personal data is connected with your eli toto account. Include your registered contact detail so we can identify the request without asking you to send a password or wallet PIN.

Correction path

If your phone, email or account detail is inaccurate, tell us which field needs attention. We may ask for an account step or verification detail before changing it, helping keep another person from altering your record.

Payment query

For a privacy question tied to DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity, share the reference and date. We can then separate your payment record from unrelated account data.

WHAT WE KEEP CLEAR

Your Privacy Policy Choices Across Devices

Privacy Policy choices should remain understandable whether you sign in on Android, iPhone or desktop.

Collected details

We may handle your name or contact detail, account credentials in protected form, verification status, sign-in events and support messages. Payment references from DANA and QRIS help us match a transaction without treating a wallet PIN as an account field.

Cookie function

Necessary cookies can keep a signed-in step working and preserve a selected setting. Your browser may block or clear them, although doing so can require you to repeat an account step before the lobby opens.

Device signals

A phone or desktop session can provide browser, device and network signals used for account protection. We compare these signals with sign-in activity to spot unusual access, rather than using them to read content from your device.

Account protection

Before changing a contact detail or discussing a wallet-linked record, we may ask you to complete phone verification or another account check. This protects your data when a shared phone or public connection is involved.

Retention timing

We keep account, payment and support records for the period needed for their stated purpose, security checks or a dispute. When a record no longer needs retention, our handling follows the applicable deletion or archival process.

Request channel

Use the account support path to ask for access, correction, deletion consideration or an explanation of processing. State the request plainly and provide the contact detail linked with your account so we can route it correctly.

Privacy Policy Answers For eli toto Accounts

These Privacy Policy answers address the questions we expect before you open or continue an eli toto account. They cover the data connected with sign-in, local wallet records, cookies, device use and requests for changes. If your situation is not listed, send the account support team your registered contact detail and a short description. We will handle the request according to the policy and where local law permits.

It covers account details, sign-in activity, phone verification, device signals, cookies, support messages and payment references. It explains why we use those records, how long we retain them, how we protect account access and how you can ask about correction or deletion.

We record payment references, status and timing so a DANA or QRIS request can be matched to the correct account. We may use the same approach for OVO, GoPay, bank transfer and virtual account records, without requesting your wallet PIN.

Yes. Send an access request through the account support path and identify your account with its registered phone or email. We may ask for phone verification before discussing personal records, especially when the request concerns wallet activity or a shared device.

Tell support which account field is wrong, such as your phone or email, and describe the correction clearly. We may require an account check before changing it. This step helps prevent an unknown person from taking over your sign-in route.

Yes. We may handle browser, device and session signals from your phone or desktop to keep sign-in safer and identify unusual access. These signals help protect the account path; they do not give us permission to read unrelated content on your device.

Contact account support and ask which cookie purpose you want explained. Necessary cookies can support sign-in and settings, while your browser can clear or block some cookies. After clearing them, you may need to repeat a sign-in step.

We retain each record for the account, payment, security or dispute purpose that requires it, subject to applicable requirements. You can ask us to explain retention or consider a deletion request. Any decision depends on local law and the record's purpose.