Reference

radenjitu Privacy Policy for Your Account

Our Privacy Policy explains what radenjitu collects when you create an account, sign in from a mobile device, or use DANA and QRIS at the cashier.

Account recordsWallet activityDevice choicesPolicy requests
radenjitu radenjitu Privacy Policy for Your Account
HELP WITH REQUESTS

Three Routes for Privacy Support

A clear contact path helps you resolve a data question without repeating your account story.

Account access Use the support route after login to ask about stored contact details, phone verification…
Wallet records For DANA, OVO, GoPay, QRIS, bank transfer, or virtual account records, provide the payment…
Privacy request Ask for access, correction, restriction, or removal of eligible data through the policy contact…
DATA HANDLING

Six Privacy Controls Behind Your Login

We handle this policy area through practical controls rather than broad promises. Your account path, mobile browser, wallet selection, and support request each create different records, so we…

Account creation

We collect the details needed to open your account and complete phone verification before access.

Mobile device data

When you sign in on a phone, we may record device and browser details for session continuity, fraud checks, and…

Cookies and storage

Cookies or similar storage can remember a sign-in state, language setting, and policy preference.

Payment matching

A DANA, OVO, GoPay, QRIS, bank transfer, or virtual account reference helps us match a receipt with your account.

Retention period

We retain records only for the account, support, security, or legal purpose that requires them.

Change requests

You can request a copy, correction, restriction, or removal of eligible data through support.

Privacy Policy Answers for radenjitu

These Privacy Policy answers focus on the records you are most likely to ask about before opening an account. They cover phone verification, mobile access, wallet references, cookies, retention, and correction requests. If your situation is not listed, use the support route after login and describe the exact account step, payment reference, or device action involved.

It covers account details, phone verification, sign-in and device records, cookies, support messages, and payment references linked to DANA, OVO, GoPay, QRIS, bank transfer, or a virtual account.

Phone verification confirms that the account access request belongs to you and helps us protect account records. We use the verification result for access and security purposes, not as a wallet password.

Yes. It explains that mobile browser and device details may support session continuity, fraud checks, and display settings. You can manage browser storage through your phone settings, with some account effects.

We use payment references, dates, and status details to match a receipt with your account and answer support questions. We do not request the password or access code held by your wallet provider.

Yes. Send a correction request through the policy contact path after login, identify the affected account field, and complete ownership checks. We will explain the outcome or any reason a record remains.

Retention depends on why the record exists, your account status, unresolved support matters, and applicable legal duties. When the purpose ends, we follow a deletion or anonymisation process.

You may request access, a copy, restriction, or removal of eligible data through support. Where local law permits, we assess the request after account verification and explain any limits.