Reference

rajarungkat Privacy Policy for Indonesia

The rajarungkat Privacy Policy shows how we collect, use, store and protect details linked to your account, including phone verification, device access and wallet records.

Clear data purposesWallet record detailsAccount access choicesPolicy contact path
rajarungkat rajarungkat Privacy Policy for Indonesia
CONTACT ROUTES

Get Privacy Help Beside Your Account

A clear support route matters when a privacy request meets an account or wallet question. We ask you to use the support link inside your rajarungkat account and include the phone number connected to your profile, the relevant request and any payment reference you want checked. Do not send a wallet password or full security code. We use the account path to confirm ownership before changing records or discussing access.

Team online

Account support link

Open the support link from your signed-in account and select the privacy subject. Include your registered phone number and the data request you want us to assess, so we can match the message to the correct account without asking you to reveal a wallet password.

Cashier status path

If your request concerns DANA, OVO, GoPay, QRIS or bank transfer records, mention the cashier reference and date shown in your account. We use those details to locate the relevant entry while limiting exposure of payment credentials and unrelated account activity.

Device access check

When a privacy concern follows a phone or browser change, tell us the device path you used, such as mobile browser or desktop browser. We may ask for an account step to confirm ownership before correcting data or closing an access request.

DATA PRACTICES

What We Do With Your Account Details

We keep the Privacy Policy practical by linking each data purpose to an account action you can recognise.

Phone verification

We use the phone verification result to connect an account request with the correct profile and reduce mistaken changes.

Browser cookies

Our cookies can remember a signed-in session, language choice or security preference on the device you use.

Security events

We record selected login, browser and device events to investigate unusual access and protect your account.

Payment references

For DANA, OVO, GoPay, QRIS, virtual account and bank transfer activity, we may keep reference numbers, status details and timestamps.

Data retention

We assess retention by purpose: account operation, security checks, payment disputes or a legal requirement.

Change requests

You can ask us to correct an inaccurate phone detail, clarify a stored record or request access to personal data…

Privacy Policy Answers for rajarungkat

These Privacy Policy answers address the account questions we expect before registration or a data request. We cover wallet references, cookies, device access, correction requests and local eligibility in plain language. If your situation is not listed, use the signed-in support path with the smallest amount of personal detail needed to identify your account.

The rajarungkat Privacy Policy covers account details, phone verification, login and device events, cookies, payment references, support messages and retention. It explains why we use each category, how we protect access and how you can ask about, correct or request a copy of your personal data.

No. For DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity, we use transaction references, status details and timestamps where needed. The Privacy Policy does not require you to send a wallet password or full security code through our support path.

We collect selected device and browser signals to recognise account access, investigate unusual login events and keep a session working. The Privacy Policy limits this use to stated operational and security purposes. You can clear cookies in your browser, but another account check may follow.

Use the support link inside your signed-in account and describe the copy or correction you need. Include your registered phone number, but not a wallet password. We may verify ownership before responding, then explain the records covered, any limits and the next step.

We retain account, payment and security records for the operational, dispute, security or legal purpose described in the Privacy Policy. We assess whether storage is still needed and remove or separate records when that purpose ends, subject to any period required where local law permits.

Yes. The Privacy Policy explains cookies that support a session, language choice or security preference. You can manage or clear them through your phone or browser settings. If a session is cleared, we may request phone verification or another account access step.

Yes. Account access and related data processing depends on local law. Where local law permits, we provide the policy details and support route relevant to your request. If a legal restriction applies, we explain the affected action and the available way to contact us.