Reference

rp678 Privacy Policy for Your Account

Your account data, wallet status and login activity are covered in the rp678 Privacy Policy, so you can understand what we collect before opening an account.

Clear data purposesWallet-linked checksCookie choicesContact route
rp678 rp678 Privacy Policy for Your Account
CONTACT ROUTES

Wallet Status and Privacy Contact Paths

A clear contact path matters when you want to ask about the Privacy Policy or a record connected with your account. Start from the support link beside the cashier area, include the phone or email connected to your login, and tell us whether your question concerns cookies, account access, DANA, OVO, GoPay or QRIS. We use those details to locate the correct record without asking you to send a password or wallet PIN.

Team online

Policy questions

Use the support path beside the cashier area to ask how we collect, use or retain account data. Include your registered contact detail and the subject of your request, but never send your password, one-time code or wallet PIN in a message.

Access requests

If you need a copy, correction or deletion request under applicable rules, tell us which account record is involved. We may ask for an account step that confirms ownership before changing data, especially when the request affects login or payment history.

Payment records

For a DANA, OVO, GoPay, QRIS, bank transfer or virtual account question, attach the payment date and reference only. We can compare that reference with the cashier record while keeping your wallet password, card secret and one-time code out of the request.

DATA PRACTICE

How rp678 Handles Account Data

Our Privacy Policy is applied through the account, wallet and device steps you actually use. We separate login checks from payment references, limit support access to the records needed for your request…

Account creation

When you open an account, we use the details you submit to create login credentials and send account-related messages. Phone verification takes place before account access, helping us connect the right person with the right account without requesting unrelated profile details.

Wallet references

A DANA, OVO, GoPay or QRIS payment may produce a reference, amount and status for reconciliation. Bank transfer and virtual account records can follow the same path. We use these details to match an event, investigate a mismatch and answer your payment question.

Device signals

Your phone or computer may share browser type, session time and basic device signals when you log in. We use them to recognise unusual access and protect the account. These signals do not give us your device files, contacts or private messages.

Cookies

Cookies keep a signed-in session, remember selected settings and help us understand whether a page works after you return. You can manage cookies through your browser controls. Turning some off may require another login or affect saved preferences, while account records remain governed by this policy.

Retention

We keep records only for the operational, security, support or legal period connected with their purpose. Payment references may remain while reconciliation is open, and account messages may remain while a request is being handled. When retention is no longer needed, records are removed or restricted.

Security requests

Ask us to access, correct or remove eligible data through the support route beside the cashier. We may verify ownership before acting, and we will explain if a record must remain for a legal or payment reason. Access depends on local law and the request details.

Privacy Policy Questions for rp678

These answers address the searches we receive about the rp678 Privacy Policy, from wallet references to phone verification and cookie controls. Read them before opening an account, then use the support route beside the cashier if your request concerns a specific record. We will handle the request according to applicable rules and where local law permits.

It covers account details, phone verification, login activity, device signals, cookies, payment references and support requests. It also explains retention and your available requests. DANA, OVO, GoPay, QRIS, bank transfer and virtual account references are handled only for matching, support, security or related legal needs.

Yes. The Privacy Policy explains that DANA and QRIS may provide a payment reference, status and related reconciliation detail. We use that record to match the cashier event to your account or investigate a mismatch. Do not send a wallet PIN or one-time code to support.

We use the contact detail connected to your account and may require phone verification before access. If a request asks us to change or release account data, we can ask for an additional ownership step. This helps prevent another person from taking control of your records.

You can contact us through the support route beside the cashier and state whether you want access, correction or deletion. Include the registered contact detail and the record concerned. We may verify ownership first, and the result depends on local law and any required payment retention.

Cookies can keep your session active, save selected settings and show whether a page works on your phone or computer. Browser controls let you manage them. If you disable certain cookies, you may need to log in again or lose saved preferences, but the account policy still applies.

We retain each record for the period connected with account support, security checks, payment reconciliation or a legal requirement. A QRIS reference may remain while a payment question is open. When the purpose ends, we remove, restrict or anonymise the record where applicable.

Use the support link beside the cashier area and identify your account contact detail, request type and any relevant payment reference. We will not ask you to disclose a password or wallet PIN. Handling and eligibility depend on local law, including where local law permits.