Reference

Privacy Policy for Your ezi88 Account

ezi88 Privacy Policy explains how we collect, use and protect the account, wallet and device details you provide when you open an account.

Clear data purposesWallet status checksPhone verification
ezi88 Privacy Policy for Your ezi88 Account
CONTACT ROUTES

Use ezi88 Support for Privacy Requests

A clear contact route helps you act on the Privacy Policy without searching through the lobby.

Account privacy Ask us which account details are held and why they are needed. Include the phone number used during verification, but do not send a password or wallet PIN. We compare the request with the account record before sharing any private account response.
Wallet records For DANA, OVO, GoPay or QRIS questions, attach the payment reference and date rather than a full secret credential. Our support path can connect the receipt to the cashier record, explain the status and handle a privacy request linked to that transaction.
Policy changes If a detail on your account needs correction, tell us the old value, the requested value and the reason. We may ask for a phone verification step before changing it, helping keep an unauthorised person from altering your account record.
DATA PRACTICES

Browse How We Handle Your Data

The practical side of our Privacy Policy appears in the way account access, cookies and payment records are handled.

Account details

We use your phone number and account credentials to create access, confirm the right account and respond to requests about the Privacy Policy. We do not need your password in a support message, and we can ask for a separate verification step before discussing private account details.

Payment references

A DANA, OVO, GoPay, QRIS, bank transfer or virtual account reference may be tied to your account record when you check a cashier status. We use that reference to match a receipt or resolve a request, not as a substitute for your private wallet credentials.

Device signals

Your phone or browser can provide limited device and session signals that help us identify an unusual login or keep an account session working. These signals support account security and troubleshooting; they are handled within the purposes described in this Privacy Policy.

Cookies

Cookies can remember a session choice, keep a policy page available and help us understand whether a page request completed. You can manage cookie choices through your browser settings, although changing them may affect account access or the way a request is displayed.

Retention

We retain account, support and payment-reference records only as needed for the stated account purpose, security checks and a lawful request. If you ask how long a particular record is kept, tell us its category and we will assess the request under the rules that apply to you.

Your requests

You can contact us to ask for access, correction, deletion or an explanation of how a detail is used where local law permits. Provide enough account context for us to verify the request, and we will use the support route shown beside the cashier for the response.

Find Answers About Privacy Policy

These Privacy Policy answers focus on the account steps you are most likely to ask about before opening access. We explain what happens around phone verification, wallet references, cookies, device signals and support requests, with the same policy applying when you use a phone or desktop browser in Indonesia. If your question is not covered, use the contact route beside the cashier and identify the relevant account record without sending a password.

The ezi88 Privacy Policy covers account details, phone verification, device and session signals, cookies, support messages and payment references. It explains why we use each category, how it supports account access or a cashier request, and how you can ask about access, correction or deletion where local law permits.

Phone verification helps us connect an account request with the correct person before access or a private support reply. It can also protect changes to account details. We do not ask you to place a password or wallet PIN in a support message, and the step is handled under this Privacy Policy.

Yes. The Privacy Policy covers payment references connected with DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity. We may use a reference, date or receipt detail to match a cashier status or answer your request, while your wallet secret remains outside the support message.

Use the support path beside the cashier and state which account detail needs correction, why it is wrong and what value should replace it. We may verify your phone before making a change. Where local law permits, the same route can handle access, deletion or purpose questions.

Yes. The Privacy Policy applies when you access your account from a mobile browser or desktop browser. A device and session signal may help us identify unusual access or keep a session working, while cookie choices may affect how the policy and account pages behave.

We keep account, support and payment-reference records for the period needed for the stated account purpose, security checks and a lawful request. Retention can depend on the record category and local rules. Ask through support with the relevant date or receipt detail if you need a specific assessment.

Contact us through the support route shown beside the cashier and describe the Privacy Policy concern in plain English. Add your registered phone detail or payment reference only when needed for verification. Never include your password or wallet PIN; we may request a separate account check before replying.