Reference

Privacy Policy for rp55com Accounts

Our Privacy Policy explains how rp55com handles the details you provide when opening an account, signing in, checking wallet status or contacting support.

Account dataCookie choicesWallet recordsYour data requests
rp55com Privacy Policy for rp55com Accounts
CONTACT ROUTES

Privacy Help Beside Your Account Path

A clear contact path matters when you want to understand a record or change a detail. Start from your signed-in account support area and include the email or phone linked to your profile, plus the subject of your Privacy Policy request. We may ask for an account check before discussing personal data, especially when a DANA, OVO or QRIS reference is involved. If your account is locked, use the same support route rather than sending identity details through an unrelated channel.

Team online

Account privacy request

Use the support path inside your account to ask what personal details we hold, why a field is needed or whether an eligible record can be corrected. Include your linked phone number so we can locate the right profile.

Wallet record query

For a DANA, OVO, GoPay or QRIS record, share the transaction reference and status shown in your account. We use those details to locate the payment event without asking you to send a wallet password or private access code.

Sign-in safety concern

If a device or sign-in looks unfamiliar, tell us through the account support route and change your password from the account settings path. We can review the access event and guide you through the next account-security step.

Correction follow-up

When you request a correction or removal, we may ask for enough account detail to confirm ownership. Our reply will explain any action taken, any record we must retain and the reason that record remains available.

DATA PRACTICE

What We Do With Your Personal Details

Our Privacy Policy is applied through practical account steps rather than broad promises. Phone verification helps connect a request to the right profile, while device and session checks help us spot unusual…

Account creation

When you open an account, we use the details you submit to create your profile, send account notices and complete the phone verification step before account access. Keep your contact details current so a privacy request reaches the correct record.

Device signals

Your browser, device type, session timing and sign-in events may be recorded for account protection and fault checking. These signals help us compare a new access attempt with ordinary activity without treating the device itself as your identity.

Cookie controls

Cookies can keep your sign-in flow, language choice and page state available between visits. You can adjust cookie settings in your browser, though blocking required cookies may interrupt account access or prevent a wallet status from displaying correctly.

Payment references

DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity can create reference data such as status, time and amount. We use it to reconcile your account record, investigate a disputed event and answer a payment-related privacy request.

Account security

We use phone verification, sign-in records and account checks before releasing personal details through support. Never send a password, wallet PIN or one-time code in a message; those credentials are not needed for a Privacy Policy request.

Retention and changes

We remove or anonymise eligible details when the operational, dispute or legal need ends. Some transaction or account records may remain for a required period, and we will explain that reason when you ask us to correct or delete data.

Privacy Policy Answers for Indonesia

These Privacy Policy answers address the account and wallet questions you are most likely to have before opening or using your rp55com profile. They cover the data collected during phone verification, sign-in, cookies and local payment activity, as well as the practical steps for requesting a copy, correction or deletion. Where a request affects account access or a payment record, we explain the account check that may be required.

It covers personal details linked to your account, phone verification, sign-in and device events, cookies, support messages and payment references from DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity. It also explains retention, security and ways to request changes.

We collect the contact and account details you submit, together with phone verification status and records needed to keep access secure. When you sign in, device type, browser signals and session events may be recorded to detect unusual activity and resolve access faults.

Yes. The Privacy Policy includes payment references connected with DANA and QRIS, as well as OVO, GoPay, bank transfer and virtual account activity. These may show status, amount, timing and a reference code so we can match a wallet event to your account.

Use the support path inside your signed-in account and state that you want a copy of your personal data. Include the phone or email linked to the profile. We may verify account ownership before sharing details, especially when wallet or sign-in records are included.

You can request a correction or removal through account support. We will check the request, update eligible details and explain any record that must remain for an operational, dispute or legal reason. Removal can also affect account access where local law permits.

Cookies can keep your sign-in state, language selection and page settings available. Browser controls let you block or clear them, but required cookies may be needed for account access and wallet status. Our Privacy Policy explains their role rather than treating every cookie the same.

Change your account password from settings, then contact support through the signed-in account route if possible. Tell us the approximate time and device shown in your access record. Do not send a wallet PIN, password or one-time code in your request.