Reference

zeus138 Privacy Policy, Clearly Explained

Our Privacy Policy shows what zeus138 collects when you open an account, sign in from a mobile device, or connect DANA, OVO, GoPay and QRIS.

Account dataWallet detailsDevice choicesYour requests
zeus138 zeus138 Privacy Policy, Clearly Explained
CONTACT YOUR WAY

Privacy Questions Reach The Right Desk

A direct support request is the quickest way to ask about this Privacy Policy or the data linked to your account. Include your registered phone number, the subject of your request, and a short description of the record you want checked. We use the account support route for login and wallet-status questions, while policy requests stay focused on collection, access, correction and deletion.

Team online

Account support path

Use the signed-in account route when you need a copy of account data or want us to check a phone-verification record. We can match the request to your account before discussing personal details.

Wallet status request

If a DANA, OVO, GoPay or QRIS reference appears incorrect, send the payment reference and date through support. We review the record without asking you to share a wallet password or private PIN.

Device access query

Tell us which phone, browser or session concerns you when asking about device data. We can explain the security record connected with that access and note a correction request for review.

HOW WE HANDLE DATA

Practical Privacy Steps Inside zeus138

We keep this policy practical: you should know what happens after each account action and where to ask for help.

Collection at account opening

When you open an account, we collect the details needed for account creation and phone verification. A clear account path helps us connect later privacy requests with the correct record rather than a shared device.

Cookies and session storage

Cookies and similar session tools remember sign-in state, language choices and basic navigation. On mobile, clearing browser data may sign you out and remove those preferences without deleting the account itself.

Mobile device signals

Our security checks may record browser type, operating system, session time and approximate network details. These signals help identify unusual access when you move from a phone to a desktop browser.

Wallet record matching

For QRIS, DANA, OVO, GoPay, bank transfer or virtual account requests, we use references and status details to reconcile the account record. We do not ask for your wallet password or private PIN.

Retention and removal

We retain personal records while they serve account operation, dispute handling, security checks or legal needs. When a record no longer serves those purposes, we remove it or change it so it no longer identifies you.

Requests and corrections

You can ask what personal data we hold, request a correction, or ask about removal through account support. We may verify your account details first so another person cannot change your record.

Privacy Policy Answers For Your Account

These Privacy Policy questions cover the actions you are most likely to take before opening or using a zeus138 account. Each answer points to a practical record, device step, wallet reference or support path, so you know what to prepare when asking us for help.

It covers account creation, phone verification, device sessions, cookies, game browsing, support requests and payment references from DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity.

We use your phone number to create and verify the account, connect you with the correct support record, and help protect access when a sign-in or wallet-status question is raised.

Yes. The policy covers browser type, operating system, session time and approximate network details. These signals help us identify unusual access when you switch between a phone and desktop.

We use payment references and status details to reconcile your account record. The Privacy Policy does not require your DANA or QRIS password, private PIN or wallet login credentials.

Yes. Send a request through account support with your registered phone number and the records you want checked. We may verify account ownership before sharing personal details.

Contact account support, describe the incorrect field, and provide the account detail needed to locate it. We record the correction request and may ask for phone verification first.

We keep records while they support account operation, payment reconciliation, security, disputes or legal needs. After that period, we remove or anonymise them through our retention process.