Reference

Open rp500 With Privacy Policy Clarity

Our Privacy Policy explains what we collect when you open an rp500 account, use DANA or QRIS, and move between the mobile lobby and account page.

Clear data purposesWallet record detailsYour request optionsIndonesia access wording
rp500 Open rp500 With Privacy Policy Clarity
HELP PATH

Check Privacy Support Before Account Access

A clear contact route helps when a Privacy Policy question affects your account or wallet record.

Data request Ask us which account details we hold, why they are used, and whether a particular phone verification or login record is connected to your profile. Include the email or phone route attached to the account so we can compare the request with our records.
Wallet receipt For a DANA, OVO, GoPay or QRIS question, send the transaction reference and approximate time rather than your wallet password. We use those details to locate the payment record, explain its status, and separate account data from information held by the wallet provider.
Correction route If your name, phone detail or account contact is inaccurate, ask for a correction through the listed support route. We may request an account step or phone check before changing data, because the Privacy Policy requires us to protect the profile from an unverified request.
CONTROL CHECKS

Explore Data Controls Inside rp500

We handle Privacy Policy requests as account operations, not as a general advertising conversation. Our process separates identity checks, wallet references, device activity and support messages so we can answer the right…

Account details

We may hold the contact details you provide during account creation, including a phone number used for verification. That record helps us connect a request to the correct profile and prevents a change request from being applied to someone else.

Device signals

Login time, browser type and device signals can help us spot a session that does not match your usual account activity. On mobile, these checks support the path from login to the lobby without exposing your wallet PIN to us.

Cookies

Cookies and related storage can remember a session step, preserve selected settings and help us understand whether a page request completed. You can manage browser storage through your device settings, although removing it may require another login or verification step.

Payment records

A DANA, OVO, GoPay, QRIS, bank transfer or virtual account reference may be retained to reconcile a receipt with your account. We use the reference for status checks and do not need your wallet password to investigate it.

Account security

Phone verification, login checks and careful handling of support requests work together to protect account data. Keep your password and wallet credentials private; our support route should not ask you to reveal either one while handling a Privacy Policy request.

Retention requests

You can ask what data remains, why it is retained, or whether a correction is possible through the listed contact route. We assess deletion or amendment requests against the record purpose, account status and requirements that apply where local law permits.

Ask About rp500 Privacy Policy

These Privacy Policy answers focus on the account questions you are most likely to have before using the Indonesia service. We keep the wording practical: what is collected, how wallet records are matched, what happens on a phone, and how to request a change. Where access or eligibility is relevant, it depends on local law.

It covers account and phone details, login and device signals, cookies, payment references, support messages, retention and your request options. The policy explains why each category is used and how you can ask for access, correction or another permitted action.

We may receive a transaction reference, amount status and timing from a DANA or QRIS request so we can match a receipt to your account. We do not need your wallet PIN. OVO, GoPay, bank transfer and virtual account records follow the same status-check purpose.

Phone verification helps connect an account request to the correct profile and supports checks when you ask to change account details. We may use the verification record alongside login activity, but you should never send your password or wallet credential through support.

Yes, you can contact us through the listed support route and ask which account data we hold or request a correction. Include your account contact detail, not a secret credential. We may complete an identity check before releasing or changing information.

Retention depends on the record type and why it was created. Payment references may be kept for reconciliation, while support and verification records may follow separate operational needs. Ask us for a record-specific explanation; deletion depends on applicable requirements and local law.

Cookies or similar browser storage can keep a login step, device setting or page state available on your phone. Clearing them may sign you out or repeat verification. Account access depends on local law, and browser controls remain available in your device settings.

Use the support contact route displayed on the site and describe the policy issue in plain English. For a wallet matter, add the payment method and transaction reference. Do not include a PIN or password; our team can explain the relevant data step safely.