Reference

888r Privacy Policy For Your Data

The 888r Privacy Policy explains how we collect, use and protect details linked to your account, device and wallet activity.

Account dataWallet recordsDevice choicesPolicy access
888r 888r Privacy Policy For Your Data
HELP ROUTE

Check Your Privacy Contact Path

A clear contact route matters when your account details or payment records need attention.

Account help panel Open the help panel after signing in and mention the account step, device path…
Wallet status request For DANA, OVO, GoPay or QRIS questions, provide the payment rail and visible status…
Data change request Ask us to correct account details through the same account help route.
SECURITY PRACTICE

Switch On Account Data Controls

Privacy depends on practical account habits, not only a page of legal wording. We separate access checks from payment references, explain why device signals appear, and keep a…

Data we handle

We handle details such as your phone verification result, account settings, sign-in events, device signals and wallet references.

Cookie choices

Cookies and similar tools can remember a session, protect the account path and show whether a page has loaded correctly.

Account security

Phone verification before account access helps connect a request to the correct account.

Record retention

We retain account, security and transaction records for as long as needed for the stated purpose, dispute handling and legal…

Correction requests

If your name, phone detail or account setting is inaccurate, use the account help panel and describe the exact field.

Policy questions

You can ask why a device signal, wallet reference or sign-in event appears in your record.

Ask About 888r Privacy Policy

These Privacy Policy answers address the account and wallet questions you are most likely to have before opening an account. Each answer stays focused on data use, access, security and requests connected with Indonesian access where local law permits.

The 888r Privacy Policy covers account details, phone verification, sign-in events, device signals, cookies, support messages and payment references connected with DANA, OVO, GoPay, QRIS or bank transfer.

We use limited device and session signals to recognise an account path, protect sign-in activity and investigate unusual access. These records help us separate your request from another person’s request.

Yes. The Privacy Policy explains how QRIS references and visible payment status can be linked to your account transaction record. We do not need your wallet password to check that status.

Open the account help panel, identify the exact field that needs correction and complete any requested phone verification. We use that step to confirm the request comes from the account holder.

We keep account, security and transaction records for the period needed for their stated purpose, dispute handling and legal duties. After that period, our process addresses removal or anonymisation.

Yes. Send the wallet name and visible status through the account help route. We can explain how that reference supports payment matching without asking you to disclose a password or private wallet code.

You can open this Privacy Policy page before completing the account path and return to it from the policy link. If access is restricted, it depends on local law and regional availability.