Reference

Privacy Policy for Your zen288 Account

Our Privacy Policy explains how we collect, use and protect the details connected with your zen288 account, including login records, device signals and wallet activity.

Clear data purposesWallet record controlsPhone verification contextRequest path included
zen288 Privacy Policy for Your zen288 Account
CONTACT ROUTES

Where To Ask About Privacy Policy

A clear contact route matters when you want to check a record, correct an account detail or ask why a wallet event appears in your history. We direct privacy questions through the same account support path used for login and payment-status issues, so your request can be matched to the correct profile. Include your account identifier, the subject of your request and a reachable reply channel. We may ask for a verification step before discussing private records.

Team online

Support Chat Center

Open Support Chat Center from the account area and state that your request concerns the Privacy Policy. We can then identify whether you need access, correction, deletion clarification or an explanation of a DANA, OVO, GoPay or QRIS record.

Account access check

If you cannot sign in, tell us which phone verification step stopped you and the device path you used. We use that detail to separate an access problem from a privacy request without exposing account data before identity checks are complete.

Payment record query

For a wallet or bank-transfer question, include the payment rail, date and reference shown in your account. A precise DANA, QRIS, virtual account or bank-transfer reference helps us locate the relevant record while limiting the data shared in our reply.

DATA PRACTICE

How We Apply Privacy Controls

We apply this Privacy Policy at the points where your account creates useful records: opening access, moving between devices, contacting Support Chat Center and checking wallet status.

Account data

We may handle your name, phone number, account credentials, verification result and sign-in history so we can create access and…

Device signals

When you move from a mobile browser to desktop, we may record browser type, operating-system details, session time and security…

Cookies

Cookies can keep a sign-in session, remember a language choice and help us understand whether a page loads correctly.

Wallet records

Payment references from DANA, OVO, GoPay, QRIS, BCA, BRI, Mandiri or BNI may be linked to your account status.

Retention checks

We retain account, support and transaction records only for the period needed for the stated service, security or legal purpose.

Change requests

To request access, correction or a change to your data, contact Support Chat Center from the verified account where possible.

Privacy Policy Questions Answered

These questions focus on the records you are most likely to notice while opening or using a zen288 account. We explain how the Privacy Policy connects phone verification, mobile access, local wallet references and support requests. If your situation is not listed, use Support Chat Center and describe the exact account or payment record you want us to check.

The zen288 Privacy Policy covers account details, phone verification, sign-in events, device signals, cookies, support messages and payment references. It explains why we use each category, how we protect access and how you can request a copy, correction or clarification.

Phone verification helps connect an account request to the person controlling the registered number. We may use the result when you open access, recover a session or ask about private records. We do not disclose account details before the required identity check.

Yes. The Privacy Policy covers references connected with DANA, QRIS, OVO, GoPay, bank transfer and virtual account activity. We use those references to match a status, check a receipt query and identify a mismatch, rather than storing unrelated wallet content.

You can contact Support Chat Center from your verified account and ask for an access request under the Privacy Policy. Include the phone number linked to the account and the record type you need. We may confirm identity before preparing a response.

Send a correction request through Support Chat Center and identify the field that needs changing, such as a phone detail or account name. We may request phone verification, compare the request with account records and tell you if a legal restriction affects the change.

Retention depends on the purpose for which a record was created, including account access, payment reconciliation, security or a legal requirement. When you ask for deletion, we first check whether the record must remain. We explain the outcome through the available support path.

Yes, access depends on local law. Our Privacy Policy describes data handling for supported Indonesian access, but eligibility and available account functions can vary by location. If you are in Denpasar or elsewhere, contact support when a local access question affects your request.