Reference

Privacy Policy For Your obat89 Account

Our Privacy Policy explains what we collect when you open an obat89 account, use phone verification, browse the lobby, or check DANA and QRIS status.

Clear data purposesAccount access safeguardsYour request optionsDANA and QRIS context
obat89 Privacy Policy For Your obat89 Account
REQUEST HELP SAFELY

Get Privacy Help Near Account Access

A clear contact route helps you ask about personal data without sending sensitive wallet credentials.

Account data request Ask us to identify the personal data linked with your account, including contact details…
Wallet status question If a DANA, OVO, GoPay, QRIS, bank transfer, or virtual account reference looks incorrect…
Correction or deletion Tell us which detail needs correction or which eligible record you want removed.
HOW WE HANDLE DATA

Practical Controls Behind This Privacy Policy

Our handling process follows the same account steps you see on the site: create an account, complete the requested phone check, sign in, and then use the lobby or cashier path.

Data collected

We may receive your name or contact detail, phone verification result, account activity, device information, cookie settings, support messages, and payment references. The exact fields depend on the action you take and the data needed to keep that action connected to your account.

Cookies and sessions

Necessary cookies can keep your sign-in state, language choice, and security session working as you move from the lobby to account pages. You can manage browser cookie settings, although removing required cookies may interrupt account access or request processing.

Account security

Phone verification is used before account access where required, and login or device signals can help us detect unusual activity. We do not ask for your DANA PIN, OVO password, GoPay code, or QRIS secret as part of a normal support request.

Payment references

For DANA, OVO, GoPay, QRIS, bank transfer, and virtual account activity, we may store a reference, amount status, timestamp, and account match result. These details let us investigate a cashier question without storing your external wallet login credentials.

Retention approach

We keep personal data only for the period needed for account operation, security checks, support history, dispute handling, or legal obligations. When a retention reason ends, we delete, anonymise, or restrict the relevant record where our process allows it.

Your contact route

You can ask about access, correction, deletion, processing purpose, or cookie choices through the available obat89 support route. Include your account identifier and a short description, but remove wallet passwords, PINs, security codes, and unrelated personal documents.

Privacy Policy Answers For Indonesian Accounts

These answers cover the questions we expect you to ask before opening an account or connecting a local wallet. They focus on the Privacy Policy rather than game selection, so you can understand data use before moving from phone verification to the account area. If your situation is not listed, contact us through the available support route and describe the specific record or request.

The Privacy Policy covers data collected during account creation, phone verification, login, cashier requests, cookie use, device checks, and support contact. It also explains retention, security handling, your request options, and the payment references used for DANA, OVO, GoPay, QRIS, bank transfer, and virtual account activity.

Phone verification helps connect account access to the correct contact detail and can support security checks when you sign in. We record the verification result and related account event, not your private wallet password. Access or eligibility depends on local law and the checks required for your account.

Yes. The Privacy Policy covers payment references connected with DANA and QRIS, along with OVO, GoPay, bank transfer, and virtual account requests. We may use a reference, status, timestamp, and account match result to resolve a cashier question, while your wallet PIN remains outside our normal request.

You can contact us through the available support route and ask what personal data is linked to your account. Include your account identifier and describe the records you want to access. We may verify ownership first, and some security, dispute, or legal records may require restricted handling.

Send a correction request through the available support route and identify the detail that is inaccurate, such as a contact record or account profile field. We may ask for an account step that confirms ownership. We will explain if a record cannot be changed because retention or security rules apply.

Retention depends on why the data was collected. We may keep account, login, payment-reference, and support records for account operation, security checks, disputes, or legal duties. When the reason ends, our process may delete, anonymise, or restrict the record, subject to applicable requirements.

Yes. Necessary cookies can preserve a sign-in session, language setting, or security state as you move between the lobby, account area, and cashier path. Browser controls can limit cookies, but removing required cookies may affect access. The available cookie choices are shown where those settings apply.