Reference

Legal terms for your rajabotak account

rajabotak Legal sets out how we handle account access, wallet records, policy requests and personal data for Indonesia.

Access depends on local lawPhone verification appliesPolicy requests have a clear path
rajabotak Legal terms for your rajabotak account
CONTACT THE TEAM

Three routes for Legal questions

A clear contact route helps when you need to question an access decision, correct an account record or understand a wallet reference. We ask you to include the phone number connected to your account and a short description of the issue, without sending a password or one-time code. The same route can help with policy wording while you are using a mobile browser or desktop device.

Team online

Access clarification

If your account path stops after phone verification, contact us with the displayed message and your registered phone number. We can explain whether the restriction relates to account details, a policy check or access that depends on local law.

Wallet record query

For a DANA, OVO, GoPay or QRIS reference that does not match your account history, send the date, rail name and reference shown to you. We use those details to locate the record without asking for your wallet password.

Policy change request

You can ask us to correct personal details, explain a Legal clause or clarify how long a record is kept. Include the exact account detail or policy wording in your message so our team can respond to the right request.

DATA HANDLING

How we manage policy records

We treat Legal requests as account matters rather than casual chat. Our process checks the account identifier, separates wallet references from authentication secrets and records the action taken by our team.

Account details

We use the account details you submit, including the phone number used for verification, to connect policy requests with the right record. Keep those details accurate; a mismatch can delay an access explanation or a correction request.

Wallet references

DANA, OVO, GoPay and QRIS references are treated as transaction records, not as permission to access your wallet. We do not need your wallet password or one-time code when checking a record connected with your account.

Cookies

Cookies can support account sessions and remember technical choices on your device. Clearing them may sign you out or remove saved settings, but it does not erase records already held for a Legal or account request.

Account security

Phone verification helps us connect access with your account path. Never share a password or one-time code in a support message. If your device changes, sign in through the normal browser path and report suspicious access promptly.

Retention questions

We retain account, payment-reference and support records for the period needed to operate the account, address disputes and meet applicable requirements. Ask our team about a specific record; the answer can depend on its purpose and local law.

Corrections and access

You may ask us to explain, correct or assess data connected with your account where local law permits. State the requested change clearly, and we may ask for account verification before disclosing or editing personal details.

Answers before your account step

These Legal answers focus on the questions we expect before an Indonesian account is opened or used. They cover access, personal data, wallet references, cookies, retention and contact steps. If your situation is specific, use the policy contact route with your registered phone number and the relevant message or reference.

rajabotak Legal covers account eligibility, phone verification, access controls, personal-data handling, cookies, wallet references and policy requests. It also explains how we handle corrections and questions about account records. Access depends on local law, so the applicable outcome can differ by location.

Access is available where local law permits and depends on local law. Before continuing, use the account path shown for your location and provide accurate details for phone verification. If access is restricted, contact us with the displayed message so we can explain the policy reason.

We treat DANA, OVO, GoPay and QRIS names, references and status details as account-related payment records. They should correspond with the account information you provide. We do not ask for a wallet password or one-time code when checking a payment reference.

You can ask us to assess or correct personal details connected with your account where local law permits. Mention the field that is wrong, such as a phone detail or account identifier, and complete any verification we request before we disclose or change the record.

Cookies can support a signed-in session and device settings, but clearing them does not remove records held for account, payment-reference or policy purposes. If you want to ask about a particular cookie or data use, contact us with your device and account context.

We keep records for the time needed to operate the account, address disputes and meet applicable requirements. Retention depends on the record type and its purpose. Ask about a specific account, wallet reference or support case, and we will explain what we can disclose.

Use our policy contact path and include your registered phone number, the exact access message or the relevant DANA, OVO, GoPay, QRIS, bank transfer or virtual account reference. Do not include a password or one-time code. We can then route the question to the right team.