Reference

Open e88pro Privacy Policy With Clarity

Our Privacy Policy explains what we collect when you open an e88pro account, move through the lobby and check wallet status.

Account dataWallet recordsDevice controlsPolicy requests
e88pro Open e88pro Privacy Policy With Clarity
REQUEST A HAND

Browse Your Privacy Support Path

A clear request path helps when you want to ask about personal data rather than a wallet balance or lobby title. Contact our support route from your account context and include the phone number or account detail needed to locate the record. If your question concerns a DANA, OVO, GoPay or QRIS receipt, attach the payment reference while removing unnecessary private details. We use the account and payment context to check the request, explain the relevant handling and direct you to the next step.

Team online

Account request

Ask us to find the personal data connected with your account after phone verification. Include the account contact you use to sign in, so we can distinguish your request from another account without asking you to send a full payment history.

Wallet record

For a privacy question about DANA, OVO, GoPay, QRIS, bank transfer or virtual account records, share the transaction reference and date. We use those details to locate the relevant status while avoiding a request for your wallet password or complete wallet credentials.

Policy clarification

If a paragraph in this Privacy Policy does not match what you see after signing in, send the wording and your device path, such as mobile browser or desktop browser. We can explain the data step involved and tell you how to request a correction.

DATA HANDLING

Switch Through Our Privacy Controls

We keep the Privacy Policy practical by linking each data category to an account action you can recognise.

Account details

We handle details such as your account contact and phone verification status to create, secure and maintain access. When you ask us to check a record, we use the account path connected to your sign-in rather than treating an unverified message as proof of ownership.

Payment matching

A selected rail such as QRIS, DANA, OVO, GoPay, bank transfer or virtual account may create a payment record with a reference and status. We use that operational trail to match the account action, investigate a stalled receipt and answer related privacy requests.

Device signals

We may process browser, device and connection signals when you sign in from mobile or desktop. These details help us identify unusual access, diagnose a page that will not load and keep the account path separate from another device session.

Cookie choices

Necessary cookies support session continuity between phone verification, the lobby and account pages. Where optional cookies are offered, your browser controls can limit them. Changing cookie settings may affect saved session behaviour, but it does not erase account records by itself.

Retention decisions

We keep personal data for the period needed to run the account, reconcile payment status, investigate security events or meet applicable legal duties. When a record no longer serves one of those purposes, we work to delete it or reduce it to a form that no longer identifies you.

Change requests

You can ask about access, correction, deletion or the handling of a specific record through our support route. Tell us whether the request concerns phone verification, device data, cookies or a payment reference, and we will explain the checks needed before making a change.

Find Privacy Policy Answers

These Privacy Policy answers focus on the account and payment questions you are most likely to have before opening access from Indonesia. We keep the examples concrete so you can identify the relevant record, device path or account step. If your situation is different, contact us with only the details needed to locate your request. Access depends on local law, and the handling described here applies to the e88pro service available to you.

The e88pro Privacy Policy covers account details, phone verification, sign-in activity, device signals, cookies, support messages and payment records. It explains why we use each category, how we retain it and how you can ask about access, correction or deletion.

We use phone verification status to support account ownership checks and protect the sign-in path. It helps us respond to an account request without relying on an unverified message. We do not need your wallet password to investigate a Privacy Policy question.

Yes. The Privacy Policy includes operational records connected with DANA, OVO, GoPay, QRIS, bank transfer and virtual account steps. We may use a payment reference, selected rail and status to match an account action or answer a privacy request.

We may handle browser, device and connection details from your mobile or desktop session. These signals help us investigate sign-in issues, identify unusual account access and separate one session from another. They are not a request for your private device files.

Contact our support route from your account context and state whether you want access to a record or a correction. Include the sign-in contact, the data category and any relevant payment reference. We may verify account ownership before responding to protect your information.

You can send a deletion request through our support route and identify the account record involved. We assess the request against account operation, payment reconciliation, security needs and applicable legal duties. Some records may need to remain for those purposes.

This Privacy Policy is written for the Indonesia service path, but access and eligibility depends on local law. The exact account and payment experience can also depend on the region, device and selected rail. Contact us if your available path differs.