Reference

rp99apk Privacy Policy for Indonesia

Our Privacy Policy explains what we collect when you open an rp99apk account, sign in from a mobile device, or use DANA, OVO, GoPay and QRIS payment paths.

Account dataCookie choicesPayment recordsSecurity requests
rp99apk rp99apk Privacy Policy for Indonesia
CONTACT ROUTES

Get help with a privacy request

A clear contact route helps you act on this Privacy Policy without searching through unrelated pages.

Account help channel Send a Privacy Policy request through our account help channel when you need to access, correct or question information connected with your rp99apk account. We use the account identifier and request date to locate the right record before replying.
Payment status path For a DANA, OVO, GoPay or QRIS privacy question, share the payment reference and status shown in your account. We can then separate a wallet record from a general support message and limit the reply to information linked with you.
Security escalation If you notice an unfamiliar sign-in or device session, contact us through the same help route and state that the request concerns account security. We may pause discussion of sensitive details until the phone verification step confirms your account connection.
HANDLING DETAILS

What we do with your data

We keep this Privacy Policy practical by describing the handling points you can see in your account journey.

Account creation

When you open an account, we collect the details needed to create and protect that account. A clear phone verification step comes before account access, helping us connect later privacy requests with the correct account rather than an unverified message.

Device sessions

A mobile browser may create session and device records when you sign in and move from the login page to the lobby. We use these signals to detect unusual access, and we may ask you to verify your phone before discussing sensitive account details.

Cookie controls

Cookies can remember sign-in continuity, security settings and page preferences. Your browser controls whether optional cookies remain active. Turning them off may require another login or make some account pages less convenient, but it does not erase transaction records already held.

Wallet records

For DANA, OVO, GoPay and QRIS activity, we record operational details such as the chosen rail, reference, time and status. We use these fields to reconcile a receipt and answer a payment question without requesting unrelated personal content.

Retention periods

We retain information only for the period needed for account operation, security review, support history or legal record duties. A deletion request may therefore remove eligible profile details while a necessary payment or security record remains for its required period.

Change requests

If your phone detail or another account field is inaccurate, contact our help channel with the requested correction. We check account ownership first, record the requested change, and reply if more evidence is needed or if a record cannot legally be altered.

Privacy Policy answers for your account

These Privacy Policy answers focus on the searches we hear around account access, Indonesian wallet records, cookies and personal-data requests. Each answer reflects the way we handle the relevant account step rather than describing unrelated lobby content. If your situation is not covered, send the request through the account help channel with a clear date and account reference. Access and eligibility depend on local law.

The Privacy Policy covers account details, phone verification, sign-in and device records, cookies, support messages and payment references. It explains why we use those details, how security checks work, how long records may remain and how you can request access, correction or deletion.

We use DANA or QRIS transaction details such as the selected rail, reference, time and status to match a payment with your account and answer receipt questions. We do not need unrelated wallet content for that check, and support requests should include only relevant information.

Yes, where local law permits, you can ask for a copy of eligible personal data through our account help channel. Include your account identifier and the date of the request. We first confirm account ownership before discussing records connected with your phone or device.

Send the requested correction through the account help channel and explain which field is inaccurate. We may require the phone verification step or another account check before changing it. If a payment or security record must remain unchanged, we will explain that limitation.

Yes. When you sign in through a mobile browser, we may record session and device signals used for access continuity and unusual-session checks. These signals help protect your account; they do not replace the phone verification step required before sensitive account discussion.

You can request deletion through the account help channel, subject to local law and record duties. We assess profile details separately from payment, security or support records. Eligible information may be removed, while records needed for legal or security reasons can remain.

Use the account help channel linked near the cashier path and label your message as a Privacy Policy request. State whether it concerns access, correction, deletion, cookies or a wallet reference. We may ask for phone verification before sharing account-specific information.