Reference

5rp Privacy Policy For Your Account

The 5rp Privacy Policy explains how we use account, device and wallet details when you open the lobby with DANA, OVO, GoPay or QRIS.

Account clarityWallet recordsCookie choicesPrivacy requests
5rp 5rp Privacy Policy For Your Account
PRIVACY HELP ROUTE

Where To Ask About Your Records

A clear contact path matters when a wallet reference or account detail looks unfamiliar. We ask you to use the support route shown inside your account, include the relevant receipt or status reference, and avoid sending a password or full wallet PIN. Our team can direct a privacy request to the right handling queue while keeping the original account context attached.

Team online

Account contact path

Open the support route from your signed-in account and describe the Privacy Policy request clearly. Include your registered phone number only when requested so we can locate the correct account record.

Wallet status check

For DANA, OVO, GoPay or QRIS questions, provide the transaction reference and date rather than your wallet password. We use those details to match payment status without asking for unnecessary credentials.

Receipt question

If a bank transfer or virtual account receipt needs correction, attach the relevant reference through the account support route. We can separate a payment query from a formal request about stored personal data.

SIX DATA CONTROLS

What Our Privacy Process Covers

We treat privacy as an account process you can check, not a vague promise. The controls below explain how we handle sign-in records, wallet references, cookies, retention and requests to change your…

Account details

We use the details you enter for account creation and phone verification to connect you with the correct account. Please keep those details current so a privacy request reaches the right record.

Payment references

DANA, OVO, GoPay, QRIS, bank transfer and virtual account references help us reconcile a transaction. We do not need your wallet PIN or banking password to check a receipt.

Device signals

We may record browser, device and login signals when you use a mobile path or desktop session. These signals help identify unusual account activity and diagnose access issues without reading unrelated device content.

Cookies

Cookies can remember sign-in preferences and help us understand whether a page or account step works correctly. You can manage cookie settings through your browser, although some account functions may then need extra steps.

Retention period

We retain account, support and transaction records only while they serve the stated purpose or an applicable record-keeping need. When retention is no longer required, the data is deleted or de-identified where practical.

Change request

To request access, correction or removal of eligible details, use the account support route and identify the record concerned. We may confirm your account through phone verification before making a change.

Privacy Policy Answers For 5rp

These answers address the questions you may have before opening an account or checking a wallet record. They explain the practical route for privacy requests, cookies, account access and payment references under the 5rp Privacy Policy.

It covers account details, phone verification, device and login signals, cookies, support messages and payment references linked to DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity.

We use your phone number for account identification and a verification step before access or a privacy change. This helps us avoid changing the wrong record and does not require your wallet PIN.

Yes. The Privacy Policy covers the QRIS reference, selected payment rail, transaction date and status details needed to match a receipt. We do not ask for your DANA, OVO or GoPay password.

Use the support route inside your signed-in account and ask for an account data request. Include the registered phone number or relevant reference when requested so we can verify the correct record.

Yes, where local law permits. Send the correction through the account support route, identify the inaccurate field and complete any account verification needed before we update the eligible record.

We keep transaction and support records for the period needed to operate the account, reconcile receipts or meet an applicable legal record requirement. After that, we delete or de-identify them where practical.

Cookies can retain sign-in preferences and help us detect page errors. You can adjust them in your browser, but turning some off may require extra sign-in steps or limit parts of the account path.