Reference

edc33 Privacy Policy for Your Account

Our Privacy Policy shows what we collect when you open an edc33 account, verify your phone, use DANA or QRIS, and enter the lobby from a mobile browser.

Clear data purposeWallet privacy contextPhone verification detailsIndonesia access wording
edc33 edc33 Privacy Policy for Your Account
PRIVACY CONTACT

Three Paths For Privacy Questions

A clear contact route matters when you want to ask about the Privacy Policy, correct account details, or understand a wallet record. We keep privacy help close to the account and cashier paths so you do not need to share sensitive credentials in an open message. Choose the route that matches your need, include the account phone number or transaction reference when appropriate, and remove passwords, wallet PINs and one-time codes before sending your request.

Team online

Account privacy request

Use the contact option shown after account access when you want to ask what personal details we hold, request a correction, or ask how a phone verification record relates to your edc33 account. We may ask for a safe account check before discussing private details.

Wallet record question

For a DANA, OVO, GoPay, QRIS, bank transfer or virtual account record, include the transaction reference and date through the account support path. We can explain the privacy use of that reference without asking you to send a wallet PIN or login password.

Access and device help

If a mobile browser or desktop session cannot reach the Privacy Policy or account contact path, tell us the device type and browser step that stopped. We use that detail to investigate access without requesting remote control, saved passwords or one-time verification codes.

DATA HANDLING

Six Privacy Controls Inside edc33

Our handling choices are designed around the account actions you actually take, from phone verification to wallet status checks.

Account details

We use your account details to create access, confirm the phone step, maintain sign-in security and respond to a request made through your account. We do not need your personal wallet PIN or password to check whether a DANA or QRIS reference has reached the cashier record.

Cookies and sessions

Cookies and session markers help keep the right account open while you move from login to Live Casino, appleslot or the cashier path. Your browser may retain a session choice, but clearing cookies can sign you out and require phone verification again.

Device security

We may record device type, browser details and sign-in signals to identify unusual access. If a new phone or desktop session looks different, we can ask for the account check again. These signals support access protection; they are not a request for remote device control.

Transaction records

A payment reference can show the rail used, such as OVO, GoPay, DANA, QRIS, bank transfer or virtual account. We use that record to match status and answer a support question, while avoiding collection of your wallet password or card-like secret.

Retention periods

We keep personal details and transaction references for the period needed to operate the account, resolve a stated request, prevent misuse and meet an applicable legal requirement. When that purpose ends, the record is removed or separated from direct account access where the rule permits.

Changes and contact

You can ask us to correct account details, explain a data use, or request removal through the account contact option. Tell us which field or record is involved, and we may confirm ownership before making a change. Do not include passwords, PINs or one-time codes.

Seven Questions About edc33 Privacy

These Privacy Policy answers cover the searches we expect before you open an account or connect a local wallet. Each response points to a practical account step, from phone verification and cookie settings to a request about DANA or QRIS records. If your situation involves access or eligibility, it depends on local law and the route available in your account.

The edc33 Privacy Policy covers account details, phone verification, sign-in sessions, cookies, device signals and payment references. It applies when you access Live Casino, appleslot, the cashier path or account support from a mobile or desktop browser where local law permits.

We use your phone number to create the account path, complete the stated verification step and help protect access when a new device signs in. We do not ask you to place a password, wallet PIN or one-time code inside a privacy request.

Yes. The Privacy Policy explains how we handle references connected with DANA, QRIS, OVO, GoPay, bank transfer and virtual account activity. We use those references to match a status or answer support, not to request your private wallet password.

You can use the account contact option to request a correction to details such as your phone number or account record. State the field that needs attention and complete a safe ownership check if requested. The available action depends on local law.

Cookies and session markers help keep your account connected while you move between login, the lobby and the cashier path. Clearing them may sign you out and trigger phone verification again. Your browser settings control whether non-essential session choices remain stored.

We retain account details, device signals and transaction references for the operational, security or legal period connected with their purpose. When that period ends, we remove or separate the record where the applicable rule permits. Ask through account support for a record-specific explanation.

Start with the contact option available after account access and describe whether your request concerns account data, a device session or a DANA, OVO, GoPay or QRIS reference. Include only the needed reference and never send your password, wallet PIN or one-time code.