Reference

rajabom Privacy Policy for Your Account Data

Our Privacy Policy explains how we collect, use and protect the details connected with your rajabom account, including phone verification, device access and wallet status.

Account clarityWallet recordsDevice accessPolicy requests
rajabom rajabom Privacy Policy for Your Account Data
CONTACT ROUTES

Get Help With Privacy Requests

A clear support path matters when you need to ask about a stored detail, correct an account record or question a wallet reference.

Account access If phone verification or sign-in creates a privacy question, use the account help route…
Wallet records For DANA, OVO, GoPay or QRIS questions, attach the payment reference shown in your…
Correction requests Ask us to correct an inaccurate profile detail by naming the field and the…
SIX DATA CHECKS

Six Checks Behind Our Data Handling

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

Account details

We use your phone number and account details to identify the profile during access checks. Phone verification comes before account access, helping us avoid discussing private records with the wrong person.

Device signals

A mobile or desktop sign-in can create device and session signals. We use them to maintain the requested session and examine unusual access, not to request access to unrelated files.

Cookies

Cookies can remember session choices and help the account page load the right status. You can manage cookies through your browser settings, though changing them may affect sign-in behaviour.

Wallet matching

Payment references from DANA, OVO, GoPay, QRIS, bank transfer or virtual account are matched with the account request they belong to. This supports receipt checks without storing your wallet password.

Security records

We retain access and verification records for account protection, including the event needed to investigate a disputed sign-in. We do not ask you to send a password through support.

Retention changes

We keep records only for the period needed for the stated account, payment or security purpose and then remove or separate them when appropriate. Ask support which record your request concerns.

Privacy Policy Questions Before Account Access

These answers focus on the searches we hear before an account is opened: what we collect, how payment references work, how to request a change and what access wording applies in Indonesia. If your question is not listed, send the account and receipt details through the support route.

It covers account details, phone verification, device and session signals, cookies, payment references, security records, retention and requests to access or correct data connected with your rajabom account.

We use phone verification before account access to connect the request with the correct profile. It also helps support check an account issue without relying on a password or an unverified contact.

Yes. The Privacy Policy covers references and status details created when you use DANA, QRIS, OVO, GoPay, bank transfer or virtual account routes, including receipt checks linked to your account.

You can ask support about the account records connected with your phone number. Include the relevant request or receipt reference, and we may complete an identity check before releasing or discussing private data.

Send a correction request through the account help route, identify the field that needs attention and provide the linked phone number. We may ask for phone verification before changing the record.

We retain records for the account, payment or security purpose described in the Privacy Policy, then remove or separate them when appropriate. Support can identify the purpose connected with your request.

Account access and eligibility depends on local law. The Privacy Policy applies where local law permits, so check the access screen and contact support if your location or account status is unclear.