Reference

Privacy Policy for Your obat388 Account

obat388 keeps this Privacy Policy focused on the details you need before opening an account: what we collect, why we use it, and how you can ask about…

Account dataWallet recordsCookie choicesPhone verification
obat388 Privacy Policy for Your obat388 Account
CONTACT PATHS

Ask About Privacy From Your Account

A clear contact route matters when a phone check, wallet receipt, or data request needs attention. We ask you to use the support path shown after login and include the account phone number, approximate event time, and relevant payment reference. That lets us locate the correct record without asking you to send a password or full wallet credentials. You can also reach the policy link from the cashier path and our obat388 brand home.

Team online

Account request

For access, correction, or removal questions, send the request through the signed-in support path. We may ask you to complete phone verification before discussing account-linked data, so a private request is connected to the correct account.

Wallet status

If a DANA, OVO, GoPay, QRIS, bank transfer, or virtual account reference appears incorrectly, include the receipt code and time. We use those details to check the payment record without requesting your wallet PIN or password.

Policy questions

For a question about this Privacy Policy, quote the section or data type you mean. Our support route can explain the request steps, the identity check needed, and any account records that must remain available.

HANDLING PRACTICES

What This Privacy Policy Covers

We apply this policy to the account path, the mobile browser session, wallet status checks, and messages sent to support.

Collected account details

We can handle your phone number, verification result, login history, device identifiers, and account preferences.

Payment references

A wallet or bank transaction can produce a reference, amount, status, and time.

Cookies and sessions

Cookies and similar browser storage can keep a session active, remember a selected setting, and help us detect a broken…

Account security

Phone verification comes before account access, and session signals help us spot an unfamiliar device or repeated login issue.

Retention decisions

We keep account, security, and transaction records only as long as needed for the stated purpose, dispute handling, service records…

Requesting changes

You can ask us to access, correct, or remove personal details through the signed-in support route.

Privacy Policy Answers For Indonesia

These Privacy Policy answers address the searches we hear most often before account opening. They cover phone verification, mobile access, payment references, cookies, retention, and contact steps. If your question concerns a particular record from DANA, QRIS, Live Baccarat Diamond, or another account activity, include that detail through the support path so we can respond to the right account.

The obat388 Privacy Policy covers account details, phone verification, login and device signals, cookies, support messages, and payment references. It explains why we use those records, how we protect account access, how long records may remain, and how you can request access or correction.

We use your phone number to create an account link and complete the phone verification step before access. It also helps us check that a privacy request comes from the account holder. We do not need your wallet PIN or password for that process.

Yes. The Privacy Policy covers the payment reference, status, time, and account match returned during a DANA or QRIS step. We use that context to check a receipt or stalled status, while your wallet PIN and full authentication code should remain private.

When you use the mobile browser path from login to the lobby, we may receive device and session signals such as browser type, access time, and security events. These help us keep the session consistent and investigate unusual access without needing unrelated phone content.

Cookies can retain a session, remember a setting, or help identify a failed login. You can clear or restrict them in your phone or desktop browser. If you do, some account steps may repeat, but that browser choice does not send us your private device files.

Use the signed-in support path and describe the data request clearly, such as account details, a QRIS receipt reference, or a login event. We verify account ownership before responding, then explain the records available and any reason a change may be limited.

You can submit a removal request through the account support route. We first confirm ownership and check whether the data is still needed for security, a payment dispute, service records, or applicable obligations. We then explain what can be removed and what must remain temporarily.