Reference

edc99 Privacy Policy For Your Account

edc99 Privacy Policy explains what we collect when you open an account, sign in, use the lobby, or check DANA and QRIS status.

Clear data purposesWallet record handlingCookie choicesAccount request path
Explore The Lobby Read FAQ
edc99 edc99 Privacy Policy For Your Account
REQUEST SUPPORT

Where To Ask About Your Privacy Policy

A clear request route helps when you want to check a record, correct an account detail, or ask how a wallet reference was used.

Account request Use the signed-in support path for a copy, correction, or deletion request under our Privacy Policy. Include the phone or email linked to your account so we can identify the correct record without requesting your password.
Wallet question If a DANA, OVO, GoPay, QRIS, bank transfer, or virtual account reference looks unfamiliar, send the date, amount reference, and account identifier through the support route. Do not send a wallet PIN or full security code.
Access concern When a phone or desktop session shows an unfamiliar sign-in, tell us through the account access contact route. We can check session details, help secure the account, and explain which Privacy Policy record supported the check.
DATA HANDLING

What We Do With Your Account Data

We keep this Privacy Policy practical by tying each data use to an account task: opening access, confirming phone verification, matching wallet status, protecting a session, or responding to you.

Account creation

When you open an account, we use the submitted contact details to create your profile and send the phone verification step required before access. We do not need your password in a privacy request, so keep that secret outside every support message.

Wallet matching

Payment records show which account action relates to DANA, OVO, GoPay, QRIS, bank transfer, or a virtual account. We use the reference to check status and resolve a receipt question, rather than treating the wallet name as broad consent.

Device security

Our account security checks may record browser type, device signals, sign-in time, and session activity. These details help us spot an unfamiliar login on mobile or desktop and decide what account confirmation is needed before access continues.

Cookies

Required cookies support sign-in, session continuity, and saved privacy choices. Optional measurement cookies may help us see which policy page path brought you to an account question. Browser controls can restrict cookies, though necessary settings may stop parts of account access.

Retention

We keep account, support, security, and payment-reference records only for the operational, security, or legal period connected with their purpose. When that period ends, we delete or anonymise the record unless another valid need requires continued storage.

Change requests

You can ask us to access, correct, or remove eligible personal details through the signed-in support route. We may confirm account ownership before making a change, and where local law permits, we will explain any record that cannot yet be removed.

Privacy Policy Answers For edc99

These Privacy Policy answers address the account and wallet questions you are most likely to have before opening access. They cover what we collect, why we use it, how device records work, and how to contact us. If your question involves a particular DANA, OVO, GoPay, QRIS, bank transfer, or virtual account reference, include that reference through the protected support path rather than placing sensitive credentials in a message.

It covers details collected during account creation, phone verification, sign-in, wallet status checks, support contact, and use of the mobile or desktop lobby. It also explains cookies, device signals, retention, security checks, and the route for requesting access, correction, or removal.

We may collect contact details needed to create your account, phone verification results, sign-in and session records, device or browser signals, support messages, and payment references. We use each category for a stated account, security, wallet-status, support, or legal purpose.

Yes. The Privacy Policy covers references connected with DANA, OVO, GoPay, QRIS, bank transfer, and virtual account activity. We use those references to match an account action, check a receipt or status question, and investigate unusual activity without asking for your wallet PIN.

Required cookies help maintain sign-in, session continuity, and your selected privacy settings. Optional cookies may help us understand policy-page navigation. You can use browser controls to restrict them, but disabling required cookies may interrupt phone verification, account access, or the move from login to the lobby.

You can contact us through the signed-in support path and request access to, or correction of, eligible account details. Include the phone or email linked to your account. We may verify ownership first, and where local law permits, we will explain the result and any limits.

We retain account, wallet-reference, support, and security records for the period needed for their operational, security, or legal purpose. After that need ends, we delete or anonymise the information unless another valid requirement calls for continued retention.

Use the account access contact route shown on the sign-in screen and describe the unfamiliar device, date, or session. Do not send your password, wallet PIN, or full security code. We can check the relevant security record and explain the next account-protection step.

Related Pages

edc99 Indonesia Live Blackjack Gold Account information About Us La Liga Over Under