Reference

Privacy Policy For Your rk555 Account

Our Privacy Policy explains how we use the account, device and payment details you share with rk555, so you can understand each step before opening an account.

Clear data purposesWallet status checksMobile access controlsPolicy request path
rk555 Privacy Policy For Your rk555 Account
REQUEST HELP DIRECTLY

Privacy Policy Support For Indonesia

A clear contact route matters when your account record or wallet reference needs attention. Our support path is designed for policy questions, correction requests and access concerns rather than general lobby advice.

Policy questions Use our support contact when you want to ask what the Privacy Policy covers, why a phone number is needed or how a particular account record is used. Include your rk555 account phone number and the subject of your request so we can route it accurately.
Wallet references If a DANA, OVO, GoPay or QRIS reference appears unfamiliar, send the receipt reference and approximate transaction date through support. We can compare the payment record with your account without asking for your wallet PIN, password or full private wallet credentials.
Access concerns When a sign-in alert, phone verification prompt or device change does not match your activity, contact support before continuing. We can help identify the account path, record the concern and explain the security step that applies where local law permits.
SECURITY BY ACCOUNT STEP

What We Keep And Why

We keep our Privacy Policy practical: each data category has a reason connected to account access, payment matching, security or a request you send us.

Account details

We use your phone number and account identifiers to create the correct login path, complete phone verification and respond to account requests. Keeping these details accurate helps us distinguish your record from another account when you ask for a correction or access explanation.

Device signals

A mobile browser or desktop sign-in can create security signals such as device and session details. We use them to recognise account activity, investigate an unexpected access attempt and help protect the account path without asking you to share a device password.

Payment matching

A DANA, OVO, GoPay, QRIS, bank transfer or virtual account reference lets us connect a payment status with the right account. We use the reference and related status details for reconciliation, support and account records, not for collecting your wallet PIN.

Cookies and sessions

Our browser session may use cookies or similar technical storage to keep your sign-in path working, remember security state and measure page operation. You can manage browser storage controls, but removing them may interrupt phone verification or require you to authenticate again.

Retention choices

We retain records for as long as needed for the purpose described in the Privacy Policy, account security and applicable local requirements. When you ask why a record remains, our support team can explain the category, purpose and request route available where local law permits.

Change requests

To request correction, access or clarification, contact support with your account phone number, the relevant data category and a short description. We may need to verify that you control the account before discussing details, which protects your record from an unauthorised request.

Privacy Policy Questions About rk555

These Privacy Policy answers address the account and payment questions you may search before opening access from Indonesia. We explain the practical route for phone verification, device records, cookies, wallet references and data requests. If your situation is not covered, contact support with the account phone number connected to your question. We will handle the request according to the policy and where local law permits.

The rk555 Privacy Policy covers account details, phone verification, device and session signals, cookies, payment references and support requests. It explains why we use each category, how we protect the account path and how you can ask for access, correction or clarification where local law permits.

We use your phone number to create and secure the correct account path, complete phone verification and identify your record when you contact support. It also helps us respond to an access concern without relying on a wallet PIN or another private payment credential.

Yes. The Privacy Policy includes payment references and status details connected with DANA, OVO, GoPay and QRIS, as well as bank transfer and virtual account records. We use those details to match activity with your account and resolve receipt questions, not to request your wallet PIN.

We may use technical device and session signals from the mobile browser or desktop path to recognise sign-ins, maintain account security and investigate unusual access. These signals help us respond when a device change does not match your activity, without needing your device password.

You can contact support to request correction or clarification of account data. Include your account phone number, the data category and the change you believe is needed. We may verify account control first, then explain the available action under the Privacy Policy and local requirements.

Retention depends on the purpose of the record, account security needs and applicable local requirements. Payment references, verification details and support messages may therefore follow different retention periods. Ask support about a specific category, and we will explain the request path where local law permits.

Use our support contact for questions about data access, correction, cookies, phone verification or an unfamiliar DANA, OVO, GoPay or QRIS reference. Share only the details needed to locate your account. Do not send a password or wallet PIN with your request.