Reference

Privacy Policy for Your Indonesia Account

Our Privacy Policy shows exactly how we handle the details connected with your raja padi4d account, from phone verification to wallet records and device sessions.

Clear data purposesCookie choicesAccount request pathIndonesia-focused handling
raja padi4d Privacy Policy for Your Indonesia Account
CONTACT THE TEAM

Privacy Help Along Your Account Path

A direct support route helps you resolve a Privacy Policy question without sending sensitive credentials.

Account help Use the account help path when you need to ask how your phone number, verification result or login record is used. We may request a matching account detail, but we will not ask you to disclose a wallet PIN, password or one-time security code.
Receipt check For a privacy question about DANA, OVO, GoPay or QRIS, include the payment reference and date rather than a full wallet credential. Our team can locate the related record, explain its purpose and tell you whether a correction request is possible.
Policy request If you want a copy, correction or removal request assessed, contact us through the support channel shown in your account area. State the request clearly and use your registered phone number so we can reduce mistaken changes to another account.
DATA HANDLING

What We Keep Secure at raja padi4d

Privacy is managed through practical account controls rather than broad promises. We limit internal access to records by work need, check unusual login or wallet activity, and keep the policy available from…

Account details

We handle the phone number, account identifiers and verification result needed to connect you with the correct account. These details help us confirm ownership when you ask about access or request a change, while payment credentials such as wallet PINs remain outside our support request.

Wallet records

DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity can create reference data in our systems. We use the reference, status and related account details to reconcile a transaction or answer a receipt question, not to request your private wallet password.

Cookies

Cookies can remember a session, language choice or security setting on the device you use. You can clear or restrict them through your browser controls, although doing so may require another account login and can affect the way your Privacy Policy settings are remembered.

Device security

We record practical session signals such as device type, browser details and login time to identify unusual account activity. If a session looks unfamiliar, sign out from the account area, change your password and contact support without sending a screenshot that exposes security codes.

Retention period

We retain account, support and transaction records only for the period needed for account operation, security checks, dispute handling and applicable legal duties. When a record is no longer needed for those purposes, it is removed or separated from active account handling.

Your request

You can ask what account data we hold, request a correction, ask about deletion or object to a particular use where applicable. Send the request through account support with your registered phone number; we may verify ownership before changing or disclosing any record.

Privacy Policy Answers for Your Account

These Privacy Policy answers cover the questions we expect you to ask before opening or using an account. They focus on account details, Indonesian payment references, cookies, device sessions and the request route. If your situation is not listed, contact support from the account area and describe the specific record you want us to examine.

It explains how we handle account details, phone verification, device session signals, cookies, support messages and payment references from DANA, OVO, GoPay, QRIS, bank transfer or virtual account. It also sets out how you can ask for access, correction, deletion or clarification.

We use your phone number to create and identify your account, complete the clear phone verification step before account access and help prevent mistaken changes. If you contact support, the registered number helps us confirm that a request concerns your account rather than someone else’s.

No. Our Privacy Policy concerns the transaction reference, status and account connection needed for reconciliation or support. We do not need your DANA, OVO, GoPay or QRIS PIN, password or one-time security code, so do not send those details in a message.

Open the account help path and send a clear request using your registered phone number. Tell us whether you want a copy, correction or deletion assessment, and include the relevant receipt reference when applicable. We may verify account ownership before responding or making a change.

Cookies can retain a session, language choice or security setting on your device. Your browser lets you clear or restrict them, but that may sign you out or require a fresh account login. The Privacy Policy remains available through the account area after those changes.

We keep account, support and transaction records for the period needed for account operation, security checks, dispute handling and applicable legal duties. The exact period can differ by record type and local requirements. When the purpose ends, we remove or separate the record from active handling.

Account access and eligibility depends on local law. Before you open or use an account, check whether access is permitted where you are located. Our Privacy Policy still explains data handling for an account, and support can clarify a record request without advising you to bypass local requirements.