Reference

Open the obs188 Privacy Policy

The obs188 Privacy Policy explains what we collect when you open an account, check phone access, browse Live Baccarat Royal or use DANA, OVO, GoPay and QRIS.

Clear data purposesWallet activity explainedAccount contact pathCookie choices
obs188 Open the obs188 Privacy Policy
CONTACT OPTIONS

Ask About Privacy Through Your Account

Privacy questions should reach us through the account support route, where we can connect your request with the correct sign-in and wallet record. Tell us whether your question concerns a phone check, a cookie, a DANA receipt, a QRIS status or another account detail. We may ask for enough account context to identify the record, but do not send a password or full payment credentials. Our support path is designed to keep privacy requests separate from general lobby activity.

Team online

Account support route

Use the support path connected to your obs188 account when you need to ask about stored details, a phone verification record or a sign-in session. We can then match the request to the right account without asking you to post private details in a public channel.

Wallet receipt check

If your privacy question involves DANA, OVO, GoPay or QRIS, include the payment reference visible in your account rather than a wallet password. We use that reference to locate the status record and explain what was retained for the account service.

Access assistance

When a phone check or device session blocks your policy request, tell us the sign-in step that stopped. We can explain the next account action, while access remains subject to local law and we avoid requesting unnecessary identity details.

DATA PRACTICES

Understand Cookies, Sessions and Retention

We handle privacy through practical account controls rather than broad promises. A phone verification step helps connect access to the right account, while session records help us spot a sign-in that does…

Account data

We may hold the phone number, account identifier and access details you provide while opening or using an account. These records help us return you to the correct account and answer a specific request about access, rather than creating a separate profile for every visit.

Payment records

A DANA, OVO, GoPay, QRIS, bank transfer or virtual account action can create a reference, amount status and related account event. We retain the details needed to reconcile that event and handle a question, while wallet passwords remain outside our requested support details.

Cookies

Cookies can remember an active browser session and help the account path move between login, lobby pages and wallet status. You can adjust them in your browser settings. Blocking required cookies may sign you out or prevent a requested account page from loading.

Device sessions

We record limited session signals so we can investigate an unexpected sign-in or a stalled phone verification step. On a shared phone, sign out after use and clear the browser session. Contact us if a device record looks unfamiliar or no longer belongs to you.

Retention

We keep account, payment and support records only while they serve account operation, security, dispute handling or a legal requirement. The period can differ by record type. Ask through account support which category applies and whether a deletion or restriction request can be considered.

Change requests

You can ask us to correct an account detail, explain a stored record or consider a removal request where local law permits. Include the account phone contact and the exact field or event concerned. We may verify ownership before making a change to protect your account.

Find Privacy Policy Answers Before Access

These Privacy Policy answers cover the questions we expect before an account is opened or a wallet is connected. They explain the practical path for Indonesian account holders, including phone verification, cookies, payment references, device sessions and requests to change stored details. If your situation is not listed, use the account support route and describe the exact record or access step you want us to check.

The obs188 Privacy Policy covers account details, phone verification, sign-in and device session records, cookies, support messages and payment references linked to DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity. It also explains retention, correction requests and contact steps.

We use your phone number to support the account opening and verification path, connect you with the correct account and investigate access problems. A phone check may be required before account access. We do not ask you to send your password through support.

Yes. The Privacy Policy covers account-linked references created when you use DANA, OVO, GoPay, QRIS, bank transfer or a virtual account. We use those references to match payment status, answer receipt questions and handle disputes connected with your account.

Cookies can keep a browser session active and help the path from login to the lobby or wallet status load correctly. You can change cookie settings in your browser. If required cookies are blocked, you may be signed out or unable to complete an account action.

You can contact account support to request a correction, ask what record we hold or ask whether removal is possible where local law permits. State the account contact and the exact field concerned. We may verify account ownership before changing any personal data.

Retention depends on the type of record and its purpose. We may keep account, payment and support details for account operation, security, dispute handling or a legal requirement. Ask support about the category linked to your request and whether a restriction or removal request applies.

Use the support route connected to your account and describe the Privacy Policy issue clearly, such as a cookie, phone check, device session or QRIS receipt. Do not include a password or full wallet credentials. Access and any request outcome depend on local law.