Casino / Sports
This page explains exactly what data rajabandott collects when you use your account, how we store it, and the choices you have over it. Every section here is specific to account activity on rajabandott — including how your OVO, GoPay, and QRIS wallet details are handled — and applies where local law permits access.
When you open an account on rajabandott, we collect the information you provide during registration — your name, contact details, and the e-wallet identifiers you connect for transactions, such as OVO account numbers, GoPay linked phone numbers, or QRIS scan references. We also record session data generated when you log in from a browser or the mobile app: device type, IP address, and interaction timestamps. This data exists to verify your identity, process your wallet transactions accurately, and keep your account secure against unauthorised access. We do not sell your personal data to third parties. Data linked to your OVO, GoPay, or QRIS payment activity is retained only as long as your account remains active or as required by the applicable data-retention obligations in your eligible region. You may request a summary of what we hold at any point by contacting our support channel directly. Access to this policy and its scope depends on local law and is available where local law permits.
OVO wallet identifiers linked to your account are stored for transaction verification only, not shared with third parties.
GoPay phone references connected during deposit are retained for reconciliation and removed when the account is closed.
QRIS scan data associated with a transaction is logged against your account record for audit purposes only.
Not every digital touchpoint you encounter falls under this policy. The table below distinguishes what rajabandott's Privacy Policy directly governs from what sits outside its reach. Understanding this boundary helps you know where to direct a data question and where to look for a third-party provider's own terms.
Login activity, session records, and account-level preferences you set inside rajabandott are fully within scope. We hold these records and you may request them through our support route.
Transaction references generated when you use OVO, GoPay, or QRIS are covered. However, the payment provider's own data practices are governed by that provider's separate policy, not ours.
Interaction data collected while you browse game lobbies or navigate account pages is within scope. We use it for session integrity — not for building external advertising profiles.
Links or embedded content originating from external providers — including game studios — are outside this policy's scope. Follow those providers' own privacy terms for data they collect independently.
Holding an account with rajabandott means you have concrete actions available regarding the data we keep. You are not limited to reading this page — you can act on it. The account dashboard, accessible after login, shows the profile details we currently hold on record, including the contact information and wallet identifiers attached to your account. If any detail is incorrect or outdated, you can update it directly within the account settings page under the profile section. For data you cannot edit through the dashboard — such as historical transaction records tied to an OVO or GoPay reference — you may raise a correction or deletion request via our support contact. We aim to respond to data requests in a reasonable timeframe; the current status of your request is shown in your account dashboard after login. If you have a question about what a specific data field means or why it is held, reaching out to our support team is the most direct route to a clear answer.
Log in and open the profile section of your account dashboard to see the data we currently hold, including contact details and linked wallet identifiers.
Outdated name, email, or phone fields can be updated directly in account settings. Changes take effect in your account record after you save and confirm.
For records you cannot edit yourself — such as past transaction logs connected to OVO or GoPay — contact support with your account reference and the specific detail you want addressed.
If you wish to close your account and understand the data implications, contact support directly. We will walk through the retention obligations that apply in your eligible region.
If a section of this policy raises a question you cannot resolve by reading it, the fastest route is direct contact. We have dedicated contact paths for data-related enquiries — separate from general account help — so your question lands in the right place without being routed through unrelated queues.
Open the live chat widget from your account dashboard to raise a privacy or data question in real time. Identify your query as a data enquiry when the chat opens so the agent can respond with the correct context.
For formal data access or deletion requests, send an email from your registered account address. Include your account reference number and a clear description of the data you are asking about.
Minor corrections — contact details, linked phone numbers for GoPay or OVO — can be handled entirely inside your account settings without contacting support. Log in, navigate to profile, and follow the edit fields shown.
Handling your account data carefully is not an optional extra — it is a condition of operating the platform responsibly. This section outlines the specific practices we follow so you can verify the approach, not just take our word for it.
We use session cookies to keep you logged in across pages and to record how your account interacts with the platform. You can clear cookies from your browser at any time; doing so will end your active session and may require you to log in again.
Login credentials and wallet identifiers — including those tied to OVO, GoPay, and QRIS — are stored in encrypted form. We do not display full wallet numbers in your account view; only masked references are shown.
Active account records are retained for as long as your account remains open. On account closure, data is held only for the period required by applicable obligations in your eligible region, after which it is scheduled for deletion.
When we make a material change to this policy, we post an update notice on this page. We do not send automatic push alerts, so checking this page after login is the way to stay current with the version in effect.
These are the data and privacy questions we receive most often from account holders. Each answer is specific to how rajabandott handles information — not a generic legal summary.
We collect the name, contact details, and e-wallet references you provide at registration — for example, the phone number linked to your GoPay or OVO account. We also record device and session data generated when you log in, used only for account security and transaction verification.
No. Wallet identifiers connected to your account — whether OVO, GoPay, or QRIS scan references — are used only to process your own transactions and are not sold or passed to external marketing parties. Payment providers process their side independently under their own terms.
Log in and open the profile section of your account dashboard. The fields shown there reflect the data we hold on record. For data that does not appear in the dashboard — such as historical transaction logs — contact support with your account reference and we will provide a summary.
Yes. Send a deletion request through the email contact route using your registered address. We will confirm what data can be deleted immediately and what must be retained for the period required by applicable obligations in your eligible region before deletion is completed.
No. Game studios — including PG Soft, Habanero, and others whose titles appear in the lobby — operate under their own data practices. Our policy covers only what we collect through the account and platform layer. For studio-level data, check that provider's own terms.
We post an update notice directly on this page when a material change is made. There is no scheduled change date; the current version in effect is always shown here. Check this page after login to confirm you are reading the latest version.