Reference

Privacy Policy for Your zeus23 Account

Your account details, wallet references and device signals are covered in the zeus23 Privacy Policy, so you can see what we collect and why.

Clear data purposesWallet records explainedAccount access choicesContact path included
zeus23 Privacy Policy for Your zeus23 Account
DATA HELP DESK

Three Ways to Ask About Your Data

A direct support route keeps privacy questions separate from ordinary lobby browsing. Start from the account help area when you need to check a phone record, cookie choice or wallet reference; our team can link the request to your account without asking you to send a password. If you are in Medan or elsewhere in Indonesia, use the same digital routes shown on the site, with service availability displayed in the support panel.

Team online

Account help

Use the account help path to ask which profile details are stored, correct a phone number, or clarify the verification record attached to your access. We may ask for an account identifier so we do not disclose personal data to the wrong person.

Wallet enquiry

For a DANA, OVO, GoPay or QRIS reference, contact support through the cashier-linked help route. Include the date, status and reference shown to you, but never send a wallet PIN, password or one-time security code in your message.

Privacy request

Choose the privacy contact option when you want access, correction, deletion or a copy of your account records. We will confirm the request, check account ownership, explain any lawful retention need, and tell you what action can be taken.

SIX PRIVACY CONTROLS

Six Controls Behind Your Account Privacy

Our privacy process follows the points you can check from your own account activity: what you entered, what your device sent, and which support action followed.

Account data

We collect details you provide during account creation, including contact information and the phone verification result. These fields help identify your profile and support a requested correction. We do not need your wallet PIN or account password in a support message.

Device signals

When you move from login to a mobile lobby, we may record browser type, device signals, session times and security events. These records help investigate unusual access and keep a session tied to the device activity you initiated.

Cookie choices

Cookies can preserve a session, remember a selected setting and help us understand technical errors. Your browser controls whether optional cookies remain. Removing them may require another login, while essential session functions can still be needed for account access.

Wallet records

Payment records can show whether a DANA, QRIS, OVO, GoPay, bank transfer or virtual account request was created, matched or completed. We use those references for reconciliation and support, while sensitive wallet credentials stay outside our request process.

Security checks

Phone verification, sign-in records and unusual-session checks help us protect your account. If a request concerns a sensitive change, we may confirm ownership before acting. Never share a password or one-time code when asking about privacy.

Retention and changes

We keep records for the period needed for account support, security, disputes or legal duties. You can request correction or deletion through support; we will explain if a specific record must remain and update you on the result.

Privacy Policy Questions Indonesian Accounts Ask

These answers address the privacy searches we hear most often before an account is opened or a wallet status is checked. They cover access, payment references, cookies, retention and contact steps in plain English, with the same local-law wording used throughout our Privacy Policy.

It covers account details, phone verification, device and session signals, cookies, support messages, and payment references connected with DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity. It also explains retention, security checks, your request rights and how access depends on local law.

We use the phone verification result to connect an account request with the correct profile and to help protect access. It can also support a correction or recovery request. We do not ask you to place a password or one-time code inside a support message.

Yes. The Privacy Policy covers transaction references, status, amount and time linked with DANA or QRIS, along with comparable records for OVO, GoPay, bank transfer and virtual account requests. These details help reconcile a request without requiring your private wallet credentials.

You can contact us through the privacy request route to ask what account records we hold or to correct inaccurate details. We may verify ownership first, then confirm the scope, explain any record that must remain, and report the action taken.

Use your mobile browser cookie controls to remove or restrict optional cookies, and revisit the site settings when available. Essential session cookies may still be needed for login. Clearing cookies can sign you out and may remove saved preferences from that device.

We retain records while they are needed for account support, security investigations, payment reconciliation, disputes or legal duties. When a purpose ends, we remove or anonymise the relevant data where practical. A privacy request can ask us to explain a particular retention period.

Open the account help area and choose the privacy contact option, or use the cashier-linked support route for a wallet reference. State whether you need access, correction or deletion, include your account identifier, and leave out passwords, wallet PINs and one-time codes.