Reference

zeus40 Privacy Policy for Indonesian Accounts

We keep this policy focused on the data needed to open your account, verify sign-in, remember your session, and answer privacy requests without extra steps.

Account dataCookie dataDevice signalsSupport access

Browse Lobby Read FAQ

What This Policy Covers

zeus40 Service availability depends on jurisdiction. Users are responsible for checking local law before access.

Our policy covers the data we collect when you open an account, contact us, or move money through DANA, OVO, GoPay, or QRIS. We keep account details, transaction references, device logs, and cookie records so we can verify you, stop duplicate requests, and explain what happened

1
if you ask about a transfer. We do not keep more than we need for those jobs, and we retain each record type only for the period required by law or operational need. If local law limits what we can collect or store, we follow that
2
rule. When access or eligibility is discussed, it depends on local law and is available only where local law permits. You can ask us to correct, export, or close records through support after we verify your account.

Service availability depends on jurisdiction. Users are responsible for checking local law before access.

CONTACT PATHS

Where to Ask About Privacy

If you want to ask about this policy, we keep three contact paths open so you can reach the right team quickly.

DATA PRACTICE

How We Handle Privacy Requests

We handle privacy requests with a simple flow: collect only what we need, separate payment records from chat logs, and let you change or close records through the account you already use.

Data minimisation

We ask for account name, contact details, and device signals only when they help us verify you or handle your request. We avoid collecting extra fields that do not serve a privacy purpose.

Cookie use

Cookies keep you signed in, remember language choice, and help us spot repeated login failures. You can clear them in your browser, but some session features may reset until you sign in again.

Account security

We use login history, IP checks, and device markers to flag access that does not match your normal pattern. If anything looks wrong, we may ask you to confirm through the email on file.

Retention rules

We keep records only as long as needed for account handling, dispute resolution, or legal duties. Different record types can have different retention periods, so payment logs and chat logs do not share one timer.

Change requests

You can ask us to correct, export, or close certain records after we confirm ownership. We handle each request by account email and a second check, so no one can change your data without proof.

Contact path

For privacy matters, use live chat, email, or the logged-in request form. We log the request timestamp and the team that handled it, which helps us trace your case from start to finish.

Common Privacy Questions From You

These are the questions we hear most when you open an account, connect a wallet, or ask us to change stored data. We answer from the policy we apply inside the lobby, and we keep each request tied to your verified account so no one else can act for you. If local law changes what we can collect or keep, we adjust the policy and apply the rule only where local law permits.

We collect the contact details, login credentials, device signals, and basic session data needed to verify access and keep the account running. If you use DANA, OVO, GoPay, or QRIS, we may keep transaction references for reconciliation.

Cookies help us remember your session, language choice, and recent sign-in state so you do not repeat the same steps on every visit. They also help us detect unusual logins and stop repeated failed attempts.

Send the request through live chat, email, or the logged-in form, and include the account email plus the field you want changed. We verify ownership first, then update the record or explain why we cannot.

We keep each record type for the time needed to run the account, resolve a dispute, or meet a legal duty. Payment references, support logs, and device logs can each follow a different retention period.

Only staff who need the data to operate your account, answer a request, or check a payment reference can access it. We keep access limited by role, and we expect partners to handle their side with the same care.

If local law changes what we may collect, store, or disclose, we update the policy and follow the new rule only where it applies. Access or eligibility depends on local law and is available only where local law permits.

You can ask us to close the account and check which records must stay for legal or dispute reasons. After verification, we remove or lock the rest according to the retention rule for that record type.

zeus40 Privacy Policy for Indonesian Accounts

Where to Ask About Privacy

How We Handle Privacy Requests

Data minimisation

Cookie use

Account security

Retention rules

Change requests

Contact path

Common Privacy Questions From You

01 What data do you collect when I open an account?

02 Why do you use cookies on my device?

03 How can I ask for a correction to my data?

04 How long do you keep my records?

05 Who can see my personal data?

06 What happens if local law changes?

07 Can I close my account and remove data?

Related Pages