LEGAL REFERENCE

Privacy Policy for your account

rajabandoy brings casino tables, slot rooms and sportsbook access into one Indonesia account, and this Privacy Policy explains how we handle your account data. Open your account in...

Account dataPrivacy choicesIndonesia accessQRIS context
View Game Library Read FAQ
rajabandoy Privacy Policy for your account

Our privacy posture in Indonesia

This Privacy Policy sets our posture for rajabandoy accounts in Indonesia. We collect only the personal data needed to create your account, keep your session working, answer support requests, process identity or safety checks, and connect transaction references from DANA, OVO, GoPay, QRIS or bank rails where local law permits. We use that data to run the service you ask for, prevent

account misuse, record consent choices, and improve policy clarity. We do not sell your personal data. Some vendors may process data for hosting, fraud screening, analytics, messaging, or payment routing, under contract and only for our stated purposes. Access may vary by supported regions, and you can contact us to ask for access, correction, or deletion where available.

Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.

PLAYER SUPPORT

Contact paths for privacy requests

We keep privacy contact paths close to your account flow, so you do not need to search around the site. Use the...

Account privacy desk Ask us about access, correction, deletion, consent status...
Transaction reference help If your privacy request involves DANA, OVO, GoPay...
Security message channel Report unusual account activity, unknown login alerts, or...
EDITORIAL CLARITY

How we keep this policy current

A privacy page should feel clear, current and tied to the account you actually use. We check wording, vendor roles, consent flows and Indonesia access wording so this policy remains useful before...

Policy owner

A named internal owner checks privacy wording before changes go live, making sure collection, use, sharing and retention statements match how rajabandoy account flows are set up.

Vendor mapping

We map hosting, analytics, messaging and payment-routing vendors against this Privacy Policy, so each outside processor has a purpose and a contract-based role.

Consent checks

We check consent language around cookies, account notices and marketing choices, so you can see what is required for service and what can be adjusted.

Regional wording

Indonesia access wording is kept separate from global legal phrasing, with supported regions and where local law permits language added when availability matters.

Data minimisation

Each field requested during account setup is checked against a clear purpose, helping us avoid collecting personal data that does not support your account.

Change trail

When this Privacy Policy changes, we keep an internal trail showing what was updated, why it changed, and which account or service flow was affected.

Consistency across our legal pages

Your privacy rights should not change tone from one legal page to another. We align this Privacy Policy with our related pages, so account data, cookie use, promo...

Terms page alignment
Our Terms explain account rules, while this Privacy Policy explains data handling. We keep both aligned where identity checks, account security and support records overlap.
Cookie page alignment
Cookie wording points back to this Privacy Policy when identifiers, analytics events or device signals connect to your account or help keep the session stable.
Promo contact alignment
Promo messages may rely on consent or account settings. We align those references with this policy so you can understand why contact happens and how to change it.
Support record alignment
Support pages describe how to reach us; this Privacy Policy explains why we may keep chat logs, request history and verification notes after your case is handled.
Transaction record alignment
DANA, OVO, GoPay and QRIS references appear in transaction records. This policy explains how those references support reconciliation, account security and legal record needs.
Security page alignment
Security wording covers account protection steps, while this policy covers the personal data used to detect misuse, verify ownership and protect your account flow.
Regional access alignment
Where access depends on supported regions, our legal pages use the same wording so you do not receive mixed messages about availability or data handling.
AT A GLANCE

Policy layout you can scan

We design this Privacy Policy so you can find the parts that matter before you join. The layout highlights account data, choices, retention, sharing and contact routes without...

Plain account summary The opening sections explain what data we collect, why we...
Purpose-led blocks Each privacy topic is grouped by purpose, such as account...
Choice markers Where you have a choice, we mark it clearly, including...
Retention cues We explain retention by record type, so you can see...
Sharing labels Vendor and partner sharing is labelled by role, helping you...
Contact prompts Request paths appear near the relevant policy topics, so you...

Privacy Policy questions answered

We collect account details, login signals, support messages, consent choices, security records and transaction references needed to run your account and answer privacy requests where local law permits.

We use those references to match transactions to your account, resolve support cases, detect unusual activity and meet record duties. We do not need wallet passwords or private codes.

No. We do not sell your personal data. Limited vendors may process data for hosting, analytics, messaging, security or routing, and only for the purposes described in this policy.

Yes. Contact us through the privacy path and tell us what you want checked. We may verify account ownership before providing access, correction or deletion responses.

Retention depends on the record type. Session data may be shorter, while transaction references, identity checks and support records may remain longer for security and legal duties.

When we change this Privacy Policy, we update the page date or account notice where suitable. Major changes may also appear inside your account message area.