Reference

rajampo Privacy Policy for Your Account

Our Privacy Policy explains what rajampo collects when you open an account, sign in, browse the lobby or use DANA and QRIS.

Account recordsWallet receiptsCookie choicesPolicy requests
rajampo rajampo Privacy Policy for Your Account
REQUEST HELP CLEARLY

Ask About Your Privacy Policy Rights

A clear support route helps when you want to ask what data is held, why an account check is needed or how a wallet receipt is…

Account data request Ask us to identify the account records connected with your phone verification or sign-in…
Wallet record question Send a payment receipt or status reference when asking about DANA, OVO, GoPay, QRIS…
Policy change request Use the policy support route to ask for a correction, clarification or change request.
DATA HANDLING PATH

Browse How rajampo Handles Privacy

We describe practical handling rather than broad promises: which account events create records, how cookies support a session and how payment references help resolve status questions.

Account details

We may use your phone, account credentials and verification result to create and protect access. Phone verification comes before account access, so we can connect the right request to the right record.

Device activity

Your device type, browser signals and session events can help us recognise a sign-in pattern and investigate an access problem. The same details may explain why a session asks you to verify again.

Cookies and sessions

Cookies can remember session settings and support account navigation between sign-in, cashier and lobby pages. The Privacy Policy explains their purpose and how you can ask about cookie handling.

Payment references

DANA, OVO, GoPay, QRIS, bank transfer and virtual account records can include a receipt number, amount status or matching reference. We use these details to answer account payment questions.

Security checks

We use account checks, phone verification and sign-in signals to reduce mistaken access to personal records. Do not share your password or verification code when asking for support.

Retention and changes

We keep records for the period described in the Privacy Policy, then handle deletion or continued storage according to the stated purpose. Contact support to request correction, access or another permitted change.

Find Answers About Privacy Policy

These Privacy Policy answers focus on the questions you may have before opening an account or asking about a payment record. We keep each response tied to an actual account, device or wallet step, and access depends on local law.

It covers account details, phone verification, device and session signals, cookies, support requests, payment references and retention. It also explains how to ask about access, correction or another permitted change.

Yes. The Privacy Policy covers receipt identifiers, payment status and matching references connected with DANA or QRIS. We use those records to reconcile an account question, not as a general profile of you.

Phone verification helps connect an account request to the correct account and reduce mistaken access to personal records. It is part of the account access step described in our Privacy Policy.

It can include device type, browser signals, session events and sign-in patterns. These details help us investigate access problems or repeated verification requests, with handling explained in the Privacy Policy.

Use the privacy support route beside the cashier area and state whether you want access, correction or clarification. We may ask for an account check before discussing personal records.

The retention period depends on the purpose described in the Privacy Policy and any applicable local requirement. Ask support about a specific account or receipt reference for the relevant handling path.

Yes. Contact support with the account and device context connected to your request. We will explain cookie handling, session records and any available change or deletion step under the Privacy Policy.