Reference

Privacy Policy For Your apex55 Account

Our Privacy Policy explains what we collect when you open an apex55 account, move through the lobby, or check DANA, OVO, GoPay and QRIS status.

Clear data purposesWallet records explainedCookie choices availableContact path included
apex55 Privacy Policy For Your apex55 Account
HELP WITH PRIVACY

Get Clear Answers About Your Data

A direct support route helps you ask what the Privacy Policy means for your own account.

Account data request Ask us which account details we hold and why they are used.
Wallet record check If a DANA, OVO, GoPay or QRIS reference looks unfamiliar, send the receipt number…
Cookie choice help Tell us if you need help changing browser storage or cookie preferences on mobile.
DATA CARE DETAILS

Privacy Controls You Can Use

We keep this Privacy Policy practical by connecting each data use to an account action you can recognise.

Collection purpose

We collect account details to create and maintain your profile, complete phone verification and answer requests tied to your activity. We do not need your password in a support message, and we ask you to keep secret credentials out of every privacy request.

Cookie settings

Cookies and similar browser storage can preserve selected preferences and help a session continue between pages. You can adjust browser controls on your phone or desktop, although removing required storage may interrupt sign-in or make the account path ask for verification again.

Account security

We use phone verification, session signals and unusual-activity checks to help protect your profile. If you switch devices before opening FAQ Mobile Help or Aviator Fast Round, a fresh check may appear because device behaviour is part of the security assessment.

Payment references

A deposit or withdrawal record may include a rail name, receipt reference, amount and status needed for matching. For bank transfer and virtual account questions, send only the relevant reference and date so support can investigate without receiving private banking login details.

Retention period

We retain records for as long as they serve account operation, dispute handling, security checks or a legal requirement. When a record no longer has a valid purpose, we remove it or separate it from direct account identifiers where that process is suitable.

Change or removal

You can ask us to correct inaccurate personal details or request removal of data through the site support route. We first confirm that the request comes from the account owner, then explain what can change and what must remain for a stated operational or legal reason.

Privacy Policy Answers For apex55

These Privacy Policy answers address the searches we hear most often from people deciding whether to open an account. Each response points to a practical action, from checking stored details to asking about wallet records or changing browser settings. If your situation is not covered, contact support with the account identifier you can safely share; access remains subject to local law.

The apex55 Privacy Policy covers account details, phone verification, session and device signals, cookies, support messages and payment references. It explains why we use each category, how we protect it, how long we may retain it and how you can ask about correction or removal.

Phone verification helps us confirm account ownership and respond safely when you contact support. It can also appear after a device change or unusual session. We use the check for identity and account protection, not as a reason to request your password or wallet PIN.

Yes. The Privacy Policy covers payment references connected with DANA, OVO, GoPay and QRIS, including a receipt reference, rail name, date and status when needed for matching. We do not ask you to send wallet passwords, PINs or full banking login details.

Use the support route displayed on the apex55 site and state that you want a copy of your account data. Include the linked phone or email detail, but omit secret credentials. We may complete an identity check before confirming which records can be provided.

You can request a correction when your personal details are inaccurate or outdated. Send the affected field and the correct value through support. We confirm account ownership first, then update eligible records or explain why a particular record must remain unchanged.

Cookies can keep selected preferences and support a continuous browser session on mobile or desktop. You can change them through your browser settings. Removing required storage may interrupt sign-in, reset preferences or trigger phone verification when you return to the account.

We keep personal data while it is needed for account operation, payment matching, support, security checks, disputes or a legal requirement. After that purpose ends, we remove it or separate it from direct identifiers where suitable. The exact route depends on local law.