Reference

elangtoto Privacy Policy for Indonesian Accounts

The elangtoto Privacy Policy explains what we collect when you open an account, verify your phone and use the lobby from Indonesia.

Account clarityWallet contextDevice controlsPrivacy requests
elangtoto elangtoto Privacy Policy for Indonesian Accounts
PRIVACY HELP

Get Help With a Privacy Request

A clear request helps us locate the correct account record without exposing details to the wrong person. Start from your logged-in account support path and include the email or phone detail attached to your account, the subject of your request and any relevant receipt reference. We may ask for an account step, such as phone verification, before discussing private data. If wallet status is part of your question, identify whether it concerns DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity.

Team online

Account support

Use the support path connected to your account when you want to ask for a copy, correction or explanation of personal data. We use the account contact and phone verification details to reduce the chance of sending private records to the wrong person.

Wallet privacy

For a data question involving DANA, OVO, GoPay or QRIS, include the wallet name and transaction reference rather than sharing a full password or security code. We can then separate payment status from the personal account details held in our records.

Receipt checks

If your request concerns a bank transfer or virtual account receipt, attach only the reference needed for matching. We use that reference to check the relevant record, while you should remove unnecessary card, password or authentication details before sending a message.

DATA PRACTICES

How We Handle Account Privacy

Privacy work follows the same account path you use to reach the lobby: we identify the account, check the request and limit the response to the data needed for that purpose.

Data collection

We collect information you submit during account creation and phone verification, plus operational records created when you log in or contact support. Payment labels such as QRIS or DANA help us understand a transaction status, while they do not reveal more personal detail than needed for that check.

Cookie use

Cookies and similar device storage can remember an active session, preserve security settings and help the account path load correctly on mobile. You can manage cookie controls in your browser, although restricting them may require another login or prevent some privacy settings from being saved.

Account security

Phone verification is an account access step, not a public display of your phone number. We use login records, device signals and request details to investigate unusual access. Do not send us a password, one-time code or wallet security credential in a support message.

Retention period

We retain personal and transaction records only for the period needed for account operation, security checks, dispute handling and legal duties. A bank transfer or virtual account reference may therefore remain after a session ends, even when the related lobby activity is no longer visible.

Correction requests

If your name, phone detail or contact address is inaccurate, tell us which field needs correction and why. We may request phone verification or another account check before changing it, so one person cannot alter another account through an unverified message.

Deletion questions

You can ask whether account data may be deleted or restricted through account support. We assess the request against active security, payment, dispute and legal needs; where a record must remain, we explain the reason and limit its use to that purpose.

Privacy Policy Questions From Indonesia

These Privacy Policy answers focus on the account details you are most likely to ask about before opening or continuing an elangtoto account. We keep the process practical: identify the account, describe the data request and use the support route connected to your verified contact detail. Wallet records and device records may follow different handling steps.

The elangtoto Privacy Policy covers details supplied during account creation and phone verification, together with login, device, support and transaction-status records. We use them for access, security, payment matching and legal needs. You can ask which records relate to your account through the logged-in support path.

Yes. The Privacy Policy covers wallet-related status and references connected with DANA, OVO, GoPay and QRIS. We use those details to match a payment event or investigate a receipt, not to request your wallet password or security code. Share only the reference needed for the question.

Open the account support path and request a copy of the personal data connected with your account. Include your verified phone or contact detail and describe the records you need. We may confirm ownership before responding, especially when the request includes login history or wallet-linked details.

You can ask us to correct an inaccurate name, phone detail or contact address under the Privacy Policy. State the field and the correct value through account support. We may use phone verification or another account check before making the change, protecting the record from an unverified request.

We keep device, login and payment records for the period needed for security, account operation, dispute handling and legal duties. A virtual account or bank transfer reference may remain after you leave the lobby. When a record is no longer needed, our retention process removes or restricts it.

You may send a deletion question through the support route linked to your account. We assess it against security checks, payment records, disputes and legal duties. If a record must remain, we limit its use and explain the reason. Access depends on local law and the applicable request.

Contact account support promptly and state the date, device or login detail that looks unfamiliar. Do not include your password or one-time code. We can check the relevant security record and may ask you to complete phone verification before discussing private account activity.