Reference

Privacy Policy for sobat500 Account Access

The sobat500 Privacy Policy explains how we handle your account details, device signals and payment status when you use DANA, OVO, GoPay or QRIS.

Account dataWallet recordsCookie choicesPolicy requests
sobat500 Privacy Policy for sobat500 Account Access
HELP PATH

Get Privacy Help Through Your Account

Privacy questions should reach the same account path used for login and wallet checks, because that lets us confirm who is making the request before discussing…

Account support route Open the support path after login and state that your request concerns the Privacy…
Payment receipt check For DANA, OVO, GoPay, QRIS or bank transfer questions, include the visible reference and…
Access request If you cannot reach the account area, explain the access issue and the privacy…
DATA PRACTICE

Cookies, Devices and Wallet Records

We describe our handling in practical terms so your privacy choices match the way you use the service.

Data we receive

We may receive your phone number, verification details, login events, device information and selected account activity. Payment references from DANA, OVO, GoPay and QRIS help us identify transaction status without requesting unrelated wallet content.

Cookie controls

Cookies and similar device signals help remember session choices and protect sign-in activity. You can adjust browser settings, though changing them may require another login or affect how the policy page loads.

Account security

Before discussing private account details, we may check the signed-in session, phone verification status or other account signals. This reduces the chance that a third party receives your data through a support request.

Retention approach

We retain account, security and payment-status records for the period needed for their stated purpose, account protection and applicable legal duties. When a record is no longer needed, our handling follows the policy process.

Device access

Your mobile path and desktop path can create different technical records, such as browser type, session time and security events. These signals help us assess access without treating device data as your wallet password.

Change requests

Use the account support route to request access, correction or clarification about your personal data. Tell us which record concerns you, such as a phone detail, cookie choice or QRIS status reference.

Privacy Policy Questions for Indonesia

These Privacy Policy answers focus on the account actions you are most likely to take from Indonesia. We cover what may be collected, how wallet references are handled, what happens on mobile devices and where to send a request. If your case involves access or eligibility, the applicable position depends on local law and the details shown in your account.

It covers account details, phone verification, login events, device signals, cookies, game activity linked to your account and payment-status references from DANA, OVO, GoPay, QRIS, bank transfer or virtual account.

Phone verification helps connect the account to your access request and protects private details during support. We may use that status before discussing a correction, data copy or wallet reference.

Yes. The policy covers the payment reference and status needed to match QRIS, DANA, OVO or GoPay activity to your account. It does not give us permission to inspect unrelated wallet content.

Cookies and device signals can remember a session and support security checks. Your mobile browser may create different records from desktop access, and browser settings can remove or restrict those signals.

After login, use the account support route and name the specific request. You can ask about a copy, correction or clarification, and we may verify your account before responding.

We keep records for the stated purpose, account security and applicable legal duties. The period can differ by record type, such as login events, payment status or verification details.

Yes. Explain both the access problem and the Privacy Policy request through the available support path. We first separate identity and security checks from any discussion of stored personal data.