Reference

Privacy Policy for Your rajabet Account

Our Privacy Policy explains how we collect, use and protect details connected with your rajabet account, from phone verification through wallet activity.

Clear data purposesWallet status contextAccount access controlsCookie choices
rajabet Privacy Policy for Your rajabet Account
CONTACT ROUTES

Privacy Help Beside Account Support

A clear contact route helps you ask about personal data without explaining your whole account history.

Account privacy request Use the account support path to ask what personal details are held, why they…
Wallet record question If your request concerns a DANA, OVO, GoPay or QRIS record, include the relevant…
Security concern Tell us promptly if an account detail, phone verification event or device session looks…
DATA PRACTICES

How rajabet Handles Privacy Details

Our privacy process follows the points you encounter while using the service: account creation, phone verification, wallet checks and support contact.

Account collection

We collect details needed to create and maintain your account, including contact data supplied during the account step. Phone verification helps us match an access request with the account record before sensitive details are discussed.

Payment references

Wallet and transfer records help us match a cashier event with your account. For DANA, OVO, GoPay, QRIS, virtual account or bank transfer questions, we use the transaction reference rather than requesting your private wallet credentials.

Device sessions

The mobile or desktop browser you use can produce session and security records. These details help us detect unusual sign-ins and keep the path from phone verification to the lobby associated with the correct account.

Cookies and settings

Cookies can retain session settings and support basic account navigation. You may adjust cookie controls in your browser, although blocking required cookies can affect login, phone verification or access to account pages.

Retention approach

We keep personal and transaction records for as long as needed for account operation, security checks or applicable legal duties. When a record is no longer needed for those purposes, our handling process addresses its removal or restriction.

Change requests

You can ask us to correct account details, explain a data use or clarify a retention question through account support. We confirm ownership first, then assess the request against account security and local legal requirements.

Privacy Policy Answers for Indonesia

These Privacy Policy answers address the account questions you are most likely to ask before opening access or sending a support request. We keep each answer connected to the actual rajabet account path, including phone verification, mobile sessions and local wallet records. If your situation needs a detailed check, contact account support with the phone number linked to your account. Access depends on local law and is available where local law permits.

The rajabet Privacy Policy covers account details, phone verification, device sessions, cookies, wallet references and support requests. It explains why we use each category, how we protect account access and when records may be retained for security, service operation or legal needs.

We may collect details you enter during account creation, such as contact data and phone verification results. We can also record device, browser and session events, plus references for DANA, OVO, GoPay, QRIS, virtual account or bank transfer activity.

Phone verification connects an access request with the correct account and helps us respond safely to privacy questions. Before discussing account-linked data or changing details, we may confirm the phone number associated with your rajabet account.

The policy treats DANA and QRIS references as account-related transaction data used to match a cashier event, investigate status and answer receipt questions. We do not need your wallet PIN or full private wallet credentials to check that reference.

Yes. Send a correction request through account support and describe the detail that needs updating. We confirm account ownership before making changes, and we assess the request against security controls, operational needs and applicable local requirements.

We retain records while they support account operation, security review or applicable legal duties. The exact period can depend on the record type and local requirements. When a record no longer serves those purposes, our handling process addresses deletion or restriction.

Use the account support path and state that your request concerns the Privacy Policy. Include your linked phone number, the right or clarification you seek and any relevant receipt reference, while keeping passwords, PINs and secret codes out of the message.