Reference

Open your orion88 Privacy Policy

orion88 Privacy Policy shows how we collect, use and protect the details connected with your account, device and wallet activity.

Clear data purposesWallet record contextMobile access notesAccount request path
orion88 Open your orion88 Privacy Policy
HELP WITH REQUESTS

Find policy help beside your account

A clear support path matters when you want to ask about a record, correct an account detail or understand a wallet reference. Start from the support route shown after you sign in, include the account phone number and describe the Privacy Policy request. We may ask for a payment receipt or verification detail, but never ask you to send a wallet password. Your request is handled through the account support path.

Team online

ACCOUNT QUESTIONS

If your phone verification or account detail needs correction, send the request through the signed-in support path. We use the account information you provide to locate the right record and may ask you to confirm ownership before making a change.

WALLET RECORDS

For DANA, OVO, GoPay or QRIS receipt questions, include the payment reference and date shown in your record. We use those details to trace status while keeping wallet passwords, PINs and unrelated transaction content outside the request.

DATA REQUESTS

You can ask what personal details we hold, request a correction or ask how retention applies to your account. Use the policy contact route, describe the request plainly and keep the reply connected to your verified account.

CONTROL YOUR DETAILS

Explore the controls behind your data

Our handling process separates account identity, payment references and device signals so each detail has a defined purpose.

DATA PURPOSES

We collect only the details needed to create and maintain your account, confirm phone ownership, answer support requests and connect payment references with the correct transaction. The Privacy Policy explains the reason for each category instead of grouping everything together.

COOKIE CONTROLS

Cookies and similar browser signals can remember session settings and help us understand whether a sign-in request matches your device. You can review browser controls on your mobile or desktop path, while account security checks may still remain active.

ACCOUNT SECURITY

Phone verification is part of account access, and unusual device behaviour may lead to an extra confirmation step. We do not ask you to disclose a wallet PIN or password through a policy request, support message or payment receipt.

RETENTION RULES

Some records remain while your account, payment reconciliation or a legal request requires them. When a record no longer has a stated purpose, our handling follows the retention approach described in the Privacy Policy and applicable local requirements.

CORRECTION ROUTE

If your phone number, contact detail or account record is inaccurate, use the signed-in request path and identify the field to be corrected. We may verify ownership first, then update the record or explain why a particular entry must remain.

CONTACT METHOD

Questions about collection, cookies, retention or payment references should go through the support contact shown in your account area. Include a short description and relevant reference number, but remove wallet passwords and unrelated private material.

Ask about the orion88 Privacy Policy

These Privacy Policy answers address the account and payment questions you are most likely to have before opening an account. We keep the route practical: read the policy page, use the signed-in support path for a personal request and avoid sending passwords or wallet PINs in any message.

The orion88 Privacy Policy covers account details, phone verification, device and browser signals, cookies, support records, payment references and retention. It also explains how you can request access, correction or clarification through the account support route.

We use your phone number for account identification and phone verification before account access. It can also help us match a support request to your record. We will not need your DANA, OVO, GoPay or QRIS wallet password.

We may retain references such as a receipt number, amount, date or status for DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity. These references help trace a transaction without requiring your wallet PIN or unrelated wallet history.

You can ask what personal details are connected with your account by using the support contact shown after sign-in. Include your account phone number and request scope. We may verify ownership before discussing or supplying records, where local law permits.

Send a correction request through the signed-in account path and name the field that is wrong, such as a phone or contact detail. We may ask for a verification step, then update the record or explain any legal reason it must remain.

Cookies may support session continuity, browser settings and security checks when you use a mobile browser. Your browser provides controls for cookie storage. Turning some cookies off can affect sign-in or policy-page access, while security checks may still apply.

Retention depends on the purpose of the record, including account support, payment reconciliation, security checks or legal handling. The Privacy Policy describes this approach, and any access or deletion request depends on local law and the applicable record requirement.