Reference

Privacy Policy for Your omset288 Account

Our Privacy Policy explains how we handle the details connected with your omset288 account, including phone verification, login activity and wallet records for DANA, OVO, GoPay and QRIS.

Account dataWallet recordsCookie choicesAccess requests
Explore the lobby Read FAQ
omset288 Privacy Policy for Your omset288 Account
CONTACT ROUTES

Reach Us About Privacy Requests

A clear contact path helps you ask about the Privacy Policy without explaining your concern repeatedly.

Account privacy Ask us which account details are held, why they are needed and how they relate to your phone verification step. We may ask you to confirm account ownership before discussing personal records, so a privacy request is not sent to the wrong person.
Wallet record help For a privacy question linked to DANA, OVO, GoPay or QRIS, provide the payment rail and the receipt reference visible in your account. We use that narrow context to check a status record without asking you to send a wallet PIN or secret credential.
Access assistance If you cannot reach the privacy contact path because login stalls, explain the device and browser route you used, such as Android Chrome or desktop web access. We can then direct the request through an account check while keeping the request tied to your identity.
HANDLING DETAILS

Six Practical Privacy Commitments

Privacy works best when the handling steps are easy to understand. We separate account access records from the content needed to answer a payment-status question, and we use security checks before making…

Account details

We may collect your phone number, verification result and account identifiers to create and protect access. Your account step begins with the details you submit, and we use those details to match a privacy request to the correct account rather than discussing it openly.

Device signals

When you move from login to the lobby on a mobile phone, we may record browser type, device signals, session time and security events. These records help us investigate an unfamiliar session without treating your phone model as a marketing profile.

Cookie controls

Cookies can retain session settings and help the site recognise a continuing login path. You can manage browser cookie controls on your device, although switching them off may require you to repeat account steps or may affect access to a page.

Payment references

Our records may include the rail selected for a transaction, such as QRIS, DANA, OVO, GoPay, bank transfer or virtual account, plus a status and reference. We do not need your wallet PIN to answer whether a receipt is linked to your account.

Security checks

Before we disclose account data or change a privacy preference, we may compare your request with the phone verification and login details already held. This step reduces the chance that another person can obtain records or alter your account contact route.

Retention choices

We retain account, security and payment-status records only for the period needed for the purpose explained in this policy or where a legal requirement applies. You can ask what remains, request correction and ask whether deletion or restricted handling is available.

Privacy Policy Questions About omset288

These answers address the privacy searches we receive most often from people considering an omset288 account in Indonesia. They explain the account data, device records, wallet references and contact steps connected with this Privacy Policy. If your situation is not covered, send a specific request through the available support path and we will assess it against the records involved and local requirements.

The omset288 Privacy Policy explains handling for account details, phone verification, login and device records, cookie settings, payment references and privacy requests. It also explains how we use those records for access, security and support, rather than describing unrelated lobby content.

We may collect the phone number and account identifiers you submit, together with verification status and security events linked to access. The exact record depends on the account step you complete. You can ask us to identify the personal data connected with your account.

Yes. The Privacy Policy covers payment-status records connected with DANA, OVO, GoPay and QRIS, as well as bank transfer and virtual account references. These may show a rail, amount status and receipt reference; we do not ask for your wallet PIN.

We may use browser, device and session signals to protect your account and investigate unusual access. For example, a mobile login followed by a desktop session can create security records. These signals support account protection and are not a request for private files on your device.

You can contact us through the available account support route and request correction of inaccurate personal data. Include the account phone number only when needed for ownership checks, then describe the field that needs attention. We will assess the request under this Privacy Policy and applicable local requirements.

We keep account, security and payment-status records for as long as they serve the purpose explained in this Privacy Policy or a legal requirement applies. Retention can differ by record type. You can ask what category remains and whether deletion or restricted handling can be considered.

The page is intended to explain our handling for supported Indonesia access, but service access and certain privacy rights depend on local law. Where local law permits, you can use the stated contact path to ask about access, correction, deletion or restricted handling.

Related Pages

omset288 Indonesia Tennis Grand Slam About Us Plinko Mobile Play omset288 Casino