Reference

rp66 Privacy Policy For Your Account

Our rp66 Privacy Policy explains what we collect when you open an account, verify your phone and use DANA, OVO, GoPay or QRIS.

Clear data purposesWallet record controlsContact choices

Explore Our Lobby Read FAQ

How Our Privacy Policy Applies

rp66 Service availability depends on jurisdiction. Users are responsible for checking local law before access.

This Privacy Policy covers data collected when you create an account, complete phone verification, sign in, contact support or use payment paths connected with the lobby. We may record account identifiers, device details, login events, wallet status, transaction references and messages you send for account or

1
payment help. DANA, OVO, GoPay and QRIS may provide their own records under their separate terms, while we handle the account-side details needed to match a payment status. Cookies and similar storage can remember a session or security preference on your phone or desktop browser. We
2
use these records to operate access, check unusual sign-in activity, answer payment questions and meet applicable legal duties. Access and eligibility depends on local law, and this policy does not change that requirement. If we revise the policy, we will place the new version on this
3
page with its effective date.

Service availability depends on jurisdiction. Users are responsible for checking local law before access.

CONTACT PATHS

Where To Ask About Privacy Policy

A clear contact route helps you question a record without searching through unrelated pages.

Account privacy request Ask us to explain the account data linked to your phone verification, login event or support case. We will use the details you provide to locate the relevant record.

Wallet record question For DANA, OVO, GoPay or QRIS status questions, share the transaction reference and date rather than secret wallet credentials. This keeps the request focused on the payment record.

Access correction path If a profile detail is outdated, contact us through the account support route beside the cashier. We may ask for a verification step before changing personal account data.

DATA HANDLING

Six Practical Privacy Controls

Our handling process follows the account actions you take rather than treating every record the same way.

Account details

We may hold your name or contact detail, phone verification result and account identifiers so sign-in and account support connect to the right profile.

Device signals

Browser type, device markers and login times can help us spot unusual access. On mobile, these signals relate to the browser path you use from login to the lobby.

Cookie choices

Cookies or local storage may retain a session, language choice or security setting. You can manage browser storage, although removing it may require another account sign-in.

Payment matching

DANA, OVO, GoPay and QRIS references can be linked to your account-side payment status. We do not ask you to send a wallet PIN through support.

Retention checks

We retain records while they support account operation, payment questions, security checks, disputes or legal duties. After that need ends, records may be deleted or separated from direct account details.

Change requests

You can ask about access, correction or deletion through the support route beside the cashier. We may verify account ownership before discussing or changing personal data.

Privacy Policy Answers For rp66

These Privacy Policy answers address the account and payment questions you are most likely to have before opening an account. If your situation is specific, use the support route beside the cashier and include the relevant account step, device path or payment reference.

It covers account details, phone verification, login and device records, cookies, support messages, payment references and the reasons we retain or use those records.

Phone verification connects account access to the correct contact detail and helps us investigate unusual sign-in requests. We may ask you to repeat that check before discussing private account records.

Do not send a wallet PIN to us. Our account-side records may include a payment reference, status and timing for DANA or QRIS, while secret wallet credentials stay with you.

Yes. Contact us through the support route beside the cashier, identify the account detail that needs correction and complete any ownership check we request before the change is made.

Send a deletion request through account support and identify your profile. We will assess it against active payment questions, security records, disputes and legal duties before confirming what can be removed.

The same policy applies when you use a mobile browser from login to the lobby. Device and session records may support security, while browser storage controls can affect how often you sign in.

Yes. Account access and eligibility depends on local law. Where local law permits, we process requests under this policy; legal requirements may limit or shape the response.

rp66 Privacy Policy For Your Account

Where To Ask About Privacy Policy

Six Practical Privacy Controls

Account details

Device signals

Cookie choices

Payment matching

Retention checks

Change requests

Privacy Policy Answers For rp66

01 What does the rp66 Privacy Policy cover?

02 Why does Privacy Policy handling include phone verification?

03 Does rp66 store my DANA or QRIS wallet PIN?

04 Can I ask rp66 to correct my personal data?

05 How can I request deletion under this Privacy Policy?

06 How does Privacy Policy work on a mobile phone?

07 Does local law affect rp66 account data access?

Related Pages