Reference

eda toto Privacy Policy for Your Account

Our Privacy Policy explains what we collect when you open an eda toto account, use DANA or QRIS, and move between the lobby and cashier.

Account dataWallet recordsDevice choicesCookie controls
eda toto eda toto Privacy Policy for Your Account
HELP WITH RECORDS

Reach Us About Your Privacy Choices

A clear support path helps when a privacy question appears beside a login or wallet record. Start from the support link shown inside your account and include the email or phone detail connected to the record. If you are in Surabaya or elsewhere in Indonesia, we use the same account-based route so the request reaches the right case.

Team online

Account privacy request

Use the support route inside your account to ask what personal data we hold, why it is used, or which account detail needs correction. Include a clear description so we can locate the right record.

Wallet record check

For a DANA, OVO, GoPay, QRIS, bank transfer, or virtual account query, share the payment reference and date through support. We use those details to check status without asking for your wallet password.

Access concern

If a privacy request is blocked by a login issue, tell us which device path you used and what appeared on screen. We may ask for account details to confirm that the request is yours.

DATA CONTROL PATH

What You Can Ask Us To Change

We keep this policy practical by connecting each privacy choice to an account action or support request.

Collection purpose

We collect account and verification details to create access, protect the sign-in path, and respond to account questions. Payment references from DANA, OVO, GoPay, and QRIS help us identify a transaction without storing your wallet password.

Cookie settings

Cookies can support a signed-in session, remember a device preference, or help us understand a page error. You can adjust cookie controls in your browser, although some account functions may then need another sign-in.

Account security

We use sign-in checks, account details, and device signals to identify unusual access. Keep your password private and contact us through the account support route if a login appears that you do not recognise.

Record retention

We retain account, support, and payment-reference records only for the period needed for the stated purpose, account administration, dispute handling, or a legal requirement that applies to the request.

Request verification

Before changing or disclosing personal data, we may confirm your identity through the account details connected to the request. This step prevents another person from changing your profile or viewing your records.

Correction or deletion

You can ask us to correct inaccurate details or request deletion where the applicable rules allow it. We will explain if a record must remain for account, payment, security, or legal reasons.

Answers About eda toto Privacy Policy

These answers address the searches we hear most often about the eda toto Privacy Policy. They explain the account step, wallet references, device data, cookies, and request route in plain English. If your situation is different, use the support path above and identify the specific record or device involved.

It covers account details, verification information, login events, device signals, cookies, support messages, and payment references connected with DANA, OVO, GoPay, QRIS, bank transfer, or a virtual account.

We need account details to create access, confirm that a privacy request belongs to you, protect sign-in activity, answer support questions, and connect a payment reference with the correct account.

No. We record transaction references and status details needed for account and payment checks, but your DANA, OVO, GoPay, or QRIS wallet credentials remain with the relevant payment service.

Use the support link inside your account and ask for a copy of the personal data connected with your profile. Include the account contact detail so we can verify and locate the request.

Yes, you can request correction or deletion through the account support route. We may keep records needed for security, payment reconciliation, dispute handling, account administration, or a legal requirement.

Cookies may keep a mobile session active, remember a device choice, or help identify a page error. Browser controls let you adjust them, but changing settings may require another login.

Access depends on local law. Where local law permits, you can read this Privacy Policy and send an account-based request from your supported device, including a phone used in Indonesia.