Reference

Privacy Policy for Your zeus slot Account

Our Privacy Policy explains how we collect, use and protect the details you provide when opening or using a zeus slot account.

Account dataWallet statusDevice accessYour requests
zeus slot Privacy Policy for Your zeus slot Account
CONTACT ROUTES

Privacy Questions Through Your Account Path

A direct contact path helps you ask about the Privacy Policy without sharing more than necessary. Start from the account support route and include the phone number or reference connected with your request, but leave out passwords, wallet PINs and one-time codes. Our support team can help you identify the right data request, check a wallet-status record or explain an access question. If you are in Makassar, the same account route applies on mobile and desktop. Where local law permits, we respond through the contact channel attached to your account.

Team online

Account message

Send a privacy question through the account contact path and describe the record you want checked, such as a phone verification entry or login event. We use the account reference to locate the request while you keep passwords, wallet PINs and one-time codes private.

Wallet query

If your question concerns DANA, OVO, GoPay, QRIS, bank transfer or virtual account data, include the transaction reference rather than private wallet credentials. We can explain the status record held for reconciliation and tell you which part belongs to the payment provider.

Access request

Ask us to review, correct or explain personal data connected with your account. We may request a matching account detail before releasing data, because the Privacy Policy requires us to protect your records from an unrelated requester.

DATA HANDLING

What We Do With Account And Device Data

The Privacy Policy is designed around practical account events rather than vague data categories.

Account creation

When you open an account, we use the details entered in the account form and the phone verification result to create an access record. This lets us connect your login activity and privacy requests to the correct account without asking you to repeat every detail.

Payment references

DANA, OVO, GoPay and QRIS can return a payment status or reference that helps us match an account action. For bank transfer and virtual account requests, we retain the reconciliation reference needed to explain a status without storing your banking password.

Cookies

Cookies and similar browser storage can keep a session active, remember a language or help us understand whether an account page loaded correctly. You can manage browser permissions, though blocking essential storage may interrupt login or remove saved session choices.

Device security

We may use device, browser and login-time signals to spot an unusual access pattern, protect your account and investigate a security report. These signals are reviewed for account protection and are not a reason to request your wallet PIN in a support conversation.

Retention choices

We retain account, payment-reference and contact records for the period needed to operate the service, resolve disputes, protect accounts or meet applicable duties. When a record is no longer needed for those purposes, our handling process removes it or separates it from direct account use.

Data changes

You can contact us to ask whether your personal data is accurate, request a correction or ask how a particular record is used. We may verify the request through your account path first, then explain any legal or operational reason a record must remain available.

Privacy Policy Questions From Indonesia

These Privacy Policy answers address the account and wallet questions we hear most often from Indonesian customers. They explain what you can ask us to check, how verification works and why some records remain available after an account action. If your situation is different, use the account contact route and include a reference that helps us locate the request.

It covers personal data connected with your account, including contact details, phone verification, login events, device signals, cookies, payment references and support requests. It also explains why we use those records, how we protect them, how long they may remain and how you can ask about them.

We use your phone number to create and identify your account, complete phone verification and send account-related responses through the available contact route. If you ask about the Privacy Policy, the matching phone detail helps us avoid disclosing personal data to someone who cannot establish account connection.

Yes. It includes payment references and status details connected with DANA, OVO, GoPay and QRIS, along with bank transfer or virtual account references when used. We use those details to match an account request, explain a status and handle a dispute without requesting your wallet PIN.

You can contact us through the account support path and identify the data that appears incorrect. We may ask for an account-linked detail before making a change. After checking the request, we correct the record when appropriate or explain why an operational or legal record must remain unchanged.

On a phone or tablet, cookies and browser storage can keep your session, language choice or security state available between pages. You can adjust browser permissions, but blocking essential storage may interrupt account access. The Privacy Policy treats these signals as part of session and security handling.

We keep account, payment-reference and contact records for as long as needed for account operation, security checks, dispute handling or applicable duties. The period depends on the record and purpose. You can ask us about a specific item, and we will explain the retention reason where local law permits.

Use the contact route linked to your account and state whether you want access, correction, an explanation of use or a retention question. Include a relevant account or payment reference, but never include a password, wallet PIN or one-time code. Access depends on local law.