Reference

Check the eviltoto Privacy Policy

Your account details, wallet records and device access are handled under the eviltoto Privacy Policy, so you can see what we collect before opening an account.

Account dataWallet recordsDevice controlsPolicy requests
eviltoto Check the eviltoto Privacy Policy
POLICY HELP PATH

Find policy help beside wallet status

A clear contact route matters when a Privacy Policy question is connected to a pending wallet record or an account login. We ask you to include your account identifier, the affected payment reference and the policy point you want explained. Do not send a password or full payment credentials. Our support path can help with access requests, correction questions and receipt matching for DANA, OVO, GoPay, QRIS or bank transfer records.

Team online

Account access

Use the account help path when you need to ask how phone verification, login events or device details are used under our Privacy Policy. Include the email or phone connected to your account so we can locate the correct record without requesting your password.

Wallet records

For a DANA, OVO, GoPay, QRIS or bank transfer question, provide the transaction reference and date through the payment support route. We use those details to check the record while limiting the personal data shared in your message.

Data requests

Ask for a copy, correction or eligible removal of your personal data through the policy contact path. We may request account verification before acting, because the Privacy Policy requires us to protect your records from an unauthorised request.

HANDLING YOUR DATA

Browse how account data stays protected

We keep the Privacy Policy practical by linking each data category to an account task: access, payment matching, fraud checks, support or legal retention.

Account security

Phone verification is tied to account access, and we may compare login or device signals when a request looks unusual. This helps us confirm that a Privacy Policy request comes from the account holder rather than someone using copied payment details.

Payment matching

A payment reference can be stored with your account record so we can connect a QRIS receipt, DANA status or bank transfer to the correct transaction. We do not need your wallet password to investigate that reference.

Cookies

Cookies can keep a session active, remember selected settings and show us whether policy pages load correctly on mobile or desktop. You can restrict or delete cookies in your browser, although some account functions may then require another login.

Retention

We retain account, payment and support records only for the period needed for account operation, security checks, dispute handling or legal duties. The Privacy Policy explains the relevant purpose, so you can ask why a particular record remains stored.

Correction requests

If your phone number, email or account detail is inaccurate, contact us with the changed value and a way to verify ownership. We review the request against the account record before applying a correction or explaining why more detail is needed.

Contact choices

For a Privacy Policy request, use the support route linked to your account rather than posting personal details in a public message. Tell us whether you need access, correction, deletion or an explanation, and we will direct the request to the relevant team.

Ask what the Privacy Policy covers

These Privacy Policy answers address the account and payment questions you are most likely to have before opening an eviltoto account. They explain the records connected to login, phone verification, wallet references, cookies and support requests. If your situation is different, use the policy contact path with only the details needed to identify your account.

It covers account details, phone verification, login activity, device signals, cookies, payment references and support messages. It also explains why we use each category, how long records may remain, and how you can request access, correction or eligible removal where local law permits.

Yes. The Privacy Policy covers payment references connected with DANA, OVO, GoPay and QRIS, as well as bank transfer and virtual account records. These details help us match receipts, answer status questions and protect account access without asking for your wallet password.

Phone verification helps connect account access to the correct account holder and supports recovery or security checks. We may retain the verification result and related access event under the Privacy Policy, while you should never send your password through a support message.

You can request access to eligible account data through the policy contact route. Include the account phone or email and state that you want a data copy. We may verify ownership first, then explain which records can be supplied under applicable local requirements.

Send a correction request through account support and identify the detail that is wrong, such as a phone number or email. We compare the request with your account and may ask for verification before changing the record, protecting it from unauthorised edits.

Cookies can support your login session, remember selected settings and help us check whether policy pages work on your phone or desktop. Browser controls let you delete or restrict them. Limiting cookies may mean you need to authenticate again during account access.

You may request removal of eligible personal data through the Privacy Policy contact route. Some account, payment or support records may need to remain for security, dispute handling or legal duties. We will explain the result and any reason a record must be retained.