Reference

orion88 Privacy Policy for Indonesia Accounts

The orion88 Privacy Policy explains what we collect when you open an account, sign in from a phone, or check DANA and QRIS status.

Account dataCookie choicesPolicy requestsIndonesia access
orion88 orion88 Privacy Policy for Indonesia Accounts
HELP WITH PRIVACY

Get Privacy Policy Help Near Cashier

A clear contact route matters when your account record or payment reference needs attention.

Account access If phone verification or sign-in details look wrong, tell us which account step stopped and identify the device type. We use that context to locate the relevant record without asking for your password.
Payment records For DANA, OVO, GoPay, QRIS, bank transfer or virtual account questions, send the reference and date through account support. We can then check the payment record against the privacy request.
Policy changes To ask about correction, deletion or a copy of your personal data, contact us from the signed-in account path. We may request verification before changing or disclosing account records.
OUR DATA PRACTICE

How orion88 Handles Your Account Data

We keep this Privacy Policy practical: it describes why a record exists, who may receive it and when it can be removed.

Collection

We collect account details when you open an account, complete phone verification or contact support. Device and sign-in details are added when needed to keep access records accurate and investigate unusual activity.

Cookies

Cookies can remember your selected settings and help connect a sign-in session with the correct account. You can manage browser cookie controls, although some account functions may then require another sign-in.

Account security

Phone verification comes before account access, while sign-in and device signals help us check suspicious changes. Never send a password or full wallet credential when asking about your personal data.

Payment matching

A DANA, OVO, GoPay, QRIS, bank transfer or virtual account reference helps us match a cashier event. We use the reference for status checks and do not need your wallet password.

Retention

We retain records for the period needed to provide account support, resolve a payment question, protect access or meet a valid legal requirement. The applicable purpose determines when removal can occur.

Your request

You can ask for access, correction or removal of eligible personal data through signed-in account support. We verify the request first, explain any limit, and record the outcome against your account.

Privacy Policy Answers for Indonesian Accounts

These Privacy Policy answers address the searches we hear most often before account creation or a data request. They explain what to send, how payment references are handled and what happens when access depends on local law. If your case is unusual, use the signed-in support path so we can check the account record directly.

The orion88 Privacy Policy covers account details, phone verification, device and sign-in records, cookies, support messages, payment references and the purposes, sharing conditions and retention periods connected with those records.

We may collect the details you provide during account creation, phone verification and support contact, plus device and sign-in events. Payment references from DANA, OVO, GoPay or QRIS may also be recorded.

We use DANA and QRIS references to match a payment request, check its status and resolve account support. We do not need your wallet password, and you should not include it in a message.

Yes. Send a correction request through signed-in account support, describe the record and explain the change needed. We verify that you control the account before updating information or explaining why a limit applies.

Use the account support path to request removal of eligible data. We first confirm your identity, check whether the record is still needed for security, payment resolution or a legal requirement, then explain the result.

Retention depends on why the record was created. We may keep account, security or payment references while support, access protection or a valid legal requirement needs them, then assess removal under the policy.

Yes. Account and data-request access depends on local law. Where local law permits, you can read the policy and submit a request through signed-in support; we will explain any regional restriction.