Reference

edan77 Privacy Policy For Your Account

The edan77 Privacy Policy explains what we collect when you create an account, sign in from a phone or desktop, and use DANA, OVO, GoPay or QRIS.

Account detailsWallet recordsDevice accessPolicy requests
Explore Our Lobby Read FAQ
edan77 edan77 Privacy Policy For Your Account
PRIVACY HELP PATH

Where To Ask About Privacy Policy

A clear contact path helps when you want to understand a data entry, correct an account detail or ask why a wallet record appears in your history. We keep privacy questions close to the account and cashier areas so you do not need to explain the same issue across unrelated pages. Include your registered contact detail, the approximate date and the specific request. We use that context to locate the relevant record without asking you to send a password or full payment credential.

Team online

Account message

Use the support message path from your signed-in account for a Privacy Policy request. Tell us whether you need access, correction or deletion, and include the account contact detail so we can match the request safely.

Wallet question

If your question concerns DANA, OVO, GoPay, QRIS, bank transfer or a virtual account, mention the payment rail and transaction reference only. We can then separate wallet status records from unrelated account activity.

Access check

When you cannot sign in, contact support through the available account access route and explain that the request concerns privacy. We may ask for an account step that confirms ownership before discussing personal data.

DATA HANDLING DETAILS

What We Do With Account Information

Our approach is practical: collect what an account step needs, use it for a stated service reason and limit access to people handling account, payment or security requests.

Account creation

When you open an account, we use the contact details and verification information you provide to create the account path. A clear phone verification step can be required before account access, helping us distinguish an owner from an unknown sign-in.

Device signals

A mobile browser or desktop session may provide technical details such as browser type, language and connection data. We use these signals to maintain a session, detect unusual access and understand why a page such as the lobby or account area did not load.

Cookies

Cookies and similar browser storage can remember a sign-in state, preserve basic page settings and measure whether a requested page works. You can manage browser storage through your device settings, although removing it may require you to sign in again.

Wallet records

A DANA, OVO, GoPay or QRIS action can create a reference, amount, status and time record. Bank transfer and virtual account records may be matched in the same way, allowing us to answer a cashier-status question without storing a wallet password.

Account security

We use account details, verification steps and device signals to reduce unauthorised access. Never send us your password or a complete payment credential in a support message. If a sign-in looks unfamiliar, tell us the time and device used.

Retention requests

We keep personal records only as long as needed for account service, security, dispute handling and legal duties, subject to local requirements. You can request access, correction or deletion by contacting support; we may first confirm that you control the account.

Privacy Policy Questions For edan77

These Privacy Policy answers focus on the questions you may have before opening an account or contacting us about an existing one. We explain the account step, device behaviour, wallet references and request path in direct terms. If your situation depends on a local requirement, our support team can identify the relevant process without asking you to disclose a password.

It covers account details, phone verification, sign-in activity, device signals, cookies, support messages and payment references connected with DANA, OVO, GoPay, QRIS, bank transfer or a virtual account. It also explains your routes to ask for access, correction or deletion, subject to local law.

We collect the contact and verification details needed for the account path, plus technical details from the browser or device used to sign in. If you use a wallet or bank rail, we may receive a transaction reference, status and time rather than your wallet password.

The Privacy Policy treats payment references as account service records. We may connect a DANA, OVO, GoPay or QRIS reference with your account to check status, answer a receipt question or investigate a mismatch. Do not send a full wallet credential in a message.

Yes. Send a request through the signed-in support path and state that you want access to your personal data. Include your registered contact detail and the account area concerned. We may ask for phone verification or another ownership check before releasing account-linked details.

Contact support with the field you believe is wrong and the replacement detail. For example, identify an outdated phone number or an incorrect account contact. We may request an account verification step, then assess the correction against service and legal record requirements.

Retention depends on why the record exists. We keep account, device and payment references for account service, security checks, dispute handling and legal duties for the period required by applicable rules. Ask support about a specific record and we will explain the available request path.

You can submit a deletion request through support, explaining which account data you want removed. We assess it under local requirements because some records may need to remain for security, disputes or legal duties. Access and eligibility depends on local law, and ownership confirmation may apply.

Related Pages

edan77 Indonesia FAQ Champions Night Bet About Us Live Baccarat Elite