Reference

Open your radar138 Privacy Policy account path

Your radar138 Privacy Policy explains what we collect when you create an account, verify your phone, sign in from a mobile device, or use DANA and QRIS details…

Clear data purposesWallet detail controlsAccount access requestsCookie choices

Explore Our Lobby Read FAQ

Switch through privacy details for DANA and QRIS

radar138 Service availability depends on jurisdiction. Users are responsible for checking local law before access.

Our Privacy Policy sets out the data needed to create and protect your account, including your contact details, phone verification result, sign-in records, device signals, and transaction references. When you use DANA, OVO, GoPay, QRIS, bank transfer, or a virtual account, we may receive payment status

1
and reference data needed to match your account activity; we do not describe those rails as a request for your wallet password. Cookies and similar device data help retain session settings and detect unusual access. We use records for account support, payment reconciliation, security checks, and
2
legal obligations where local law permits. Eligibility and access depends on local law. The policy applies to your use of radar138 pages and related account contact routes, and its wording may be updated when our data practices change.

Service availability depends on jurisdiction. Users are responsible for checking local law before access.

ASK ABOUT PRIVACY

Browse support routes for policy requests

A clear contact route matters when your Privacy Policy question concerns a phone check, wallet reference, cookie choice, or account record. We keep policy assistance close to the account support path so you can explain the issue without posting private details in a public channel. Contact us through the support channel shown on radar138, include your account identifier and the request type, and we will use the details to locate the right record. Access remains where local law permits.

Team online

Account privacy help

Send a request through our account support channel when you want to ask about data held after phone verification. Include the contact detail linked to your account, but do not send a wallet password or full payment credential.

Wallet record check

For DANA, OVO, GoPay, QRIS, bank transfer, or virtual account references, describe the date and status shown in your account. We can investigate the matching record while keeping sensitive wallet credentials out of the conversation.

Cookie access request

If a cookie or device signal affects your sign-in, tell us the device type, browser path, and account contact. We can explain the relevant purpose and route your request for access, correction, or removal where local law permits.

HOW RECORDS MOVE

Explore how radar138 handles account privacy

Privacy is handled through practical account controls rather than broad promises. We separate the details needed for sign-in and phone verification from payment references used to match DANA, QRIS, or bank transfer…

Data collection

We collect details you submit for account creation and phone verification, along with sign-in time, device signals, and support messages. Our Privacy Policy connects each category to a stated account, security, payment, or legal purpose.

Cookie handling

Cookies can retain session preferences and help us recognise unusual access across a mobile browser or desktop browser. Your Privacy Policy rights include asking what cookie-related data is used and how a relevant choice can be changed.

Account security

Phone verification helps connect account access to the contact detail you provide. We may check device and sign-in signals when access looks unusual, and our support team will not ask you to reveal a wallet password.

Payment references

DANA, OVO, GoPay, QRIS, bank transfer, and virtual account activity may create references or status records. We use those details to reconcile account activity and investigate a receipt without treating them as your private wallet credential.

Retention choices

We retain account, security, support, and transaction records for the periods needed for their stated purposes or applicable legal duties. You can ask which category is held, why it remains, and whether a deletion request can proceed.

Request changes

To request access, correction, or another Privacy Policy action, contact support with your account identifier and a precise request. We may verify ownership before responding, and the available action depends on local law.

Check common radar138 Privacy Policy answers

These Privacy Policy questions cover the account steps and local payment records you are most likely to ask about before opening an account. Each answer stays focused on data handling, access, security, retention, and contact. When a right or restriction varies by location, the applicable position depends on local law.

The radar138 Privacy Policy covers account creation, phone verification, sign-in records, device signals, cookies, support messages, and payment references. It explains why we use each category, how we protect access, how retention works, and how you can request access or correction where local law permits.

When you open an account, we collect the contact details you submit and the result of the required phone verification step. We may also record sign-in time, browser or device signals, and support contact details so we can protect access and answer a specific account request.

Our Privacy Policy does not describe a need for your DANA, OVO, GoPay, or QRIS wallet password. Payment activity may produce a status or reference used to match your account record. Do not send wallet passwords or full payment credentials through support.

Contact us through the support route shown on radar138 and state that you are requesting access to your account data. Provide the account contact and a clear request category. We may verify ownership before responding, and the available response depends on local law.

Yes, you can ask us to check or correct account details covered by the Privacy Policy. Send the account identifier, identify the field that is wrong, and explain the requested change. We may complete an ownership check before applying or assessing the correction.

We keep account, security, support, and payment-reference records for the period needed for their stated purpose or applicable legal duties. The Privacy Policy explains the categories involved. You can contact support to ask why a particular record remains, subject to local law.

Tell support that your question concerns cookies, include the mobile browser and account contact involved, and describe the setting or sign-in effect. We can explain the relevant cookie purpose and available choices. Any request to restrict or remove related data depends on local law.

Open your radar138 Privacy Policy account path

Browse support routes for policy requests

Account privacy help

Wallet record check

Cookie access request

Explore how radar138 handles account privacy

Data collection

Cookie handling

Account security

Payment references

Retention choices

Request changes

Check common radar138 Privacy Policy answers

01 What does the radar138 Privacy Policy cover?

02 What data is collected when I open an account?

03 Does radar138 store my DANA or QRIS password?

04 How can I request a copy of my account data?

05 Can I ask radar138 to correct my details?

06 How long does radar138 keep privacy records?

07 How do I ask about cookies on my mobile device?

Related Pages