Reference

Privacy Policy for Your rajabotak Account

Our Privacy Policy explains which account, device and wallet details we collect, why we use them and how you can ask about them.

Account clarityWallet recordsCookie choicesContact routes
rajabotak Privacy Policy for Your rajabotak Account
CONTACT THE TEAM

Where To Ask About Privacy

A direct support path helps you deal with a privacy question without guessing which account screen to use. Tell us the phone number or account identifier connected to your request, describe the record you want checked, and avoid sending a password or full wallet credentials. We can then match the request to the correct account activity and explain the next step.

Team online

Account privacy request

Use the account support route when you want to ask what personal details are held, why a phone verification record appears, or which account step is linked to Secure Account Access. We may ask for account details to confirm that the request comes from you.

Wallet record question

For a DANA, OVO, GoPay or QRIS record, send the payment reference and approximate time through support. We can check the status attached to your account without asking you to reveal a wallet password, card secret or complete banking credential.

Correction or deletion

If a profile detail is wrong or you want to ask about removing a record, state the exact change and the account identifier. We assess the request against security, transaction and legal retention needs, then explain what can be changed and why.

SIX DATA CONTROLS

Six Practical Privacy Controls We Use

Privacy is handled through ordinary account operations rather than a vague promise. We separate login checks from wallet references, limit internal access to relevant records and use device signals to investigate unusual…

Collection

We collect what supports an account step: contact details, phone verification, device activity and payment references. A DANA or QRIS status is used to identify a transaction request, not to provide us with your private wallet password.

Cookies

Cookies can remember settings, help maintain a signed-in session and show whether a page has loaded correctly. You can manage cookie controls in your browser, although restricting them may affect Secure Account Access or saved preferences.

Account security

Phone verification and device checks help us compare a new sign-in with earlier account activity. If an unfamiliar device opens the account, we may request an additional check before showing wallet records or account details.

Payment separation

Payment references are kept distinct from sensitive wallet credentials. For GoPay, OVO, bank transfer or virtual account activity, our support team uses the reference, status and time to investigate without requesting a secret PIN.

Retention

We keep account and transaction records only as long as needed for account security, dispute handling, operational checks and legal obligations. When a retention need ends, the relevant record can be removed or made inaccessible under our process.

Your request

You can ask for access, correction, clarification or a deletion assessment through support. Include the account identifier and a precise request; we may verify your identity before discussing records connected with Boxing Title Bet or another account activity.

Privacy Policy Answers For rajabotak

These answers focus on the questions you may have before opening an account or checking a wallet record. They cover the practical route for access requests, cookies, phone verification, payment references and account removal. If your situation is not listed, contact support with the account identifier and the specific Privacy Policy point you want clarified.

The rajabotak Privacy Policy covers account details, phone verification, device activity, cookies, payment references and support requests. It explains why we use each category, how security checks work and how you can ask for access, correction or a deletion assessment.

We use transaction references and payment status for DANA and QRIS requests; we do not ask you to send a wallet password or private PIN. If support needs to check a record, provide the reference and time rather than secret credentials.

Send a support request with the phone number or account identifier connected to your profile and name the records you want to access. We may complete an identity check before responding, so account details are not disclosed to the wrong person.

Yes, you can ask us to correct an inaccurate profile detail or explain why a record is present. State the old and requested new value where relevant. We may retain a transaction reference when security, dispute handling or legal duties require it.

Cookies may keep a session active, remember settings and help us detect whether a page works correctly. Browser controls let you restrict them. Blocking required cookies can interrupt Secure Account Access or remove saved choices on your device.

Retention depends on the purpose of the record, including account security, payment investigation, disputes and legal obligations. DANA, OVO, GoPay, QRIS, bank transfer and virtual account references may therefore remain for different periods.

You can request deletion or ask us to assess which records can be removed. We first verify the request and check whether an account, payment or security record must remain for operational or legal reasons, then explain the result.