Reference

rp8888 Privacy Policy for Your Account

The rp8888 Privacy Policy explains how we collect, use and protect details connected with your account, device and wallet activity.

Account dataWallet recordsCookie choicesSecurity requests
rp8888 rp8888 Privacy Policy for Your Account
PRIVACY ASSISTANCE

Get Clear Privacy Help for Wallets

A clear support path matters when you need to ask about personal data rather than a cashier result.

Account request Ask us to locate, correct or explain account data through the signed-in support route. We first check the account contact detail before sharing any private record.
Wallet record If a DANA, OVO, GoPay or QRIS receipt needs checking, send its reference with your account contact. We use those details to trace the matching payment event.
Security concern Report an unfamiliar login or device session through account support. We may ask for a verification step before changing access details or discussing activity history.
DATA CONTROL

See How Account Data Stays Protected

We handle privacy through specific account routines rather than a vague promise. The same account details that help us connect login, phone verification and cashier status are separated from public lobby activity.

Collected details

We may receive your account contact, phone verification result, device signals and payment references. These details help us provide account access, match receipts and investigate unusual activity.

Cookie settings

Cookies and similar browser storage can keep your session and selected settings available. You can manage storage through your device browser, though clearing it may require another login.

Account security

Before discussing private records, we compare the request with your account contact and verification details. This helps prevent another person from changing access or receiving account data.

Payment matching

A DANA, OVO, GoPay, QRIS, bank transfer or virtual account reference may be used to match a cashier event. We use that reference for the specific account task.

Retention process

We keep records for account operation, security checks and legal needs only for the period required by those purposes. Afterward, records may be removed or restricted.

Change request

To request correction, access or removal of eligible data, contact support from your account area. Include the relevant account detail and the change you want us to assess.

Privacy Policy Questions About rp8888

These Privacy Policy answers address the account and device questions you are most likely to have before opening an account. We keep the wording tied to practical actions, from checking a wallet reference to asking us to correct a stored contact detail. If your situation is not covered, use the account support route and describe the exact record you want us to assess.

It covers account contact details, phone verification, device signals, cookies and payment references. We use them for account access, receipt matching, security checks and legal needs where local law permits.

A DANA or QRIS reference helps us connect a cashier event with the correct account and check its status. We use it for that support or account task, not as a public profile detail.

Send the request through the signed-in support route and identify the email or phone linked to your account. We verify ownership first, then assess which records can be provided under local law.

Yes. Tell support which account detail is wrong and what the correct value should be. We may ask for phone verification or another ownership check before changing the stored record.

Our Privacy Policy treats browser cookies and device storage as tools that can retain session or setting details. You can clear them in your mobile browser, but another login may then be needed.

We retain account and payment records for operating the account, checking security or meeting legal needs. When those purposes end, we remove or restrict the records through our retention process.

Use the support route inside your account and state that the request concerns the Privacy Policy. Include the relevant record, such as a phone detail or GoPay reference, without sending unnecessary private data.