Reference

rp99 Privacy Policy For Your Account

Our Privacy Policy shows exactly how we handle the account, wallet and device details connected with your rp99 access.

Clear data purposesWallet record checksPhone verification

Privacy Policy For Wallet Records

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

This Privacy Policy covers the details we receive when you open an account, verify your phone, sign in, use the lobby, or ask support to check a wallet status. We may handle account identifiers, login events, device and browser signals, selected lobby activity, payment references, and

1
messages you send through the account support path. DANA, OVO, GoPay and QRIS names can appear in transaction records so we can match a wallet reference with its account status; bank transfer and virtual account records may be handled for the same purpose. We use these
2
details to operate access, investigate mismatched receipts, reduce unauthorised account activity, and meet applicable requests where local law permits. Eligibility and access depends on local law. We do not describe payment records as a public profile, and we do not ask you to place sensitive credentials
3
in a support message.

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

HELP PATH

Privacy Questions Through Account Support

A direct account support path gives you a practical way to ask about this Privacy Policy without posting personal details in a public chat. If a receipt, login event or device record needs checking, send the request from the account connected to it and describe the issue briefly. We can then match your request with the relevant account or wallet reference.

Team online

Account requests

Use the signed-in account support path to ask which personal details are connected with your profile or to request a correction to an account field.

Wallet questions

For DANA, OVO, GoPay or QRIS records, include the payment reference and date rather than sending a wallet password; we use those details for status checks.

Device access

If a browser or mobile session looks unfamiliar, tell us through account support so we can examine the access event and help you protect the account.

DATA PRACTICE

Privacy Controls Behind Dragon Tiger Access

We keep this policy practical by connecting each data use to an account action you can recognise.

Account details

We use your account identifier and verified phone detail to distinguish your profile from another sign-in, especially when a Dragon Tiger session or wallet question needs checking.

Cookies and sessions

Cookies and similar session data help keep your sign-in active and remember essential access choices; clearing them can sign you out and require phone verification again.

Device signals

Browser, mobile device and login signals help us spot unusual account access. They support security checks and are not presented as a public description of you.

Wallet references

Payment references from QRIS, DANA, OVO, GoPay, bank transfer or virtual account can be checked against account activity when a receipt or status does not match.

Retention approach

We retain account, security and transaction records for the period needed for the stated purpose, account handling, dispute checks or applicable legal duties, then assess removal.

Change requests

To request access, correction or deletion where available, contact us through your account support path with your account identifier and the exact field or record concerned.

Privacy Policy Questions About rp99

These Privacy Policy answers focus on the account steps and local payment records you are most likely to ask about before opening access. We keep the wording tied to rp99 processes, including phone verification, mobile sessions, wallet status checks and requests made where local law permits.

The rp99 Privacy Policy covers account details, phone verification, login and device signals, lobby activity, payment references, cookies, support messages, retention and requests to access or correct personal data.

Yes. We may handle DANA and QRIS references, along with OVO, GoPay, bank transfer or virtual account details, to match a receipt with an account status or investigate a payment query.

Phone verification helps connect the account with the person completing sign-in and supports checks when an unfamiliar device, login event or wallet-status request appears on the account.

The policy covers relevant browser, mobile device and session signals used for sign-in continuity and account security. Clearing cookies may end the session and require another account check.

You can request a correction through the account support path. Send your account identifier, name the exact field that needs changing, and provide only the details needed to locate that record.

We keep records for the stated account, security, dispute or legal purpose. Retention can differ by record type, and we assess removal when that purpose no longer requires the data.

Yes. Access and eligibility depends on local law. Privacy requests are handled under applicable requirements, and the account support path is the place to ask about a specific request.

rp99 Privacy Policy For Your Account

Privacy Questions Through Account Support

Account requests

Wallet questions

Device access

Privacy Controls Behind Dragon Tiger Access

Account details

Cookies and sessions

Device signals

Wallet references

Retention approach

Change requests

Privacy Policy Questions About rp99

01 What does the rp99 Privacy Policy cover?

02 Does Privacy Policy handling include DANA and QRIS payments?

03 Why does rp99 ask for phone verification?

04 How does the Privacy Policy treat my mobile device?

05 Can I request a correction to my rp99 data?

06 How long does rp99 keep personal data?

07 Does Privacy Policy access depend on Indonesian law?

Related Pages