Reference

rp9 Privacy Policy for Your Account

DANA, OVO, GoPay and QRIS records are handled alongside your account details under the rp9 Privacy Policy, so you can see what we collect and why.

Clear data purposesWallet record contextAccount request pathIndonesia access terms
rp9 rp9 Privacy Policy for Your Account
PRIVACY HELP

Get Help With a Policy Request

A clear support path helps when you want to ask about a record, correction or account access matter.

Account data request Ask us which account details we hold and why they are used. Include the phone verification stage or login issue so we can locate the correct record without requesting unnecessary wallet credentials.
Payment record check For a DANA, OVO, GoPay, QRIS, virtual account or bank transfer query, provide the relevant receipt reference and date. We can then check the payment status without asking for your wallet password.
Correction pathway If your contact detail or account record needs changing, tell us what appears wrong and which account step confirms you. We may complete a phone check before applying or discussing the request.
DATA CONTROLS

How rp9 Handles Personal Data

We keep the Privacy Policy practical by connecting each data category to an account task. Login protection, phone verification, wallet status checks and support follow-ups can require different records, while cookies and…

Collection purpose

We collect account and contact details to create access, complete phone verification and respond to account requests. Payment references from DANA or QRIS help us match a receipt without needing your wallet password.

Cookies and sessions

Cookies can keep a login session and remember necessary browser settings. On a mobile browser, clearing site data may remove that session, so you may need to complete the account access step again.

Device signals

We may record browser or device signals linked to login protection and unusual access checks. This helps us investigate an account session while keeping the review tied to the relevant security event.

Account security

Phone verification is used before account access where required by our security process. Never share a wallet PIN or password in a support message, even when checking a payment receipt.

Retention choices

We retain records for the period needed for account security, payment matching, support history or legal duties. When a retention period ends, the record is deleted or separated where applicable.

Change or deletion request

You can ask about access, correction or eligible deletion through the privacy support path. We may verify your phone-linked account first, then explain any legal or security reason a record must remain.

Privacy Policy Answers for Indonesia

These Privacy Policy answers address the searches we hear most often about account data, wallet references, cookies and access requests. If your case involves a particular receipt or phone verification step, include that detail in your request so we can check the relevant record.

It covers account details, phone verification, login and device signals, cookies, support messages, and payment references from DANA, OVO, GoPay, QRIS, virtual account and bank transfer.

We use the verification result to protect account access and connect a privacy request to the correct account. The access process depends on local law and our current security checks.

Yes. The Privacy Policy covers QRIS references and related receipt details used to match payment status. We do not need your QRIS wallet password to investigate a receipt or account record.

Send a privacy request through the account support path and identify the phone-linked account step. We may verify your identity before explaining which records can be provided under applicable law.

Yes. Tell us which detail is inaccurate and provide the account step that confirms your identity. We will assess the correction request and explain any records that must remain for security or legal duties.

We keep payment and login records for the period needed for account protection, receipt matching, support history or legal duties. The applicable period can differ by record and local requirements.

Yes. Ask which cookie or device signal concerns you and include the browser path used for access. Clearing site data may end your session and require phone verification again.