Reference

Privacy Policy For Your rapi123 Account

Our Privacy Policy explains what rapi123 collects when you create an account, sign in from a mobile device, or check DANA and QRIS status.

Account choicesWallet recordsPolicy access
rapi123 Privacy Policy For Your rapi123 Account
POLICY HELP ROUTES

Where To Ask About Privacy Policy

A clear contact path matters when you want to ask what we hold, correct an account record, or question a wallet-related data entry. Start from the support route linked inside your rapi123 account and include the phone number or email attached to the account. We use those details to locate the right record without asking you to send a full payment credential.

Team online

Account privacy request

Use the account support path to ask for a copy, correction, or clarification of personal data connected with your rapi123 profile. Include the phone number used for verification so we can match the request to the right account.

Wallet record question

If a DANA, OVO, GoPay, or QRIS status appears in a support exchange, describe the date and reference shown in your account. We can check the related record while you keep your wallet PIN and full credentials private.

Access concern

When you cannot reach the Privacy Policy from a mobile browser, use the same account support route and tell us your device type. We can point you back to the policy page without requiring a new account.

DATA PRACTICE CHECK

Inside rapi123 Privacy Policy Controls

We keep the policy practical by separating account operation from requests about your personal data.

Collection boundaries

We collect account details, verification events, device signals, support messages, and relevant payment status records when they are needed for account access or a data request. We do not need your wallet PIN to investigate a receipt or status question.

Cookie choices

Browser cookies or similar storage can support sign-in settings and the policy page on your device. Your browser provides controls for clearing or restricting them, although some account functions may then need another sign-in.

Account protection

Phone verification is part of our account access checks, and sign-in activity may be reviewed when access looks unusual. Keep your verification code private and contact support if a device or session does not look familiar.

Retention approach

We retain records for the period needed to operate the account, resolve support questions, meet applicable obligations, or protect against misuse. When a record is no longer needed for those purposes, our handling follows the applicable retention process.

Correction requests

You can ask us to correct a personal detail that is inaccurate or outdated. Send the request through the account support path, identify the affected field, and provide enough account context for us to verify the request safely.

Policy contact

Questions about this Privacy Policy belong in the account support route, where the request can be connected to your profile. Do not send a wallet PIN, full card credential, or one-time verification code with your message.

Privacy Policy Answers For Indonesia Accounts

These Privacy Policy answers address the account questions we expect before you open rapi123. They explain the records connected with phone verification, mobile access, wallet status, cookies, correction requests, and local eligibility. If your situation is not covered, use the account support route and describe the specific record or policy point you want us to check.

It covers data used for account creation, phone verification, sign-in, device access, support messages, and payment status checks. That can include records associated with DANA, OVO, GoPay, QRIS, bank transfer, or virtual account activity when they relate to your account.

Phone verification helps connect an account request with the correct account holder before access is granted. It also gives our support route a way to locate your profile when you ask about a Privacy Policy request, a sign-in event, or an unclear wallet status.

Yes. We may handle device and browser signals connected with sign-in, page function, and unusual access checks. We use these records for account operation and protection, not as a reason to request your wallet PIN or one-time verification code.

Use the support route inside your account and state which personal detail needs correction. Include the phone number or email attached to the profile, but leave out wallet PINs and verification codes. We may confirm account context before changing a record.

We keep records for as long as needed for account access, support handling, security checks, applicable obligations, or a documented request. Retention can vary by record type and purpose. When a record is no longer needed, our handling follows the relevant process.

You can ask through the account support path for a description or copy of personal data connected with your profile, subject to identity checks and applicable rules. Mention whether your question concerns sign-in, phone verification, cookies, or DANA and QRIS status.

Yes. Account access and the handling of certain requests depends on local law. We apply the Privacy Policy with that context in mind, and we may explain why a request needs verification, a narrower scope, or a different handling route.