Reference

rindubola Privacy Policy for Your Account

Our Privacy Policy explains how rindubola handles the account, device and wallet details you provide when you open an account or access the lobby.

Account dataWallet recordsCookie choicesAccess requests
rindubola rindubola Privacy Policy for Your Account
PRIVACY HELP

Contact Us About Privacy Requests

A clear support path matters when your account record or wallet status needs attention.

Account request Ask us to access, correct or clarify personal data linked to your rindubola account.
Wallet question For DANA, OVO, GoPay or QRIS references, tell us which transaction status needs checking.
Security concern If a sign-in or device record looks unfamiliar, contact support through your account path…
DATA CONTROLS

See Your Data Controls in Practice

Privacy choices work best when each account step has a clear reason behind it. We separate contact details, sign-in records, device signals and payment references, then use each…

Data we receive

We can receive registration details, verification results, sign-in timestamps, device characteristics and payment references.

Cookie choices

Cookies and similar device storage can remember a session and support account security.

Account protection

We use contact verification, session controls and device signals to reduce account misuse.

Retention approach

We keep records for as long as needed for account security, payment reconciliation, dispute handling or a legal duty.

Request a change

You can ask us to access or correct eligible data by using the account support path.

Policy contact

Privacy questions should name the account step involved, whether login, verification or wallet status.

Find Privacy Policy Answers Quickly

These Privacy Policy questions address the account situations you are most likely to encounter, from opening access on a mobile device to checking a wallet reference. We keep the answers focused on personal data and your available request path. If your question concerns a record not listed here, use the support route connected to your account.

It covers account details, verification records, device and sign-in data, cookie choices, payment references, retention and requests to access or correct eligible personal data.

We use registration and verification details to provide account access, protect sign-in activity and connect a payment status to the correct account. Access depends on local law.

Yes. The policy covers DANA, OVO, GoPay and QRIS references used to match payment status. We do not need your wallet password to check that account-related status.

You can request a correction through the account support path. State which record is wrong and provide the registered contact detail; we may verify your identity before changing it.

Cookies or device storage may preserve a session and support sign-in security on your phone. Browser settings let you restrict them, though some account access steps may then require repetition.

We retain records while they support account security, payment reconciliation, dispute handling or a legal duty. Retention can end when those purposes no longer require the record.

Use the support route linked to your account and describe the request, such as access, correction or deletion of eligible data. We may ask for verification before discussing personal records.