Reference

ran4d Privacy Policy for Your Account

DANA, OVO, GoPay and QRIS records stay connected to the account details you submit, and our ran4d Privacy Policy explains why we use each piece of data.

Clear data purposesWallet record contextPhone verificationCookie choices

Explore Our Lobby Read FAQ

What Our Privacy Policy Covers

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

Our Privacy Policy covers the details you enter when opening an account, the phone verification step before account access, and technical records created while you move from login to the lobby on mobile or desktop. When you select DANA, OVO, GoPay or QRIS, we may retain

1
the wallet reference, request value, time and status needed to match your account activity and resolve a receipt question; we do not describe those rails as permission to use your data for unrelated purposes. Bank transfer and virtual account records can be handled in the same
2
account-support context. We use information to provide access, protect accounts, answer requests and meet obligations where local law permits. Eligibility and access depends on local law. The policy applies to ran4d pages and account services linked to this domain.

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

CONTACT PATHS

Ask About Privacy Policy Changes

A clear contact path matters when a record looks wrong or you want to understand a Privacy Policy request.

Account help route Use the help path connected to your account for a Privacy Policy question, correction request or access query. Include your registered contact detail and a short description so we can match the request to the right account record.

Wallet record query For DANA, OVO, GoPay or QRIS data questions, send the visible reference, date and status rather than a password or full wallet credential. This lets us check the payment record while limiting the sensitive details shared in your message.

Account access concern If phone verification or a login check appears unfamiliar, tell us through the account support path before changing repeated details. We can review the account signal, explain the Privacy Policy process and help separate a security concern from a normal device change.

DATA HANDLING PRACTICE

How ran4d Handles Privacy Requests

We keep this Privacy Policy practical by linking each data use to an account action you can recognise, such as phone verification, wallet status matching or a request sent through support.

Account details

We use the contact details you provide during account opening to identify your account, send account-related responses and complete the phone verification step. Keep your registered phone or email current so a Privacy Policy request can be linked to you without guesswork.

Device and cookies

A mobile browser and a desktop browser can create different technical records, including session, device and cookie data. We use these signals to keep pages working and help detect unusual access, while cookie controls let you decide whether optional records remain active.

Wallet references

When your account shows DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity, we may keep reference and status details for matching, support and account records. We do not need your wallet password to investigate a displayed transaction.

Account security

Phone verification before account access helps connect a sign-in to the contact detail you supplied. If a device change, repeated login attempt or unfamiliar session raises a question, contact us through account help and avoid sending passwords or complete payment credentials.

Retention questions

We retain records for the period needed for the stated account, support, security or legal purpose, subject to local requirements. You can ask why a particular record remains, and we will assess whether correction, restriction or removal is available under the applicable rule.

Requesting a correction

To request a change, send the account contact detail, the field you believe is inaccurate and the reason for the correction. We may ask for a confirmation step before changing it, so one account is not altered from an unverified request.

Privacy Policy Answers for ran4d

These Privacy Policy answers focus on the questions you may have before opening an account or contacting us about a stored record. We cover wallet references, cookies, phone verification, account access and correction requests in plain terms. If your situation involves a specific DANA, OVO, GoPay or QRIS reference, include that detail through the account support path so we can respond to the right record.

The Privacy Policy covers details you submit for account opening, phone verification, account support and security checks. It also covers technical session records and relevant wallet references. We use these details for stated account purposes, and access depends on local law.

Yes. The Privacy Policy covers wallet references, request values, timestamps and status details shown when your account uses DANA, OVO, GoPay or QRIS. These records help match activity and answer receipt questions; do not send us a wallet password.

We use the phone detail supplied during account opening to connect the verification step with your account and help assess an unfamiliar sign-in. If your number changes, contact account help first so we can explain the required confirmation step.

You can contact us through the account help route and ask which account, device, cookie or wallet records relate to you. Include your registered contact detail and a clear request. We assess the response under the applicable local rule.

Send the account contact detail, identify the field that is inaccurate and explain the correction you seek. We may request a confirmation step before changing it. This protects your account from an unverified alteration and keeps the request tied to you.

Our Privacy Policy distinguishes necessary session records from optional cookie data where applicable. Mobile and desktop sessions may create different technical records. You can adjust available cookie choices in your browser, while account security checks may still require necessary session data.

Yes. Access and eligibility depends on local law, including the rules that apply in your Indonesian location. Our Privacy Policy explains data handling where local law permits, but it does not change any legal restriction that applies to your account.

ran4d Privacy Policy for Your Account

Ask About Privacy Policy Changes

How ran4d Handles Privacy Requests

Account details

Device and cookies

Wallet references

Account security

Retention questions

Requesting a correction

Privacy Policy Answers for ran4d

01 What does the ran4d Privacy Policy say about my account data?

02 Does the Privacy Policy cover DANA, OVO, GoPay and QRIS records?

03 How does ran4d use phone verification data?

04 Can I ask what data the Privacy Policy keeps about me?

05 How do I request a correction under the Privacy Policy?

06 What happens to cookies on my mobile device?

07 Does access to ran4d depend on local law?

Related Pages