Reference

Privacy Policy For Your zen55 Account

Our zen55 Privacy Policy shows what account details we collect, why phone verification is needed, and how wallet records from DANA, OVO, GoPay and QRIS are handled.

Clear data purposesWallet record contextPhone verification rulesDirect privacy contact
zen55 Privacy Policy For Your zen55 Account
CONTACT PRIVACY

Get Help With A Privacy Request

A clear contact path matters when a name, phone number or wallet record needs attention. Send your privacy question through the account support route, and include the phone number linked to your account plus the subject of your request. We check enough account detail to prevent disclosure to the wrong person, while avoiding unnecessary copies of identity documents. Our support team handles login and wallet-status questions daily from 08:00 to 22:00 WIB, so you have a defined window for follow-up.

Team online

Account support

Use the support route connected to your account when you need a copy, correction or explanation concerning your Privacy Policy rights. Include your registered phone number and a short description so we can locate the relevant record without asking you to repeat the full history.

Wallet questions

If a DANA, OVO, GoPay or QRIS reference appears incorrectly, send the payment date, rail name and visible status rather than sharing a password or wallet PIN. We use those details to compare the account record and tell you what can be changed.

Support hours

Privacy and account queries are received daily from 08:00 to 22:00 WIB through the account support channel. A request about phone verification, cookie settings or retention can be routed to the team handling data questions during that service window.

DATA CARE DETAILS

What Our Privacy Controls Cover

We treat privacy as an account process rather than a short notice hidden after registration. The controls below explain how we separate necessary records from optional page settings, limit internal access, and…

Account details

We collect details such as your chosen account identifiers and linked phone number to create access, send account replies and complete phone verification. We do not need your password in a support message, so leave it out when asking us to correct or explain a record.

Payment references

A DANA, OVO, GoPay, QRIS, bank transfer or virtual account transaction can create a reference, amount and status record. We use these fields to match payment activity and resolve a receipt question; wallet credentials and PINs should remain with your payment provider.

Cookies and devices

Necessary cookies support sign-in continuity, while limited device and browser signals help identify unusual sessions. You can clear browser data or change cookie controls, although removing necessary cookies may require you to verify your phone again before account access.

Account security

Phone verification is required before account access, and security events may be recorded when a new device, browser or location pattern appears. If your code arrives unexpectedly, do not share it; contact account support so we can check the session.

Retention choices

We keep account, support and payment-reference records for the period needed for service operations, security checks, disputes and legal duties. When a record no longer has a valid purpose, we remove it or separate it from direct account identifiers.

Change requests

You can ask for access, correction, deletion or an explanation of applicable personal data through account support. State the request clearly and provide the registered phone number; we may ask a short verification question before discussing account-linked details.

Answers About The zen55 Privacy Policy

These Privacy Policy answers address the searches we hear most often before account access. Each response stays close to the records you create, the device you use and the contact path available to you. If your situation involves eligibility or location, access depends on local law and where local law permits.

The zen55 Privacy Policy covers account details, phone verification, device and browser signals, cookies, support messages, and payment references linked to DANA, OVO, GoPay, QRIS, bank transfer or a virtual account. It also explains retention, security measures and how you can request changes.

We use your phone number to create a clear account path and verify that the person requesting access controls the account contact. It can also help us answer account questions. Do not send your verification code or password in a support message.

Yes. The Privacy Policy includes payment references created when you use QRIS, DANA, OVO or GoPay. We may record a rail name, transaction reference, date and status to match activity or resolve a receipt question, but your wallet PIN stays with the payment provider.

Use the account support route and state whether you want access, correction, deletion or an explanation. Add the phone number linked to your account and the relevant record, such as a cookie setting or QRIS reference. We verify the request before sharing account-linked details.

We retain personal data only while it supports account operations, security checks, payment questions, disputes or legal duties. Retention can differ by record type. After the purpose ends, we remove the record or separate it from direct account identifiers where practical.

You can clear browser data or adjust cookie settings on your mobile or desktop browser. Necessary cookies support sign-in continuity, so disabling them may end a session or require phone verification again. Our Privacy Policy explains why each necessary setting is used.

Send the question through account support between 08:00 and 22:00 WIB each day. Mention Privacy Policy rights and the registered phone number, without sending a password, PIN or verification code. We can then route the request for access, correction, deletion or retention details.