Reference

omega89 Privacy Policy For Your Account

Your account details, wallet references and device signals receive clear treatment under the omega89 Privacy Policy.

Account dataWallet referencesCookie choicesPhone verification
omega89 omega89 Privacy Policy For Your Account
CONTACT PATHS

Get Help With Privacy Requests

A clear contact route helps when you want to ask about the Privacy Policy or the details linked to your account. Use the support link from your account area and include the phone or email attached to your profile, without sending a wallet PIN. We can then identify the request, check its status and explain any step needed before changing account records.

Team online

Account access

If phone verification or login blocks your request, tell us which device and browser you used. We can connect the access issue with the correct account record without asking for your wallet password.

Wallet references

For DANA, OVO, GoPay, QRIS or bank transfer questions, share the transaction reference rather than a PIN. This lets us check the account record while limiting sensitive payment details in the conversation.

Privacy changes

To request access, correction or deletion, use the account support path and describe the exact record involved. We may ask for phone verification before making a change to protect your account.

DATA PRACTICES

How omega89 Handles Your Account Data

We keep the Privacy Policy practical by connecting each data use to an account action you can recognise.

Data collection

We collect details needed for account creation, phone verification, login protection and payment matching. Your transaction record can show DANA, OVO, GoPay, QRIS, bank transfer or virtual account references.

Cookie controls

Cookies and similar browser signals can remember session status, support security and show whether a page loads correctly. You can manage browser permissions, though blocking some cookies may interrupt account access.

Account security

We use phone verification and login records to help identify unusual access. Never place a password, wallet PIN or full payment credential in a support message or privacy request.

Retention periods

We keep account, support and transaction references for the period needed for security, service administration or legal duties. When a record is no longer needed, we remove or de-identify it.

Request changes

You can ask us to view or correct eligible account details through support. Include the relevant phone or email and explain the requested change; we may verify ownership before responding.

Device pathway

Your mobile browser may send device type, browser version and session signals when moving from login to the lobby. These details help diagnose access without requiring an installed app.

Privacy Policy Answers For Your Account

These Privacy Policy answers address the searches we hear most often before an account is opened or a wallet is connected. We keep each response tied to an actual omega89 step, from phone verification and mobile access to a request about stored account details. If your case is different, use the support path with the smallest necessary set of details.

It covers account details, phone verification, login and device signals, cookies, support messages, transaction references and how we use, protect, retain or change those records.

No. We use payment status and transaction references for DANA, OVO, GoPay and QRIS matching. Do not send a wallet PIN, password or full payment credential to support.

Use the support link in your account area and ask for access to your stored details. Include the account phone or email, then complete any ownership check we request.

Yes, you may ask us to correct eligible account details through support. State which record is wrong and what it should say; phone verification may be required before editing.

Device type, browser version and session signals help protect login access, recognise unusual activity and diagnose a mobile path from phone verification to the lobby.

Retention depends on the record and the operational or legal reason for keeping it. Account, support and payment references are removed or de-identified when no longer needed.

You can request deletion through support where local law permits. We assess the request against records needed for security, payment reconciliation or legal duties and explain any exception.