Reference

obat99 Privacy Policy For Your Account

Live Baccarat Grand, Merapi Fire Slots and QRIS account steps are handled with your privacy in mind.

Clear data purposesWallet status contextMobile access details
obat99 obat99 Privacy Policy For Your Account
CONTACT ROUTES

Privacy Help For Wallet And Login Issues

A clear contact path matters when a privacy question appears beside a login or wallet status. We ask you to use the account support route shown after sign-in, or the contact form linked from the site, so we can match your request with the right account record. Include the issue, approximate time and relevant payment reference, but do not send a full password or wallet PIN. We use the details you provide only to assess the request and respond.

Team online

Account access request

If you cannot reach your account after phone verification, use the account help route and state that your request concerns the Privacy Policy. We may ask for account identifiers to confirm ownership before discussing stored details or changing an access record.

Wallet data question

For DANA, OVO, GoPay or QRIS references, send the payment date, amount reference and account identifier through our contact form. We do not need your wallet PIN, full credential or private security code to review a status question.

Correction request

To ask us to correct an account detail, describe the field that needs attention and provide a safe way to reach you through the account route. We check the request against our records before applying a change or explaining why a record must remain.

DATA PRACTICES

Cookies, Devices And Account Records

Privacy choices work best when you know what happens during an ordinary session. When you open the mobile lobby, our systems may read device and browser signals needed for sign-in, session continuity…

Account data

We may keep your account name, phone verification state, login history and support correspondence so we can operate access and answer a Privacy Policy request. We use these records for account administration, security checks and service communication connected with your account.

Device signals

A mobile browser may provide device type, browser version, session time and security signals. These details help us recognise a returning login and investigate unusual access. They are handled as account-security data rather than as a substitute for your identity.

Cookies

Cookies can remember sign-in state, language choices and privacy preferences during a session. You can adjust cookie controls in your browser, although removing necessary cookies may require you to sign in again or reset a saved setting.

Payment references

DANA, OVO, GoPay, QRIS, BCA, BRI, Mandiri and BNI references may appear in account records when you check a payment status. We use the reference and status details to match activity, not to request your wallet PIN or full banking password.

Retention period

We retain records only for as long as needed for the purpose collected, account security, dispute handling or a legal requirement. When a record is no longer needed, our process removes it, de-identifies it or restricts further use.

Policy contact

You can ask about access, correction or deletion through the account support route or contact form. We may verify ownership before responding, because sending account data to an unverified requester could expose your login, wallet reference or support history.

Privacy Policy Answers For obat99

These Privacy Policy answers cover the questions we expect before you open an account or connect a local payment route. They explain the data linked to an obat99 session, how to request changes, what happens on mobile, and why identity checks may be needed. If your question is not listed, use the account support path with only the details needed to locate your record.

The Privacy Policy covers data connected with your account, phone verification, login sessions, mobile browser, cookies, support messages and payment references. It applies when you browse titles such as Live Baccarat Grand or check DANA, OVO, GoPay, QRIS, bank transfer or virtual account status.

We may collect account identifiers, phone verification details, login and device signals, cookie preferences, support correspondence and payment references. We use this information to provide account access, check security events, answer your request and match a payment status without asking for a wallet PIN.

Send an access request through the signed-in account support route or the contact form linked on the site. Mention that it concerns the Privacy Policy and identify the account safely. We may confirm ownership before sharing records, so private account data reaches the correct person.

Yes. Tell us which account field is incorrect and provide the matching account identifier through the support route. We review the request against our records, may ask for phone verification, and then correct the data where appropriate or explain why a record must remain unchanged.

Cookies can keep your session, language selection and privacy choice available while you move from login to the lobby. Browser controls let you remove or restrict them. Necessary cookie changes may sign you out or require a new preference selection on your next visit.

We use DANA, OVO, GoPay and QRIS references to connect a payment status with the correct account and investigate a support request. We do not need your wallet PIN or full banking password. Bank transfer and virtual account references may be handled for the same matching purpose.

You can ask about deletion through the account support route or contact form. We assess which records can be removed, de-identified or restricted after checking account ownership. Some information may remain for security, dispute handling or a legal requirement, and access depends on local law.