Privacy Policy For Your Account
rajabom keeps your casino, slot and sportsbook account flow clear by explaining what personal data we collect, why we use it, and how it supports access where local...
How We Treat Your Data
This Privacy Policy explains how rajabom handles personal data connected with account creation, identity checks, lobby access, security screening, support requests, promos shown to your account, and payment references in supported regions. We collect only the details needed to operate the service, protect your account, meet legal duties, and keep records accurate. Where local law permits, we may use contact, device, session,
location, and transaction signals to detect misuse and improve the account journey. We do not sell your personal data. We share it only with service partners that help us run security, verification, hosting, analytics, support, and payment processing under controlled terms.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
Privacy Contact Paths
If you have a privacy question, we want you to reach us through the channel that fits the request. Use support for account data checks, use security contact for suspicious access, and use profile tools when you want to update basic details.
Account Support
Ask us to check profile details, contact records, login history, or transaction references tied to your account. We may ask extra verification before discussing personal data, so your request stays matched to you.
Security Contact
Tell us quickly if you notice unknown login attempts, unfamiliar device activity, or changes you did not make. We use your report to secure the account and assess whether privacy controls need action.
Profile Tools
Use your account area to correct basic contact details, manage communication choices, and check active sessions. Some records may stay locked when we must keep them for legal, security, or accounting reasons.
Policy Review Signals
We keep this policy tied to the way rajabom actually handles account data. When our login flow, verification process, support path, or local payment references change, we check...
Clear Scope
We separate account data, payment references, device signals, support messages, and marketing choices so you can see which part of...
Current Workflow
Policy wording is checked against active account screens, including sign-in, profile edits, verification prompts, security notices, and lobby entry points...
Local Context
Indonesia payment references such as DANA, OVO, GoPay and QRIS are treated as privacy context, not a reason to collect...
Security Link
We connect privacy handling with account protection, using session logs, device checks, and risk signals to reduce unauthorised access while...
Access Requests
You can ask about personal data linked to your account, request correction, or question a use. We respond through verified...
Retention Checks
We keep records only while needed for account service, legal duties, dispute handling, security, and accounting. When retention ends, data...
Consistency Across Policy Pages
Our Privacy Policy works beside our terms, cookie text, promo rules, and support statements. Each page has a different role, but they should not conflict. If wording changes...
| Terms Link | Terms explain account rules and service use, while this policy explains personal data handling. When both mention verification, the privacy page focuses on data collection, access, sharing, and retention. |
|---|---|
| Cookie Text | Cookie wording covers browser storage, tags, and similar tools. This policy connects those tools to account sessions, security checks, preferences, and analytics used to improve the service. |
| Promo Rules | Promo rules explain eligibility and account conditions. This policy explains how rajabom may use account status, contact choices, and activity records to show relevant promo messages. |
| Support Standards | Support pages explain how to contact us. This policy explains what data support may need, how identity is checked, and why message records may be retained after a case closes. |
| Security Statements | Security statements describe account protection steps. This policy explains the personal data behind those steps, including device records, login events, risk checks, and alerts connected with unusual activity. |
| Payment References | Payment pages may mention DANA, OVO, GoPay and QRIS. This policy limits that topic to privacy handling around transaction references, verification, fraud checks, and required records. |
| Update Rhythm | When we adjust policy pages, we check dates, wording, and contact paths together. That helps you read the full set without finding mixed privacy meanings. |
Policy Layout You Can Scan
This page is built so you can find privacy points without reading unrelated platform copy. The layout keeps collection, use, sharing, storage, choices, and contact paths visible, while...