Reference

Open your privacy choices before account access

kakek zeus Privacy Policy explains what we collect when you open an account, check wallet status or move between casino and sports pages.

Clear data purposesWallet record controlsMobile session securityRequest path included
kakek zeus Open your privacy choices before account access
PRIVACY SUPPORT

Find account help through our support path

A clear contact route matters when a Privacy Policy question concerns your own account rather than a general explanation. We ask you to contact us from the signed-in account where possible, so we can compare the request with the correct phone verification and wallet record. If you cannot access the account, use the available account help route and include the email or phone details connected to it. We will use the details you send only to identify the request and respond.

Team online

Account privacy request

Use the support path inside your account to ask what personal data we hold, why it is used and which records relate to your login or verification step. Sending the request from your signed-in account helps us match it without asking you to expose DANA, OVO or QRIS credentials.

Wallet record question

If a payment reference looks unfamiliar, contact support through the cashier-related help path and include the date, method and status shown on your account. We can check the record for DANA, GoPay, QRIS, bank transfer or virtual account activity without requesting your wallet password.

Access problem

When login or phone verification stalls, tell us which device and browser you used, then describe the Privacy Policy request in the same message. We use that context to separate a genuine account question from a session issue and direct it to the right support route.

DATA CONTROLS

Check security controls across your devices

Privacy work starts with practical account controls, not broad promises. We connect each request to the account step that created the record, check whether a device session is active and keep payment…

Account identity

We use the phone or contact detail attached to your account to identify you before discussing personal records. A clear phone verification step helps prevent one person from receiving another person's login, wallet status or transaction details.

Session cookies

Cookies can keep your signed-in session and selected settings available while you move through the lobby. You can clear them from your browser, although doing so may require another login and phone verification before account details appear again.

Payment references

Our records may show a DANA, OVO, GoPay, QRIS, bank transfer or virtual account reference and its status. These references help us reconcile a cashier event, but they are not a request for your wallet PIN, password or one-time code.

Device signals

We may record browser, device and session signals when they help protect account access or investigate an unusual login. If you switch from mobile to desktop, those signals help us distinguish a normal device change from an access request needing confirmation.

Retention period

We keep personal records only while they support account operation, security, dispute handling or a legal duty. When a stated purpose ends, we remove the record or reduce its link to you according to the retention process described in our Privacy Policy.

Change request

You can ask us to correct inaccurate account data, explain its use or remove eligible records through the support route. We may need to verify the request first, and access or deletion can be limited where local law permits continued retention.

Ask kakek zeus about Privacy Policy rights

These Privacy Policy answers address the account questions we expect before you open access. They cover the data behind phone verification, wallet status, cookies, device changes and requests for correction or removal. Read the full policy first, then use the account support path if your situation needs a record-specific answer. We apply the same approach whether you reach the lobby from a phone in Denpasar or from a desktop.

It covers personal data linked to your account, including contact details, phone verification, login activity, device signals, cookies and payment references. It also explains why we use each category, how long we retain it and how you can ask about access or correction.

Phone verification helps us confirm that an account request belongs to you before we discuss personal records or wallet status. It can also help protect a session when you change device. We use the verification detail for account security and the purposes stated in the Privacy Policy.

The policy distinguishes payment references from wallet credentials. We may record a DANA, OVO, GoPay, QRIS, bank transfer or virtual account status to match a cashier event, but you should not send us a wallet PIN, password or one-time code.

Yes. Send an access request through the signed-in account support path where possible and describe the records you want to understand. We may verify your identity before responding, because the Privacy Policy requires us to avoid giving account data to the wrong person.

Cookies can keep your session active and remember selected settings while you use the lobby. Clearing them through your browser may remove those settings and require another login. The Privacy Policy explains their role, while your browser controls whether stored cookies remain.

You can ask us to correct inaccurate details or remove eligible records through the account support route. We may retain some data for security, dispute handling or a legal duty. Any restriction depends on local law and the retention reasons explained in the policy.

Contact us through the support path connected with your account and include the request type, affected device and relevant payment date if needed. If login is unavailable, use the account help route and provide enough contact detail for us to identify the correct record.