Reference

Privacy Policy for eviltoto Accounts

Our Privacy Policy explains how eviltoto handles the details connected with your account, from phone verification to wallet records for DANA, OVO, GoPay and QRIS.

Account dataWallet recordsCookie choicesContact requests
eviltoto Privacy Policy for eviltoto Accounts
HELP WITH PRIVACY

Get Privacy Help Beside Your Cashier Path

A clear contact route helps when a Privacy Policy question is tied to an account or wallet record.

Account support link Open the support link inside your account and describe the Privacy Policy request in…
Cashier help path For a privacy question about DANA, OVO, GoPay, QRIS, bank transfer, or virtual account…
Device access check If a request follows an unfamiliar phone or browser sign-in, tell us which device…
DATA HANDLING

How We Apply This Privacy Policy

We apply the Privacy Policy through practical account steps rather than treating it as a page you read once.

Account details

When you open an account, we may collect the contact details and phone verification result needed to create and protect your profile. Your account path can also show sign-in events and preference settings. We use these details for the stated account purpose, not as a reason to request unrelated personal records.

Wallet references

A DANA, OVO, GoPay, or QRIS action creates a payment reference that helps match status and receipt details. Bank transfer and virtual account checks use the same practical approach. We need enough data to reconcile the request, while your wallet PIN and banking password remain outside our support request.

Cookies on your device

Cookies can keep a session connected, remember a selected setting, or help us understand whether a page is working correctly. You can manage cookie behaviour through your browser controls. Turning some cookies off may require another sign-in or change how account pages remember your choices.

Security signals

We may use device type, browser details, sign-in time, and account activity as security signals. These checks help us respond when a phone or desktop session looks unfamiliar. If you switch from mobile to desktop, a new verification step can protect the account before private records are shown.

Retention choices

We keep records only for the purposes and periods set out in the Privacy Policy, including account operation, payment matching, security, dispute handling, or legal duties. When a retention period ends, records are deleted or separated from direct account details where that process applies.

Requests and corrections

You can ask us to access, correct, or delete eligible personal data through the account support route. Include the request type and the account detail needed for verification. We may ask for an additional account step before acting, and some records may remain where a legal or security duty requires them.

Privacy Policy Answers For Your Account

These Privacy Policy answers address the searches we hear most often before an Indonesian account is opened. They explain the records connected with sign-in, local wallet activity, cookies, corrections, and contact requests without turning the policy into a general lobby description. If your case involves a specific DANA, QRIS, or device reference, use the signed-in support path and give only the details needed to locate it. Account access depends on local law and applies where local law permits.

The eviltoto Privacy Policy covers account details, phone verification, device and sign-in records, support messages, cookies, and payment references. It explains why we use each category, when records may be shared, how long they may remain, and how you can request access or correction.

The policy may cover the contact details you submit, your phone verification result, sign-in events, device or browser details, and account settings. We collect these details for account access, security, support, and stated service tasks. We do not need your wallet PIN or banking password.

Yes. A DANA or QRIS action can create a reference, amount, status, and time record needed to match a cashier request. OVO, GoPay, bank transfer, and virtual account routes can create similar records. These references help us check status without requesting your private wallet credentials.

Open the account support link and state whether you want access, correction, or deletion of eligible data. Include the registered phone number or another matching account detail, but not a password or one-time code. We may complete an identity check before changing or releasing private account records.

Cookies can keep your session active, remember a page preference, and help us identify technical faults. Your browser settings let you remove or restrict them. If you block required cookies, the account page may ask you to sign in again or may not retain selected settings.

Retention depends on the purpose described in the Privacy Policy, such as account operation, payment matching, security, dispute handling, or a legal duty. When the relevant period ends, we delete the record or separate it from direct account details where that method is suitable.

Yes. Use the signed-in support route and identify the unfamiliar phone or browser, approximate time, and related account detail. Do not send your password, PIN, or one-time code. We can focus first on protecting account access, then handle any Privacy Policy request connected with the event.