Reference

Privacy Policy for Your rajastar Account

rajastar Privacy Policy explains what we collect when you open an account, sign in on mobile, use DANA or QRIS, and contact our help route.

Account dataWallet detailsCookie choicesAccess requests
rajastar Privacy Policy for Your rajastar Account
CONTACT ROUTES

Privacy Questions Around Login And Wallets

A clear contact route helps when a Privacy Policy question is tied to a real account event.

Account message Send a Privacy Policy question through the account help path and include your phone number’s last digits or the relevant request date. We use those details to locate the right record without asking you to disclose a wallet PIN.
Payment receipt For DANA, OVO, GoPay, QRIS, bank transfer or virtual account questions, attach the payment reference and amount shown on your receipt. We use the reference to check status while keeping your wallet password and authentication code private.
Access request Ask us to correct, explain or remove eligible account details by naming the record involved. We may confirm your signed-in account and phone verification first, then tell you what can be changed under local requirements.
DATA PRACTICE

Six Ways We Handle Your Account Data

Privacy is handled through practical account steps rather than broad promises. We separate sign-in checks from wallet references, limit staff access to the records needed for a request, and use device signals…

Phone verification

Before account access, we may check the phone verification response linked to your account. This helps us distinguish your request from an unfamiliar sign-in and gives our team a practical record when you ask to change personal details.

Device signals

We may retain limited browser, device and session signals to identify repeated sign-ins and investigate unusual access. These signals are not a request for unrelated files on your phone, and they do not replace the account details needed for payment matching.

Cookie controls

Cookies can remember session settings and help the account path load correctly after you return. You can clear them through your browser controls, although doing so may require another sign-in or phone check before the account page opens.

Wallet references

For DANA, OVO, GoPay and QRIS, we use transaction references and status details to connect a payment event with your account. We do not need your wallet PIN or one-time authentication code to answer a receipt question.

Retention period

We keep account, payment and support records for the operational, dispute and legal period that applies to the request. When a record no longer serves that purpose, we remove it or restrict access instead of keeping it without a reason.

Change requests

You can ask about a detail held on your account, request a correction or ask whether removal is available. We may first confirm account ownership through the signed-in path and phone verification, then explain any local-law reason a record must remain.

Privacy Policy Answers For rajastar Accounts

These Privacy Policy answers focus on the account actions you are most likely to check before opening an account. We cover wallet records, cookies, device access, correction requests and contact steps in plain English for Indonesia. If your question concerns eligibility or access, the answer depends on local law, so include your account reference when you contact us.

We may collect the phone number and verification response used for account access, along with details you submit in support messages. When you use DANA, OVO, GoPay, QRIS, bank transfer or a virtual account, payment references and status details may be recorded for matching.

Yes. The Privacy Policy covers wallet-related records received from a payment event, such as a reference code, status or receipt detail. We use these records to connect the transaction with your account and do not ask for your wallet PIN or authentication code.

Limited device, browser and session signals help us keep a sign-in connected to the right account and investigate unusual access. They are not a request to inspect unrelated phone content. Clearing cookies may require you to sign in and complete phone verification again.

Contact us through the signed-in account help path and identify the detail you want corrected. We may confirm your account and phone verification before making a change. If the record is linked to a payment receipt, include its reference rather than private wallet credentials.

You may ask whether eligible data can be removed or access can be restricted. We first check the account request and any connected payment or support record. Some records may need to remain for operational, dispute or legal reasons where local law permits.

We retain payment, account and support records only for the operational, dispute and legal needs connected to them. The period can differ by record type and local requirements. When the purpose ends, we remove the record or restrict access instead of retaining it without a reason.

Send an access question from your signed-in account and name the record or activity involved, such as a QRIS receipt or phone check. We may request account confirmation before replying, then explain what can be shown, corrected, restricted or removed.