Reference

Open Your Privacy Policy Path

Our Privacy Policy explains how efek88 handles the details you provide when you create an account, verify your phone, enter the lobby or check a wallet status.

Clear data purposesWallet record contextDevice access detailsRequest change path
efek88 Open Your Privacy Policy Path
REQUEST HELP

Switch To A Clear Policy Contact Route

A direct support route helps when your Privacy Policy question concerns a phone check, wallet reference or device session. Sign in first when you can, then use the account support path so we can connect your request to the correct record. If login stalls, include the account detail you can safely provide without sending a password. We use the same route for questions about DANA, QRIS or a request to correct personal data.

Team online

Account support path

Use the support link inside your account for Privacy Policy questions. Tell us whether your request concerns phone verification, a login record or a stored account detail, and we can route it without asking for your password.

Wallet record query

For a DANA, OVO, GoPay or QRIS reference, share the transaction date and account identifier through support. Keep payment PINs and one-time codes private; our Privacy Policy does not require those secrets for a status check.

Device access check

If a new phone or browser creates an unfamiliar session, contact support from the account path and describe the device change. We can explain the relevant security record and guide a Privacy Policy request about that session.

DATA PRACTICES

Browse How efek88 Handles Policy Details

The practical parts of our Privacy Policy follow the account actions you take: opening an account, confirming your phone, signing in, checking wallet status and entering a selected lobby.

Account details

We use the details supplied during account opening and phone verification to create your account, protect sign-in and respond to account requests. Please keep them current so a Privacy Policy query can be matched to the right record.

Cookies and sessions

Cookies and related session signals can keep your login path working across a phone browser. They may also help us spot an unusual session. Our Privacy Policy describes their purpose, while your browser settings provide local control.

Wallet references

A DANA, OVO, GoPay or QRIS reference may be retained to connect a payment status with your account. We do not need your wallet PIN or one-time code for this policy-related matching process.

Security records

Login time, browser details and device signals can support account security when access changes. If a session looks unfamiliar, we use those records to investigate the event rather than asking you to disclose a password.

Retention timing

We retain personal data for the account purpose, security work, dispute handling or a legal requirement that applies. When a retention reason ends, our process considers deletion or anonymisation subject to those legal and operational limits.

Change requests

To request access, correction or an available deletion action, contact us through the account support path with the affected detail. We may verify account ownership before changing records, and we explain any limit under local law.

Ask Before You Open Your Account

These Privacy Policy answers focus on the searches we expect from an Indonesian account holder. They cover what efek88 collects, why wallet and device records appear, how to request a correction and what access wording means. Read them with the full policy, especially if your account uses DANA, QRIS or a bank transfer reference.

The efek88 Privacy Policy covers account details, phone verification, login and device records, cookies, wallet references and support requests. It explains why each category may be used, how retention works and where local law affects access, correction or deletion choices.

DANA and QRIS references can connect a payment status with your account without exposing your wallet PIN. The Privacy Policy explains that these references, along with OVO, GoPay, bank transfer or virtual account records, support reconciliation and account queries.

Yes. Use the account support path and identify the detail that needs correction, such as a phone record or account profile field. We may verify ownership first, then explain the available action and any restriction that depends on local law.

The Privacy Policy allows device and session signals to support sign-in security and investigate an unfamiliar browser or phone. These records can show that an access event changed, but they do not replace your password or require you to disclose it.

We keep account and wallet-related data for the stated account purpose, security work, dispute handling or a legal requirement. The Privacy Policy does not promise one fixed period for every record because retention can depend on the record and applicable law.

Where local law permits, you can ask what personal data is held about your account and request an available correction or deletion action. Send the request through support, describe the record involved and complete any ownership check we reasonably require.

Use the account support route and state that the request concerns login, phone verification or an unfamiliar device session. Do not send a password, wallet PIN or one-time code. We will use safe account details to identify the relevant record.