Reference

ome89 Privacy Policy And Your Account

ome89 Privacy Policy explains how we handle the details connected with your account, from phone verification and mobile browser access to activity around Dragon Tiger, Aviator, DANA and…

Account dataWallet recordsCookie choicesAccess requests
ome89 ome89 Privacy Policy And Your Account
PRIVACY HELP PATH

Get Help With Your Privacy Policy

A clear contact path matters when you want to ask about your Privacy Policy rights or the data attached to your ome89 account. Start with the support route available after login and state the phone number or account detail connected with your request. For wallet questions, include the DANA, OVO, GoPay or QRIS receipt reference without sharing a PIN. We use the details you provide to locate the correct record and respond to the request.

Team online

Account access

If you cannot reach the privacy page after phone verification, use the account support path shown on the login screen. Tell us which device and browser you used, so we can separate an access issue from a request about stored data.

Wallet records

For a Privacy Policy question involving DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity, send the receipt reference through account support. We can use that reference to identify the relevant transaction record without asking for your wallet PIN.

Data requests

To ask for access, correction or removal of eligible account data, describe the request clearly and use the contact path displayed within your account. We may ask for an account detail to confirm that the request comes from you.

DATA HANDLING

Inside ome89 Privacy Policy Controls

Our Privacy Policy follows the account journey rather than treating every visit the same way.

Account details

We handle details needed to create and maintain your account, such as your phone number and verification status. These details help us connect the correct person with account access and prevent a support request from being attached to the wrong profile.

Security checks

Login activity, device details and verification events may be used to identify unusual access. If you move from a mobile browser to desktop, these signals help us understand the account session without requiring you to send confidential wallet credentials.

Cookies

Cookies can remember practical choices, such as whether a privacy notice has been seen or which session is active. You can manage cookie behaviour through your browser settings, although changing those settings may affect sign-in and page access.

Payment references

DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity can create references linked to your account. We use those references to match status questions and receipts, not as a reason for you to share a payment PIN.

Retention choices

We keep account and transaction records only for the period needed for service operation, security, dispute handling and legal duties. When you ask about removal, we assess the request against any record that must remain under applicable law.

Policy changes

If this Privacy Policy changes, we will present the updated wording through the site or account access path. Check the page before opening a new session, especially when you use a different device or access where local law permits.

Privacy Policy Answers For ome89

These Privacy Policy answers address the searches we expect before an Indonesian account holder opens an account. They cover the data connected with phone verification, mobile access, game activity and local wallet records. If your question concerns a specific receipt or account change, use the support route after login and include only the reference needed to locate the record.

The ome89 Privacy Policy covers account details, phone verification, login and device signals, cookie choices, support messages, lobby activity and payment references. It also explains how we handle requests to access, correct or remove eligible data where local law permits.

Yes. Privacy Policy treatment includes references connected with DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity. We use those references to check account status or receipt questions, while you should never send a wallet PIN in a support message.

Phone verification connects account access with the correct account holder and supports security checks when you sign in. It can also help us locate the right profile when you ask about Privacy Policy, a mobile session or a wallet receipt.

Use the privacy or account support path shown after login and ask for access to your stored account data. Include the phone number or account detail linked to your profile. We may confirm your identity before responding, subject to local law.

You can request a correction through the account support path and explain which detail is inaccurate. For a wallet record, add the DANA, OVO, GoPay or QRIS receipt reference. We assess the request against account security and legal record duties.

On a mobile browser, cookies can remember consent choices and maintain an active session. Your browser settings control whether cookies are accepted. If you clear them, you may need to sign in again and confirm your Privacy Policy choices.

Send a data removal request through the contact path available within your account, with enough detail for us to identify the record. We assess deletion against security, dispute handling and legal duties, so some records may need to remain.