Reference

empaire88 Privacy Policy For Your Account

Your account details, wallet records and device access stay covered by the empaire88 Privacy Policy, so you can understand what we collect before opening an account.

Clear data purposesWallet record clarityAccount request pathMobile access details
empaire88 empaire88 Privacy Policy For Your Account
REQUEST HELP

Privacy Questions Follow Your Account Path

A clear contact route matters when you want to ask about the Privacy Policy, so we keep policy requests close to the account and cashier areas. Use the support path shown after login and include the email or phone detail attached to your account. We may ask for a transaction reference, such as a QRIS or virtual account record, to locate the right entry without requesting unnecessary details.

Team online

Policy request

Ask us what account, device or transaction data we hold by using the support route connected to your account. Include your registered phone detail and describe the request clearly; we will use those details to locate the relevant record and respond through the available account contact path.

Wallet record check

If a DANA, OVO, GoPay or QRIS entry looks unfamiliar, send the payment reference and approximate time through account support. We can compare the record with the cashier event while limiting the request to details needed for that specific check, rather than asking for your wallet password.

Access concern

For a login or phone-verification concern, tell us which device path you used and when the issue appeared. A request tied to your account helps us review security events, protect access and explain what data was used during the check.

HANDLING DETAILS

How empaire88 Handles Privacy Requests

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

Data collection

We collect details that help create and protect your account, such as contact data, phone-verification status, login events and device signals. Payment references from DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity are handled as transaction records, not as permission to access your wallet.

Cookie choices

Cookies may keep an account session active, remember a language or display essential security settings on your mobile browser. You can review browser controls and clear stored cookies, although doing so may require another login or remove preferences used along the account path.

Account security

Phone verification and device checks help us distinguish a normal login from an unusual access attempt. We do not ask for your wallet password through support. If a security event affects your account, we may request account-linked details before discussing the record.

Retention periods

We retain account, support and transaction records only for the period needed for the purposes described in the Privacy Policy, including security review and required record keeping. The period can vary by record type and may depend on local law or an unresolved account request.

Your data requests

You can ask whether we hold your account data, request a correction, or ask about deletion where local law permits. Send the request through the account support path and identify the relevant record, such as a login event or QRIS reference, so we can process it accurately.

Third-party handling

Payment and technical partners may process limited details needed to complete a wallet or bank transaction, display a status or protect an account session. We share only the relevant record for that purpose, and the Privacy Policy explains the context for DANA, OVO, GoPay and QRIS references.

Privacy Policy Answers Before Account Access

These Privacy Policy answers address the searches we hear before an Indonesian account is opened. We focus on practical points: what is collected, how a wallet record is used, what happens on a mobile device and where to send a request. If your situation involves eligibility or access, the outcome depends on local law.

The empaire88 Privacy Policy covers account details, phone-verification status, login and device events, cookies, support requests and transaction references. It explains why we use each category, how we protect account access and how you can ask about correction, deletion or another eligible data request.

We may store references needed to identify a DANA, OVO, GoPay, QRIS, bank transfer or virtual account transaction, including status and timing. We do not need your wallet password for a support check. The relevant record is used to trace the account event and respond to your request.

Yes. The Privacy Policy covers limited device and browser signals used for login continuity, security checks and account troubleshooting. A mobile path from login to the lobby may create session and time records. Clearing cookies can end that session and require phone verification or another login step.

Use the support route shown inside your account and describe whether you want access, correction or another request allowed where local law permits. Include your registered phone detail and the relevant record, such as a login date or QRIS reference, so we can identify the correct account.

Retention depends on the type of record and the purpose described in the Privacy Policy. Account, security, support and transaction entries may be kept while needed for those purposes or for record duties that depend on local law. We can explain the applicable period when you submit a specific request.

You can ask which cookies support your session, preferences or security settings. Browser controls let you clear or restrict them, but this may sign you out or remove stored choices. Our support route can help identify an account-access issue without asking for your wallet password.

Contact us through the support path connected to your account and label the request as a Privacy Policy concern. Provide only the details needed to locate it, such as your registered phone detail, device path or transaction reference. We will use that context to review the request and explain the next step.