Reference

Open the o777 Privacy Policy Clearly

o777 Privacy Policy explains how we collect, use and protect the details connected with your account, wallet status and device access.

Account detailsWallet recordsDevice accessCookie choices
o777 Open the o777 Privacy Policy Clearly
ASK OUR TEAM

Contact Us About Privacy Requests

A clear contact path helps you act on the Privacy Policy instead of searching through account screens.

Account request Use our account support path when you want to ask about stored contact details…
Wallet record For a DANA, OVO, GoPay or QRIS receipt question, describe the transaction status and…
Cookie choice If a cookie or device setting is unclear, contact us with the browser or…
DATA PRACTICE

Switch Through Our Privacy Controls

We handle Privacy Policy requests through the same account path used for phone verification and wallet status checks, so we can separate your record from another account.

Account details

We use the contact and verification details you provide to create, identify and protect your account. Before changing a phone number or another important field, we may ask for an account step that confirms you control the record. This reduces the chance of an unauthorised change.

Payment matching

DANA, OVO, GoPay, QRIS, bank transfer and virtual account references help us connect a payment event with the correct account. We do not need your wallet PIN for that purpose. Receipt and status records support reconciliation, dispute handling and a clear response to your data request.

Device signals

When you move from phone login to the lobby, we may process device and session signals that help protect account access. These signals can include technical browser details and session timing. They are used for security and service operation, not as a reason to ask for your private wallet secret.

Cookie settings

Cookies can remember a session choice or help the account path work as intended on your browser. You can manage available browser settings, and you can ask us what a cookie does before changing it. Removing a required cookie may mean that a fresh login or verification step appears.

Retention choices

We keep account, payment and support records for the period needed to operate the account, resolve a receipt issue, prevent misuse or meet a legal requirement. When a record is no longer needed for those purposes, our handling follows the retention process described in the Privacy Policy.

Change request

You can ask us to correct account data, explain its use or clarify whether a record is still needed. Send the request through the account support path with a precise description. We confirm the relevant account context before making a change and explain any restriction tied to law or payment records.

Browse Privacy Policy Answers

These Privacy Policy questions address the account and payment details you are most likely to check before opening access. Each answer stays tied to our actual handling path: phone verification, device sessions, cookies, local wallet references and requests for correction. If your question concerns eligibility, access depends on local law, and our support response will keep that point explicit.

The o777 Privacy Policy covers account details, phone verification, device and session signals, cookies, payment references and support records. It explains why we use each category, how we protect account access, how long records may remain needed, and how you can ask about correction or use.

Phone verification helps us identify the account holder before access and before important account changes. We use it as an account-security step, not as a request for your DANA, OVO or GoPay PIN. If verification fails, contact support and describe the step that stopped you.

Yes. The Privacy Policy covers QRIS, DANA, OVO, GoPay, bank transfer and virtual account references when they are connected with an account transaction. We use those references to match payment status, check receipts and handle disputes, without asking you to disclose a wallet PIN.

We may process technical device and session details when you move through login and account access, such as browser characteristics and session timing. These details help identify unusual access and protect your account. Ask support if you want a clearer explanation of a device record linked to your account.

Cookies can store session choices and support selected account functions on your browser. You can manage available cookie settings through your browser and ask us what a cookie supports. If you remove a required cookie, the next account path may request a fresh login or phone verification.

You can ask us to correct an account detail or explain how a record is used. Use the account support path, identify the specific field or record, and provide your account identifier. We confirm the account context first and explain any limit caused by legal, security or payment duties.

We retain records while they are needed for account operation, payment matching, receipt disputes, security checks or legal requirements described in the Privacy Policy. Retention is not a promise of a fixed period for every record. Ask support about the category involved and we will explain the applicable handling.