Reference

Open the obs188 Privacy Policy

The obs188 Privacy Policy explains what we collect, why we use it and how you can ask about your account data.

Account clarityWallet recordsCookie choicesContact route
obs188 Open the obs188 Privacy Policy
CONTACT THE TEAM

Check your Privacy Policy questions

A clear contact path helps when you want to understand a data entry, correct an account detail or ask why a verification record is needed.

Account support route Use the support path inside your signed-in account for Privacy Policy questions.
Payment record check For a DANA, OVO, GoPay or QRIS data question, share the visible transaction reference…
Correction request If your phone, email or account detail has changed, ask through the same account…
CONTROL YOUR RECORD

Browse our data handling steps

We keep the Privacy Policy practical: data is collected for account operation, security, payment reconciliation and support rather than displayed as a public identity.

Account creation

When you open an account, we use the details you submit to create your profile and connect your sign-in path.

Device signals

A desktop browser, Android phone or other supported device can send technical session details such as browser type, time and…

Cookie controls

Cookies can preserve a session and remember selected settings while you move between account pages.

Payment references

Our records may include a wallet or banking reference linked to DANA, OVO, GoPay, QRIS, BCA, BRI, Mandiri or BNI…

Security checks

We may compare sign-in patterns, phone verification and device events when an account action appears unusual.

Data changes

You can ask us to correct account details or explain how a record is used through support.

Find answers about Privacy Policy

These Privacy Policy answers address the questions we expect you to ask before creating an obs188 account. They cover account records, cookies, wallet references, device access and requests to change or remove data. If your situation is not covered, use the signed-in support route and describe the exact record or account step involved. We will use that context to direct your request.

It covers account details, phone verification, device and session signals, cookies, support messages and payment references connected with DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity. It also explains how we use, retain and protect those records.

Phone verification helps connect account access to the contact detail you provide and supports checks when an account change or unusual sign-in occurs. We may request verification before editing your profile so another person cannot change your records.

Yes. The policy covers payment references shown in your account when you use DANA, QRIS, OVO, GoPay, bank transfer or a virtual account. We use those references to match status and receipts, while your wallet PIN and security code should remain private.

Cookies can keep your session active and remember selected settings while you move through account pages. You can change cookie controls in your browser. Blocking necessary cookies may sign you out or require another account step before a request can continue.

You can request a correction through the support route inside your signed-in account. State which phone, email or profile detail is wrong. We may verify your identity first, then assess the request against retention duties and where local law permits.

We retain records for as long as needed for the purpose explained in the Privacy Policy, account security, payment reconciliation, dispute handling and legal duties where local law permits. The exact period can depend on the record type and applicable requirements.

Availability and eligibility depend on local law. If you are in Jakarta, Surabaya or another Indonesian location, check the access terms shown for your account and ask support about a Privacy Policy matter through the signed-in account route.