Reference

zeus400 Privacy Policy for Indonesia

Our Privacy Policy explains how we collect, use and protect the details linked to your zeus400 account, including phone verification, wallet activity and device access.

Account clarityWallet recordsDevice controlsCookie choices
zeus400 zeus400 Privacy Policy for Indonesia
CONTACT PATHS

Privacy Help Beside Your Account

A clear contact path helps when a privacy question appears during sign-in or wallet checking. We ask you to contact us through the support route shown inside your account and include the email or phone detail connected to the request. That lets us match the request to the correct record without asking you to send a full payment credential. For a QRIS receipt, DANA status or device-access concern, keep the reference and approximate time available so we can trace the relevant event.

Team online

Account request

Use the account support route when you want to ask what personal details are held for your zeus400 profile. We may request a phone verification step before discussing account-linked data, helping us avoid disclosing details to the wrong person.

Wallet record

For a DANA, OVO, GoPay or QRIS privacy question, send the transaction reference rather than a wallet password or full security code. We use the reference to locate the relevant status record and separate it from unrelated account activity.

Access concern

If your account opens on one device but not another, tell us the device type, browser path and approximate time. We can examine session signals and guide you through account checks without requesting unnecessary personal details.

DATA PRACTICES

How We Handle Your Privacy

Privacy work sits alongside the account steps you already use: phone verification, wallet status checks and sign-in from mobile or desktop.

Account data

We use your account details to create access, verify the phone connected with the profile and respond to account requests. A request about your record may require a matching account step, especially when the question concerns wallet activity or a sign-in event.

Wallet details

For DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity, we retain practical references such as method, amount status and time needed to reconcile a request. We do not need your wallet password to investigate a receipt or pending status.

Cookies

Cookies and similar session tools help keep the signed-in path connected while you move from the account page to the lobby. Browser settings can restrict some cookies, although changing them may require you to sign in again or repeat a security check.

Device security

We may record basic device and browser signals to spot unusual access, protect your session and investigate repeated login failures. If you switch from a mobile browser to desktop, these signals can differ and may lead to an additional account check.

Storage period

We keep personal and transaction records only for as long as needed for the stated account, support, security or legal purpose. The period can differ by record type, and a deletion request may be limited where a record must be retained for a valid legal or dispute reason.

Changes and requests

You can ask us to access, correct or clarify personal data through the account support route. Include the profile contact and the specific request; we may verify ownership before making a change, and we will explain any restriction that depends on local law.

Privacy Policy Questions From Indonesia

These Privacy Policy answers focus on the account, wallet and device situations you are most likely to encounter. If your question concerns a specific record, use the support route inside your account and include only the details needed to locate it.

The zeus400 Privacy Policy covers account details, phone verification, wallet references, support messages, cookies and device signals used during access. It also explains how we use, protect, store and respond to requests about those records, with access that depends on local law.

You should never send a DANA, OVO or GoPay password through support. Our payment records use practical references such as method, status, time and transaction number so we can reconcile a request without needing your wallet security credentials.

A QRIS record may contain a reference, selected method, status and timing needed to match the account request. If you ask about a QRIS receipt, provide the reference and approximate time through account support, not your wallet password or full security code.

Yes. Send a correction request through the support route inside your account and identify the specific field, such as a phone detail or contact address. We may ask you to complete phone verification before changing account-linked data.

Ask for access through the account support path and state which record you need, such as profile data, cookie activity or a bank transfer reference. We may confirm account ownership first, then explain the available response and any limit that depends on local law.

Yes. The policy covers basic browser, device and session signals created when you sign in from mobile or desktop. These signals help protect the account and investigate access issues; restricting cookies may cause another login or phone verification step.

Storage depends on the record and its purpose. We keep account, support, security and payment references for as long as needed for those purposes or a valid legal requirement. You may ask us to clarify a specific retention period through account support.