Reference

rajabandot no 1 Privacy Policy

Our rajabandot no 1 Privacy Policy explains what we collect when you open an account, verify your phone, use DANA or QRIS, and reach the lobby from an…

Account dataWallet recordsCookie choicesAccess requests
rajabandot no 1 rajabandot no 1 Privacy Policy
CONTACT ROUTES

Get Privacy Help Beside Your Account

A clear contact path helps when a privacy question appears beside a login or wallet record. We ask you to send the account phone number, the subject of your request and any relevant DANA, OVO, GoPay or QRIS reference through the support route connected to your account. Do not send a wallet password or full payment credentials. We use the submitted details only to identify the request and respond to you.

Team online

Account access

If you cannot reach your account, use the account help route and state that your request concerns the Privacy Policy. We may ask for phone verification before discussing personal records, so another person cannot obtain account details.

Wallet reference

For a DANA, OVO, GoPay or QRIS question, include the visible transaction reference and date, not your wallet password. This lets us locate the relevant record while keeping sensitive wallet credentials outside the support request.

Correction request

To request a change, describe the exact account field that needs correction and the reason. We compare the request with your verified phone details, then explain whether the change can be made under local law.

DATA PRACTICE

What Our Privacy Policy Does With Data

We handle policy requests through the same account path you use to reach the Indonesia Mobile Lobby 504 from a phone or desktop browser.

Collection

We collect details you provide during account creation, including your phone number, plus technical browser and device signals needed for login sessions. If you use QRIS or a local wallet, we also receive the payment reference and status connected to that request.

Cookies

Cookies can keep your session path available when you move from login to the lobby on an Android browser or desktop. You can clear browser cookies, but doing so may remove saved session choices and require phone verification again.

Account security

Phone verification is used before account access and before we discuss personal records with you. We do not ask for your DANA, OVO, GoPay or QRIS wallet password, and we use account checks to reduce mistaken disclosure.

Retention

We keep identity, support and payment-reference records for the time needed to operate the requested account service, resolve disputes, detect misuse and meet duties that depend on local law. When a purpose ends, handling follows our deletion process.

Your requests

You can ask what personal data we hold, request a correction, question a wallet reference or ask about deletion. Include your verified phone details and a precise request so we can respond without exposing another account holder's records.

Policy contact

Use the support route connected to your account for Privacy Policy questions. We may request the account step, device path or transaction reference involved, while keeping the conversation focused on your data and not unrelated lobby activity.

Privacy Policy Answers For Your Account

These Privacy Policy answers cover the searches we expect before account access: what we collect, why wallet references appear, how cookies work and how to request a change. We keep the answers tied to rajabandot no 1 account steps, Indonesian payment rails and the browser paths you actually use. If your question is not listed, send the request through account support with only the necessary details.

The rajabandot no 1 Privacy Policy covers account details, phone verification, browser and device signals, cookies, support messages and payment references from DANA, OVO, GoPay or QRIS. It also explains access, correction, retention and deletion requests where local law permits.

We use your phone number to create and verify the account path before discussing personal records. This helps us distinguish your request from another account. We do not use phone verification to obtain your wallet password or full wallet credentials.

No. Our payment records contain the reference and status needed to match a DANA or QRIS request, rather than your wallet password. For a payment question, send the visible reference and date through support, while keeping login credentials private.

Yes. Send a correction request through the account support route and name the exact field that is wrong. We may ask for phone verification before changing it, then explain the result and any restriction that depends on local law.

Cookies can preserve a browser session while you move from login to the lobby on Android or desktop. Clearing them may remove saved choices and trigger phone verification again. Our Privacy Policy treats cookie records as technical session data, not wallet credentials.

We keep records for the purpose that required them, such as account support, payment matching, misuse checks, disputes or legal duties. The period can differ by record type and depends on local law. You can ask support which category applies.

Use the support route connected to your account and state that the request concerns the Privacy Policy. Include your verified phone details and only the relevant DANA, OVO, GoPay or QRIS reference. Never include a wallet password or full payment credentials.