Reference

Open the apex88 Privacy Policy

Our Privacy Policy explains how apex88 collects, uses and protects details connected with your account, device and wallet activity.

Account dataWallet checksDevice accessPolicy requests
apex88 Open the apex88 Privacy Policy
REQUEST A RESPONSE

Contact us about your privacy request

A direct support route helps you ask what data we hold, why it is used or how to correct an account detail.

Policy questions Use our support chat to ask about the Privacy Policy, the data connected with your account or the reason we request phone verification before account access. Include your registered contact detail so we can route the question without asking you to post private records in a public channel.
Data corrections If your name, phone detail or wallet reference needs correction, describe the exact field and the account step where it appears. We may ask for an account check before editing it, and we will not ask you to send a wallet password or one-time security code through chat.
Access concerns Tell us if your account opens on one device but not another, or if a payment receipt appears under the wrong status. Share the time, device path and payment rail, such as QRIS or bank transfer, so our team can trace the relevant record.
DATA HANDLING DETAILS

Browse the controls behind this policy

Privacy depends on clear handling at each account stage, so we separate identity details, device signals and payment references rather than treating them as one record.

Account details

We may handle your contact details, phone verification result and account activity to create access and answer account requests. The account step matters because it connects the correct person with the correct record. We use these details for the purposes described in this Privacy Policy.

Wallet references

A DANA, OVO, GoPay or QRIS reference can appear in payment records when you request an account action. Bank transfer and virtual account references can also be retained for matching, status checks and dispute handling without asking us to store your wallet password.

Browser cookies

Cookies can keep your session active and help us recognise the browser path used to access the lobby. If you clear cookies, you may need to complete account access again. Browser settings let you control cookies, although some account functions may then need another check.

Device signals

We may record practical device signals such as browser type, operating system and access time to identify unusual sign-ins. These signals help us respond when your mobile browser and desktop browser show different access patterns, without treating a device signal as your identity by itself.

Retention timing

We retain account, payment and support records only as long as they serve the purpose explained in the policy or are needed for a related dispute and security check. You can ask why a particular record remains, and we will explain the applicable account or payment reason.

Policy changes

When we change this Privacy Policy, we place the updated wording on this page and identify the effective date. Your continued account access after an update may involve the revised terms, where local law permits. Ask support if you need help comparing a previous policy version.

Find answers about Privacy Policy

These answers focus on the questions you may have before opening an account or sending a privacy request. We keep the wording tied to actual account, device and payment steps, so you can decide what to ask us through support before using the service where local law permits.

The apex88 Privacy Policy covers account details, phone verification, browser cookies, device signals, support messages and payment references. It explains why we use each category, how we protect access and how you can ask about, correct or request changes to data connected with your account.

Phone verification helps connect account access with the person controlling the registered contact detail. We may use the result when you open an account, request a correction or ask about private records. We do not need your one-time security code in support chat.

Yes. The Privacy Policy covers payment references linked to DANA, OVO, GoPay and QRIS, as well as bank transfer and virtual account records. We use those references to match receipts, check status and investigate disputes, not to request your wallet password.

Contact our support chat and name the account field that is wrong, such as a phone detail or payment reference. We may request an account check before making a change. Describe the issue without sending passwords, one-time codes or full wallet credentials.

Cookies may keep your session active and help us understand the browser path used for account access on your phone. You can manage cookies in your browser settings. Clearing them can require another login or phone verification when you return to the account.

We keep data for the period needed for the purpose stated in the Privacy Policy, including account access, payment matching, security checks or a related dispute. You can ask support why a record remains and which account or payment purpose supports its retention.

You can ask support what account, device, cookie or payment data is connected with your profile and why it is used. We may verify your account before responding so private details are not disclosed to another person. Access remains where local law permits.