Reference

Read the rajabola2 Privacy Policy

The rajabola2 Privacy Policy explains what we collect when you open an account, sign in on mobile, or connect DANA, OVO, GoPay and QRIS.

Clear data purposesWallet details explainedAccount request path

Explore Our Lobby Read FAQ

Check how wallet data is handled

rajabola2 Service availability depends on jurisdiction. Users are responsible for checking local law before access.

Our Privacy Policy covers details supplied during account creation, phone verification, sign-in, payment selection and support contact. When you choose DANA, OVO, GoPay or QRIS, we may handle transaction references, status results and receipt details needed to match an account request; bank transfer and virtual account

1
records can include the selected BCA, BRI, Mandiri or BNI route. We use these records for account administration, payment reconciliation, security checks and required legal requests. Device type, browser signals and sign-in events help us identify unusual access, while cookies help retain necessary session settings. We
2
keep records only for the period needed for these purposes or required by applicable rules. You may ask about access, correction or deletion through our support path, subject to verification and where local law permits. The current policy applies to your use of rajabola2 services from
3
Indonesia and may be updated when our data practices change.

Service availability depends on jurisdiction. Users are responsible for checking local law before access.

POLICY HELP DESK

Contact us about policy questions

A clear contact route matters when you want to understand a record or correct an account detail.

DATA CONTROL STEPS

See how account data stays controlled

We handle this policy area through practical account controls rather than vague promises. Phone verification connects a request to the right profile, device and sign-in records help us check unusual access, and…

Account creation

We collect the details needed to open and maintain your account, then use phone verification before account access. This reduces confusion when a support request involves more than one profile.

Device signals

Your browser, device type and sign-in events may be recorded for security checks. These signals help us investigate an access concern without treating them as wallet credentials.

Cookies

Cookies can retain session settings and help the account path work between login and the lobby. You can manage browser cookie settings, though some account functions may then need another sign-in.

Payment references

DANA, OVO, GoPay, QRIS, bank transfer and virtual account entries are handled as transaction references and status records. We do not ask for your wallet password through support.

Retention period

We retain account, security and payment records for the time needed to provide the requested service, resolve disputes, prevent misuse or meet applicable legal duties.

Your requests

You can ask about access, correction, deletion or processing concerns through the account support path. We verify the request first and respond according to applicable rules.

Find answers about Privacy Policy

These questions cover the account, device and wallet points we receive most often. If your situation is not listed, contact us from the signed-in account path with the relevant reference, and we will check the request under the Privacy Policy.

It covers account creation, phone verification, sign-in activity, device signals, cookies, support messages and payment references connected with DANA, OVO, GoPay, QRIS, bank transfer or virtual account use.

Phone verification helps connect account access and policy requests to the correct profile. We may use it before discussing personal records or changing account details, subject to applicable rules.

Yes. The Privacy Policy covers QRIS, DANA, OVO and GoPay transaction references, status results and receipt details used to match a payment event with your account.

You can submit an access request through the signed-in support path. We verify your identity before responding and provide the available records where local law permits and no exception applies.

Send a correction request through account support and identify the detail that needs changing. We may request phone verification or another account check before applying an approved update.

We keep records for the period needed for account administration, security checks, payment reconciliation, dispute handling or legal duties. The period can differ by record type and applicable rule.

You may ask for deletion through the account support path. We assess the request under the Privacy Policy, verify ownership and explain if a record must remain for security or legal reasons.

Read the rajabola2 Privacy Policy

Contact us about policy questions

See how account data stays controlled

Account creation

Device signals

Cookies

Payment references

Retention period

Your requests

Find answers about Privacy Policy

01 What does the rajabola2 Privacy Policy cover?

02 Why does rajabola2 need phone verification?

03 Does the Privacy Policy cover QRIS and wallet records?

04 Can I ask for a copy of my account data?

05 How do I correct information held by rajabola2?

06 How long does rajabola2 retain personal data?

07 Where local law permits, can I request deletion?

Related Pages