Reference

rene4d Privacy Policy Explained

rene4d Privacy Policy explains how we collect, use and protect the account, wallet and device details you provide when you access our services.

Account clarityWallet dataCookie choicesPolicy requests
rene4d rene4d Privacy Policy Explained
CONTACT YOUR WAY

Privacy Help When Account Status Stalls

A clear support path matters when you need to ask about the Privacy Policy, correct account data or understand a wallet status.

Policy questions Send a Privacy Policy question through our support desk and tell us which section…
Wallet status For DANA, OVO, GoPay or QRIS records, include the payment reference and account phone…
Account corrections Ask us to correct an inaccurate name, phone detail or contact record through support.
DATA HANDLING

Six Privacy Controls Behind Your Account

We keep the Privacy Policy practical by linking each data practice to an account action you can recognise.

Account details

We handle details such as your account contact and phone verification status to create access, confirm ownership and respond to account requests. We do not need your password in a support message, so keep it private.

Payment references

A DANA, OVO, GoPay or QRIS reference can identify a transaction status without revealing more wallet content than needed. Bank transfer and virtual account records support matching, reconciliation and payment enquiries.

Device signals

Browser, device and login signals can help us detect unusual access and protect your account. Our mobile path may record technical details needed to keep the session connected from login to the lobby.

Cookies

Necessary cookies keep sessions and security controls working, while preference cookies help remember choices. You can adjust browser settings, but blocking required cookies may interrupt phone verification or account access.

Retention

We retain account, payment and support records for the period needed for service delivery, security checks, dispute handling and legal duties. When a record is no longer needed, our handling follows the applicable retention process.

Your request

You can ask about the data connected to your account, request a correction or question a processing purpose through support. We verify ownership first, then explain what action is available under local requirements.

Privacy Policy Answers for Indonesia

These Privacy Policy answers address the account and payment questions we expect from Indonesian customers before they open an account. Each answer points to a practical route, whether you are checking cookies on a phone, asking about a QRIS reference or requesting a correction. Access remains where local law permits, and account-specific replies may require phone verification.

The rene4d Privacy Policy covers account details, phone verification, login and device signals, cookies, support messages, payment references and retention. It explains why we use each category, how we protect account access and how you can ask about, correct or otherwise request action on relevant data.

Yes. The Privacy Policy explains that DANA, OVO, GoPay and QRIS references can help us match a transaction status to your account. We use the reference needed for that task and may ask for ownership confirmation before discussing payment-linked account details.

Contact our support desk through the account-linked route and describe the data you want corrected. Include your account contact and a clear explanation, but never send your password. We may complete phone verification or another ownership check before changing the record.

On mobile, necessary cookies can keep your login session, security checks and account path connected. Preference cookies may remember selected settings. You can change cookie controls in your browser, though blocking required cookies can interrupt phone verification or access to account pages.

We keep account, payment and support records for as long as needed for service delivery, account security, transaction reconciliation, dispute handling and legal duties. The period can differ by record type. You can ask support which retention purpose relates to your request.

Yes. Send a request through the account-linked support route and identify the account contact used for access. We verify ownership before describing linked data, which may include phone status, login signals, cookie preferences, support history and payment references.

Yes. Account access and any related service depend on local law, or are available where local law permits. If a location or eligibility rule affects your request, we will explain the relevant limitation through support rather than asking you to bypass it.