Reference

Privacy Policy For Your zeus200 Account

Our Privacy Policy explains what account details we collect, why we use them and how you can request changes before opening the lobby.

Clear data purposesWallet record handlingAccount access rights
zeus200 Privacy Policy For Your zeus200 Account
CONTACT ROUTES

Privacy Help Beside Your Account Path

A clear contact route helps when you want to ask about a Privacy Policy request, correct an account detail or understand a wallet record. Start from the support link connected to your account and include the phone or account reference you use with zeus200. We will ask for enough detail to locate the request without asking you to send a password or full wallet credentials. If your question concerns a Live Baccarat session, a QRIS receipt or a phone change, name that context so we can direct it correctly.

Team online

Account privacy request

Use the account support path to ask what personal details are held, why they are needed or how a correction request should be submitted. We may ask you to confirm your phone before discussing account-specific records.

Wallet record question

For DANA, OVO, GoPay or QRIS records, send the transaction reference shown in your account rather than your wallet password. We use that reference to check the payment entry and reply about its privacy handling.

Access and deletion query

If you want a copy, correction or removal request, contact support through the signed-in account path where possible. We may retain selected records when a legal, security or reconciliation need still applies.

DATA PRACTICES

What We Do With Your Account Details

We keep this policy practical by linking each data use to an account action you can recognise, such as phone verification, a sign-in attempt, a payment status check or a support request.

Data collection

We collect details you enter during account creation and phone verification, plus technical records created during sign-in. These may include a device type, session time and security events needed to protect the account path.

Cookie choices

Cookies can keep your signed-in session and remember functional settings between the lobby and account pages. You can adjust browser controls, although disabling required cookies may interrupt sign-in or make a session expire sooner.

Account security

Phone verification and unusual-login checks help us separate your account activity from an unfamiliar device. Never send a password in a support message; we use account references and verification steps instead.

Payment matching

A DANA, OVO, GoPay or QRIS reference lets us connect a wallet event to the correct account record. Bank transfer and virtual account details may be checked for reconciliation without requiring your banking password.

Retention choices

We retain records only for the period needed for account operation, security checks, dispute handling or legal duties. A deletion request can be assessed against those needs, and we will explain any record that must remain.

Request changes

Ask us to correct an inaccurate name, phone detail or account reference through the signed-in support path. Include the specific field and your preferred contact route so we can verify the request safely.

Privacy Policy Answers For Indonesia

These Privacy Policy answers address the account questions we expect before you open zeus200 from Indonesia. They explain access, wallet records, cookies, phone checks and requests for copies or corrections in plain terms. When a question involves eligibility, our access wording is consistent: it depends on local law. For a personal request, use the support path attached to your account rather than sharing sensitive credentials in an open message.

It covers details collected during account creation, phone verification, sign-in, support contact and wallet transactions. It also explains device records, cookies, retention and your request options. The policy applies when you use the lobby from Indonesia, where local law permits access.

We use your phone detail to create and secure the account, complete an account step before access and help identify a genuine request. If you ask about a Live Baccarat session or payment record, phone verification may be needed before we disclose account-specific details.

Yes. The Privacy Policy covers references connected with DANA, OVO, GoPay and QRIS, along with bank transfer and virtual account reconciliation. We use those references to match a status to your account and do not ask for your wallet or banking password.

Contact us through the support path linked to your signed-in account and ask for an account data copy. Include the phone or account reference you use. We may verify ownership first, then explain which records can be supplied and in what format.

Yes. Send a correction request through account support and identify the exact field, such as a phone detail or account name. We may ask for a verification step before changing it, especially if the request could affect sign-in or payment matching.

Retention depends on the type of record and whether it is needed for account security, payment reconciliation, dispute handling or a legal duty. You can ask support about a specific DANA, QRIS, bank transfer or virtual account entry and receive an explanation.

Use the account support route and describe the concern without sending a password, wallet PIN or full banking credentials. Mention whether it involves cookies, phone verification, device access or a payment reference. We will direct the request to the appropriate privacy contact.