Reference

radar138 Privacy Policy for Indonesia Accounts

Our radar138 Privacy Policy explains what we collect when you open an account, use DANA or QRIS, and contact support about wallet status.

Account dataWallet recordsCookie choicesSupport requests
radar138 radar138 Privacy Policy for Indonesia Accounts
CONTACT ROUTES

Three Ways To Ask About Privacy

A clear contact route helps you resolve a privacy question without exposing extra account details.

Account support path Open the support area after login to ask about stored account details, a correction…
Payment status check For DANA, OVO, GoPay, QRIS, or bank transfer questions, include the receipt reference and…
Access assistance If login or phone verification stalls, use the account help route shown on the…
DATA PRACTICE

Six Data Controls Inside radar138

We handle this policy area through practical account controls rather than broad promises. Your sign-in, verification, wallet reference, device, and support records are considered in context, with access…

Collection

We collect details you provide during account opening, including your phone number and verification response, plus activity records needed to…

Device signals

Browser and device details can help us recognise unusual sign-in behaviour.

Cookies

Cookies or browser storage may keep a session active, remember a security preference, or support account navigation.

Account security

Phone verification and sign-in checks help connect the account to the right person.

Retention

We retain records only as long as needed for the stated account, payment, security, support, or legal purpose.

Your request

Use the support path in your account to request access, correction, or deletion of eligible data.

Privacy Policy Questions Answered

These answers address the searches we hear most often about the radar138 Privacy Policy. They cover account creation, Indonesian wallet records, cookies, device access, and requests for changes. If your situation involves a specific receipt or verification event, use the support path inside your account so we can check the relevant record without asking you to share secret credentials.

It covers account details, phone verification, login and device records, lobby activity linked to your account, payment references, cookies, support messages, retention, and requests to access or change eligible data.

Yes. We may receive payment references and status details connected with DANA, OVO, GoPay, QRIS, bank transfer, or a virtual account. The payment provider may apply separate privacy terms.

Phone verification helps connect account access to the correct person and supports security checks when login behaviour changes. We use the result for account operations and do not need your one-time code in support messages.

You can ask through the support path inside your account. State that you want an account-data request and provide your account reference; we will assess the request under applicable law and available records.

Send the correction request through account support, identify the field or record, and explain the accurate replacement. For payment data, add the receipt reference, but leave out passwords and one-time codes.

Cookies or similar browser storage can support a login session, security preference, or account navigation. Clearing them may sign you out or change the mobile path, after which you can sign in again.

We assess deletion requests individually. Some account, payment, security, or legal records may need to remain for a defined operational reason where local law permits; support can explain the outcome.