Reference

ora78 Privacy Policy For Account Data

The ora78 Privacy Policy explains how we collect, use, protect, and retain information connected with your account, device, and wallet activity.

Clear data purposesWallet activity explainedAccount contact pathMobile access details
ora78 ora78 Privacy Policy For Account Data
CONTACT YOUR WAY

Privacy Help For Wallet And Login Issues

A direct support request gives you a practical route to ask about the Privacy Policy without explaining your concern in a public channel.

Account help Use the account support route when you need a copy of personal data, a…
Wallet questions For DANA, OVO, GoPay, or QRIS status concerns, include the receipt reference and date…
Security concern If a device sign-in looks unfamiliar, contact us through account help and state the…
DATA HANDLING

How ora78 Protects Your Account Records

We keep this policy practical by connecting each data practice to a real account action. Your personal details, wallet references, and device events are handled for access, transaction matching, security, and support.

Account details

We use details such as your contact information and phone verification result to maintain account access. Check your account fields carefully and ask support to correct an error.

Device signals

Sign-in time, device type, and related security signals can help us identify unusual access. These signals support account protection when you move from mobile login into the lobby.

Cookies

Cookies and similar browser storage can keep a session working and remember basic access settings. You can adjust browser controls, though some account steps may then need repeating.

Payment records

A DANA, OVO, GoPay, QRIS, bank transfer, or virtual account reference helps us match a transaction status. We do not ask you to disclose a wallet PIN.

Retention periods

We retain records only as long as needed for the stated account, security, support, or transaction purpose, including periods required by applicable legal duties.

Your requests

Ask for access, correction, deletion, or a restriction on certain processing through account support. We verify ownership first and explain any record that cannot be removed.

Privacy Policy Questions About ora78

These answers address the Privacy Policy searches we hear most often before an account is opened. They cover the records connected with your account, payment references, device access, and requests sent to support. If your situation is not listed, use the account contact path and describe the specific record or account step.

The Privacy Policy covers account details, phone verification, device and sign-in signals, support messages, cookies, and payment references linked to DANA, OVO, GoPay, QRIS, bank transfer, or virtual account activity.

We use the verification result to confirm an account access step and help protect the account from unusual sign-ins. You should never send your password or wallet PIN to support.

Yes. The Privacy Policy explains how we handle QRIS receipts and DANA, OVO, or GoPay status references when they are needed to match account activity or investigate a payment issue.

You can ask for a copy of personal data connected with your account through account support. We verify account ownership first, then identify which records can be supplied under applicable legal requirements.

Yes. Send support the field that needs correction and the account context, without sharing a password. We may request phone verification or another ownership check before changing personal details.

Retention depends on the purpose and applicable legal duties. We keep account, security, support, or transaction records for the period needed for that purpose, then assess whether continued storage is necessary.

Use account support and mention the device path, approximate sign-in time, and affected account. We can check the security record after ownership verification and explain the next available account-protection step.