Reference

Privacy Policy for Your Account Path

rp99apk puts our Privacy Policy beside the account path, so you can see what we collect before opening access to Live Baccarat Turbo, Live Sic Bo Royal or…

Account dataWallet referencesCookie choicesAccess depends on local law
Explore Our Lobby Read FAQ
rp99apk Privacy Policy for Your Account Path
CONTACT THE TEAM

Three Ways To Ask About Privacy

A clear contact route matters when you want to ask what sits on your account or why a wallet reference appears in a record. From the account support path, tell us whether your question concerns login activity, a DANA receipt, a QRIS reference or a request to change your details. Include only the minimum needed to locate the account; never send a wallet PIN or full payment password. We answer privacy requests through the support route shown on rp99apk.

Team online

Account privacy request

Ask us to identify the account data linked to your login details. We may request an account step or phone verification before discussing records, so a stranger cannot obtain details from your profile.

Wallet reference question

If a DANA, OVO, GoPay or QRIS reference looks unfamiliar, send its date and status through support. We use the payment reference to locate the event while avoiding any request for your wallet PIN.

Correction or removal request

Tell us which account detail needs correction or which stored contact route you want changed. We review the request against account security needs and explain if a record must remain for a stated operational reason.

SIX HANDLING CONTROLS

Six Controls Behind rp99apk Privacy

We handle privacy through practical account controls rather than broad promises. Login events, phone verification and device signals help us identify unusual access around titles such as Crash Countdown Round or Fishing…

Account collection

We collect the details needed for an account path, such as your contact route and verification result. If you open Live Baccarat Turbo or Live Sic Bo Royal, related login and session events may be recorded for access protection.

Device signals

Your phone or browser may provide technical signals such as session time, browser type and security events. These help us detect an unexpected login; they are not a request for access to your private files or device content.

Cookie choices

Cookies can keep your account path active and remember selected page settings. You can manage cookies through your browser controls, although switching them off may require another login or affect parts of the Privacy Policy page.

Wallet records

For DANA, OVO, GoPay, QRIS, bank transfer and virtual account actions, we retain useful references such as status, time and amount. We do not need your wallet PIN to match a payment event to your account.

Retention timing

We keep each record for the period needed for account security, payment matching, support handling or a legal requirement. When that purpose ends, the record is removed, anonymised or restricted according to our internal handling process.

Your requests

You can ask what personal data we hold, request a correction, or ask how a record is used. Send the request through the account support path; we may verify ownership before making a change or sharing account details.

Privacy Policy Questions About Access

These Privacy Policy answers cover the questions we hear before an account is opened or when a wallet record needs checking. They explain the practical route for data access, device handling, cookies, payment references and account changes. If your situation is not listed, use the support path and describe the specific record or login event without sending a PIN. Access depends on local law, including any local eligibility requirement.

The rp99apk Privacy Policy covers account details, phone verification, login events, device signals, cookies, support messages and payment references. It explains how we use those records for access protection, receipt matching and account assistance when you use DANA, OVO, GoPay or QRIS.

No. Our Privacy Policy does not require your DANA, OVO, GoPay or QRIS wallet PIN. We use a payment reference, status, time and amount to locate an account event. If support asks for a PIN, do not provide it and contact us through the account support route.

Use the support path shown inside your account and ask for a personal data access request. Include your account contact route and the record you want checked, such as a login event or QRIS reference. We verify account ownership before sharing details.

Yes, you can ask us to correct an inaccurate contact detail or verification record. Send the request through support and identify the field that needs attention. We may ask you to complete phone verification before changing account data, especially when wallet access is involved.

The Privacy Policy permits limited technical records such as browser type, session time and security events. We use them to investigate unexpected access and protect your account when you move between mobile pages and the lobby. We do not request access to private files.

We retain payment references for the period needed to match transaction status, answer a receipt question, protect the account or meet a legal requirement. After that purpose ends, we remove, anonymise or restrict the record under our retention process.

The Privacy Policy remains the page for our data handling, while access depends on local law. Where local law permits, you can use the account and request support through the stated path. If eligibility affects access, we explain the relevant account step rather than bypassing it.

Related Pages

rp99apk Indonesia Account information Access guide FAQ About Us