Reference

radenjp Privacy Policy for Your Account

Your account details, phone verification and wallet references are explained in the radenjp Privacy Policy, so you can see what we collect and why before opening an account.

Account dataWallet referencesDevice sessionsLocal-law access
radenjp radenjp Privacy Policy for Your Account
CONTACT ROUTE

Where to Ask About Your Privacy

A direct support request is the quickest way to ask what account data we hold or to report a wallet reference that does not match your record.

Access request Ask us to confirm the account data linked to your phone verification. We may request an account identifier or another account step before releasing details to the person making the request.
Wallet query For DANA, OVO, GoPay or QRIS references, send the transaction date and reference shown on your receipt. We use those details to trace status without asking for your wallet password.
Correction request If a profile detail or contact record is incorrect, contact support through the logged-in account path. We check the request against your account before changing the stored record.
SECURITY DETAIL

Privacy Controls for Login and Wallets

We treat privacy as an account process rather than a statement hidden from view. The controls below explain how we handle login events, mobile browsing, wallet references, cookies and requests to change…

Data we collect

We collect account details, phone-verification results, login timestamps, device signals, support messages and transaction references. We use each category for account operation, security checks, payment matching or a reply to your request.

Cookies and sessions

Cookies can keep your login session active and retain selected security settings on a mobile browser or desktop. You can manage browser storage, although clearing it may require another account verification step.

Login protection

Phone verification helps connect an account request to the right account holder. We record the verification result and relevant access events, while you should keep passwords and one-time codes private.

Retention periods

We retain account, security and transaction references only for the period needed for service operation, dispute checks and legal duties. When no valid purpose remains, records are deleted or made non-identifying.

Changes to your record

You can ask us to correct an inaccurate contact or account detail through the logged-in support route. We verify ownership first, then update the record or explain why a specific field must remain unchanged.

Who receives data

Payment and technical partners may receive the limited reference needed to process a request, such as a QRIS status or bank-transfer match. We do not ask these partners for your private wallet password.

Privacy Policy Questions for Indonesia Accounts

These answers address the practical searches you may make before opening an account or sending a privacy request. They cover the radenjp Privacy Policy, local wallet references, device sessions, account verification and the route for correcting your stored details.

It covers account details, phone verification, login and device records, cookies, support messages, wallet references and retention. It also explains your route for access, correction and privacy questions.

No. We use the payment status, receipt details and reference needed to match an account action. We do not ask for or store your DANA, OVO, GoPay or QRIS wallet password.

We may collect the contact details you submit, the phone-verification result, login records and device signals connected with the account step. The Privacy Policy explains the purpose for each category.

Use the support contact shown after login and ask for an access request. Include your account identifier, not your password or one-time code, so we can verify ownership before responding.

Yes. Send a correction request through the logged-in support path and identify the field that needs changing. We check the request against your account, then update it or explain the limitation.

Cookies can retain a session and selected security choices on your mobile browser. Clearing browser storage may end that session and require phone verification again when you access the account.

The policy describes how we handle data for supported account activity in Indonesia. Access depends on local law, and you should check the current account path before submitting personal details.