Reference

Open e888 Privacy Policy Before Your Account

e888 Privacy Policy explains what account, device and wallet details we use, why we use them, and how you can ask about your records before opening an account.

Clear data purposesWallet detail handlingCookie choicesAccount request path
e888 Open e888 Privacy Policy Before Your Account
REQUEST SUPPORT

Switch From Login Help To Privacy Contact

A privacy question should not get lost beside a login or wallet issue. We keep a clear route from your account support area so you can identify the account involved, describe the request and attach a payment receipt or status reference when it matters. Use the same route if DANA, OVO, GoPay or QRIS activity appears unfamiliar. We may ask for account checks before discussing personal details, and we handle each request under this Privacy Policy.

Team online

Account support route

Open the support area after signing in and state that your request concerns the Privacy Policy. Include the account phone number only through the protected account path, so we can locate the correct record without asking you to post personal details publicly.

Payment reference check

For a wallet question, send the relevant receipt or transaction reference through the account contact route. We can compare the reference with DANA, OVO, GoPay or QRIS status while avoiding requests for your wallet PIN or full payment credentials.

Access issue path

If phone verification prevents access to your privacy request, explain the device path you used, such as mobile browser or desktop browser. We use those details to separate an account access problem from a personal-data request and continue the check safely.

DATA PRACTICES

Browse e888 Data Handling In Plain Terms

We keep the Privacy Policy practical by linking each data category to an account task. Phone verification supports account access, device records help us investigate unusual sign-in behaviour, and wallet references help…

Account details

When you open an account, we receive the details needed to create and maintain that account, including contact data and the result of phone verification. We use those details for access checks and account requests, not as a reason to ask for unrelated personal material.

Device records

A mobile browser or desktop browser may send technical signals such as session data, browser type and security events. We use these records to keep a sign-in session working and investigate unusual access, including a switch between your phone and computer.

Cookie controls

Cookies can keep a session active and remember selected settings, but you can manage them through your browser controls. Turning some cookies off may affect account access or page preferences; it does not automatically erase records already needed for a valid request.

Wallet references

A DANA, OVO, GoPay or QRIS reference may appear in our transaction records when you use that route. We use the reference to match status and receipts, while your wallet PIN and separate wallet login remain outside the account data we request.

Retention checks

We keep personal data for the period needed to provide account access, investigate a support case, resolve a payment dispute or meet a legal need where applicable. When the purpose ends, we delete, anonymise or restrict the record according to the policy.

Change requests

You can ask us to correct inaccurate account details, explain a data use, provide access to relevant records or address a deletion request. Send the request through account support, identify the account, and complete the verification step needed to protect your information.

Browse e888 Privacy Policy Answers

These Privacy Policy answers address the searches we hear before an account is opened or when a wallet record needs checking. We explain the account step, browser behaviour and request route in plain English for Indonesian customers. If your question involves eligibility or access, remember that it depends on local law and applies where local law permits.

It covers account details, phone verification, browser and device records, cookies, wallet references, support requests, security checks and retention. It also explains how to request access, correction or deletion where applicable. The policy applies to your use of the account and related pages where local law permits.

Phone verification helps us confirm that the person requesting account access or a privacy change controls the account contact route. We record the verification result and related account details for security and access purposes. We do not need your DANA, OVO, GoPay or QRIS PIN.

Yes. The policy covers technical records created when you use a mobile browser or desktop browser, such as session details, browser type and security events. These records help keep login working, remember selected settings and investigate unusual access without requiring a separate mobile application.

We may receive a payment reference, receipt detail or status result when you use DANA or QRIS, and similar records may apply to OVO, GoPay, bank transfer or virtual account. We use these details to match account activity and support checks, not to collect your wallet PIN.

Use the account support route and state whether you want access to relevant personal data, a correction or an explanation of processing. Identify the account and complete phone or account verification when requested. We assess the request under the Privacy Policy and applicable local requirements.

You can send a deletion request through account support. We first verify the account and assess whether records must remain for account security, a payment dispute, an open support matter or a legal need. Where deletion is permitted, we remove, anonymise or restrict the relevant data.

Start from the signed-in account support area and label the message as a Privacy Policy request. Add a clear description and, for a wallet concern, the receipt or transaction reference. Do not send a wallet PIN or full credentials. We may request verification before discussing the record.