Reference

rajaburma88 Privacy Policy for Your Account Data

Our Privacy Policy explains how rajaburma88 collects, uses and protects the details connected with your account, device and wallet activity.

Account recordsWallet referencesCookie choicesPolicy requests
rajaburma88 rajaburma88 Privacy Policy for Your Account Data
CONTACT PATHS

Where Privacy Policy Questions Go

A clear contact route helps you ask what we hold, why we use it or how to correct it. Start from the account help area and include the phone number linked to your account, but do not send a password or wallet PIN. For a payment concern, attach the receipt reference so we can separate a DANA, GoPay or bank transfer question from an account-access request.

Team online

Account help desk

Use the account help route for access, phone verification and requests to see or correct personal details. We may ask for an account identifier before discussing records.

Cashier support route

Payment status questions can include a QRIS, OVO, virtual account or bank transfer reference. This lets us trace the relevant record without asking for your wallet password.

Privacy request

Ask for a copy, correction or deletion assessment through support. We verify that the request belongs to you before changing account data or describing stored records.

HANDLING DETAILS

What Our Privacy Process Covers

We separate account operation from unnecessary exposure of your payment credentials. A phone sign-in, a mobile browser session and a desktop session can create different technical records, so…

Data collection

We collect account details, phone verification results, support messages and transaction references needed to connect your account with wallet or…

Cookie controls

Cookies and similar browser records can keep a session working and help us detect unusual sign-in activity.

Account security

Phone verification, sign-in records and device signals help us check account access.

Retention periods

We keep each record for the period needed for its stated purpose, account servicing, dispute checks or legal duties.

Who to contact

Our account help route handles privacy questions, including access, correction, deletion assessment and the reason a record is used.

Change requests

To request a correction, provide the old and new detail with your account reference.

Privacy Policy Answers for Indonesian Accounts

These Privacy Policy answers focus on the records you are most likely to ask about before opening or using an account. We explain the account step, wallet references, device behaviour and contact route in plain terms, with access remaining subject to local law. If your case concerns a specific receipt or phone number, include that detail when contacting us.

It covers account details, phone verification, device and browser records, cookies, support messages and payment references connected with DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity.

Phone verification helps connect account access to the contact detail you supplied and supports checks when a sign-in or wallet status needs investigation. We do not need your wallet PIN.

Yes. The Privacy Policy includes payment references and status details needed to match an account with DANA or QRIS activity. It does not require us to collect your private wallet password.

We may record device type, browser signals, session times and security events from a phone or desktop. These details help identify unusual access and troubleshoot account steps without reading unrelated device content.

Send a request through the account help route with your account identifier and the records you want addressed. We verify ownership before describing, copying or changing personal data.

You can request a correction or ask us to assess deletion through support. We check the request against account and legal needs, then explain which action can proceed and why.

The policy is written for access from Indonesia, but eligibility and certain data rights depend on local law. We may use the applicable rule for your location when answering a request.