Reference

rajapadi4d Privacy Policy Explained

Your rajapadi4d account data, wallet records and device signals are handled under one clear Privacy Policy, so you can see what we collect and why.

Account dataWallet recordsCookie choicesPhone verification
Explore Our Lobby Read FAQ
rajapadi4d rajapadi4d Privacy Policy Explained
ASK ABOUT YOUR DATA

Get Help With Privacy Requests

A clear support route helps you manage a Privacy Policy request without searching through your account pages.

Account request Send a privacy question through our account support path with your registered contact detail.
Wallet record If a DANA, OVO, GoPay or QRIS entry looks unfamiliar, share its visible reference…
Correction path For a name, phone or contact correction, describe the exact change and the account…
HOW PRIVACY WORKS

What Your Privacy Settings Cover

Our Privacy Policy is practical at account level: it connects data collection to a specific purpose, a visible account action or a defined support request.

Data collection

We collect account contact details, phone verification results, login events and selected payment references because those records help us maintain access and investigate a wallet status question. We aim to collect only what the stated purpose requires.

Cookie controls

Cookies and similar browser storage can remember a session path, language choice or security state. You can adjust browser controls, although removing essential storage may require another phone verification step when you return.

Account security

Phone verification, login records and device signals help us identify unusual account activity. If a sign-in from a new phone interrupts your session, contact support using the registered account detail instead of sharing a password.

Retention timing

We keep account, support and transaction references for as long as needed for service operation, dispute handling, security checks or legal duties. When a record no longer has a valid purpose, our process allows it to be removed or anonymised.

Payment privacy

A DANA, OVO, GoPay or QRIS reference helps us match a payment event to your account, while bank transfer and virtual account records support reconciliation. We do not need your wallet PIN or full banking password for that match.

Change requests

You can ask for access, correction or deletion of eligible personal data through our support path. Include the account contact, request type and relevant date; we may verify ownership before releasing or changing account-linked records.

Privacy Policy Answers For Your Account

These Privacy Policy answers address the account questions you may have before opening access or contacting us. We explain wallet references, cookies, phone verification, deletion requests and local eligibility in direct terms, so you know which details to provide and which secrets to keep private. If your case involves a DANA, OVO, GoPay or QRIS record, include only the visible reference needed for our account check.

It covers account details, phone verification, login and device signals, cookies, support messages, payment references and retention. It also explains why we use each category, how we protect account access and how you can request access, correction or deletion where applicable.

No. We may keep a DANA or QRIS payment reference, status and timing to match an account event, but you should not send us a wallet PIN, password or full banking credential. The same approach applies to OVO, GoPay, bank transfer and virtual account records.

Phone verification helps us confirm that a privacy request comes from the account holder and helps protect account access after a new-device sign-in. If you ask for a correction or data copy, we may use this step before releasing account-linked details.

Contact our account support path and state that you want a data copy under the Privacy Policy. Provide your registered contact detail and the relevant date range if known. We may ask for an ownership check before preparing the records we can release.

Yes, you can request correction or deletion of eligible data through support. Tell us which field or record is concerned, such as a phone detail or payment reference. Some records may need to remain for security, dispute handling or legal duties.

Cookies can retain a session path, language choice or security state on your browser. You can change browser controls, but blocking essential cookies may sign you out or trigger phone verification when you return. Our Privacy Policy explains the purpose of each cookie category.

Yes. Account access and eligibility depends on local law. Where local law permits, we handle Indonesian account requests using the contact and verification details held on the relevant account, while applying the Privacy Policy to the data involved.

Related Pages

rajapadi4d Indonesia FAQ Speed Baccarat Account information bola688