Cookie page alignment
Cookie settings and tracking labels should match the data categories described here. If a cookie supports login, security or analytics, this Privacy Policy explains the broader reason it exists.
LEGAL REFERENCE
Privacy Policy for Your rajabanot Account
Live Baccarat, Sweet Bonanza, Aviator and our sportsbook sit behind one account, and this Privacy Policy explains how we handle the data that keeps that account flow clear...
Account dataLobby privacyIndonesiaPolicy contact
Our Privacy Position in Indonesia
When you open or manage your rajabanot account, we collect only the data needed to identify you, operate the lobby, protect access and keep records required for supported regions. This Privacy Policy applies where local law permits access to our casino, live table, slot and sportsbook areas. We may process account details, device signals, session activity, support messages and transaction references connected
with DANA, OVO, GoPay, QRIS or other supported rails. We use that data to run your account, answer requests, improve security checks and meet legal duties. We do not sell your personal data as a product. If a partner helps us host, verify or secure the service, we require them to handle your data only for the agreed purpose and with suitable
safeguards.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
SUPPORT
Contact Paths for Privacy Requests
Privacy questions should reach a team that can trace your account without exposing more data than needed. Use these contact paths when you want access, correction, deletion checks or a clear answer...
Account privacy email
Use the help address when you want a copy of personal data linked to your account identity, lobby activity or contact history. We confirm the request path before sending anything sensitive.
Live support handoff
Start with chat if you are already signed in and need a privacy concern attached to your account record. We may move the request to email for safer document handling.
Security escalation
If you think your account data, device access or transaction reference was exposed, tell us quickly. We prioritise containment, check recent sessions and explain the next privacy steps we can take.
REVIEW SIGNALS
How We Keep This Policy Current
A privacy page should not feel detached from the account flow you actually use. We keep this policy close to our lobby, support and transaction screens so the wording matches how your...
Plain-language drafting
We write privacy terms in direct English for Indonesia, avoiding legal noise where simple wording works. If we need a technical term, we connect it to your account, session or support request.
Scheduled policy checks
Our team checks the Privacy Policy against account fields, login screens and support flows. If a data point is added or removed, the page is updated to keep your reading accurate.
Local context checks
We reference DANA, OVO, GoPay and QRIS only where they affect transaction records or verification notes. The policy stays focused on data handling rather than turning into a cashier page.
Access-control alignment
Internal access to personal data is limited by role, purpose and need. Support can help you, security can investigate incidents, and unrelated teams do not receive open access by default.
Partner handling rules
Where hosting, analytics, security or verification partners process data for us, we set purpose limits and confidentiality duties. They should not reuse your data for unrelated promotion or profiling.
Change visibility
When privacy wording changes in a meaningful way, we aim to make the update easy to notice. You can return to this page before opening an account or after signing in.
BENCHMARKED
Policy Consistency Across Account Pages
Your privacy rights should read the same whether you start from the lobby, the account screen or a help contact. We align this page with sibling legal pages so your data choices...
Terms page connection
Our Terms explain account use, while this page explains personal data handling around that use. We keep the split clear so you can see rights, duties and privacy choices separately.
Promotion page boundaries
If you check what is running this week, any related account eligibility data still falls under this Privacy Policy. Promo displays do not remove your rights to ask about stored data.
Support page matching
Support forms ask for details only to solve the issue you raise. The same request data, attachments and contact replies are covered here, including how we limit access internally.
Security page flow
Login alerts, device checks and session records support account protection. This Privacy Policy explains those security records without turning the page into technical jargon or hiding retention choices.
Cashier record clarity
DANA, OVO, GoPay and QRIS references may appear in account history where supported. We treat those references as privacy-relevant records, not as public labels or marketing material.
Account settings match
Your profile fields, communication choices and verification status should reflect the categories named here. When you update details, the privacy record follows the same account management path.
Visible Privacy Cues on This Page
This layout is built to help you spot the privacy parts that matter before you join. The sections below show what we collect, who can handle...
Short privacy badges
The chips near the hero point to account data, lobby privacy and Indonesia context. They help you recognise the page purpose quickly before reading the full policy language below.
Context chips only
DANA, OVO, GoPay and QRIS appear as context chips because transaction references can involve personal data. They are not presented here as a selling point or cashier instruction.
Direct request routes
The contact cards separate access, correction and security concerns so you can choose the safer path. Each route is written around privacy handling rather than general lobby help.
Rights-first wording
We describe access, correction, deletion checks and objection paths in direct wording. The goal is to make your control over account data easier to understand before you submit a request.
Data-category clarity
We name account details, device signals, session activity, support messages and transaction references instead of using vague labels. Clear categories make it easier for you to ask precise privacy questions.
Policy-side consistency
The page connects privacy wording with Terms, Cookies, support and security pages. That consistency helps you avoid conflicting answers when you move between account areas on rajabanot.
Privacy Policy Questions Before You Join
We collect account details, contact records, device signals, session activity, support messages and transaction references needed to run your account. The exact data depends on what you do and which supported region applies.
Device and session data help us secure access, spot unusual sign-ins and keep the lobby stable. We use it for account protection and service operation, not to expose your private activity publicly.
No. When those references appear in supported regions, they are treated as account records covered by this Privacy Policy. You can still ask about access, correction or handling of related personal data.
Yes. Contact us through the privacy email or signed-in support path and we will verify the request before sharing account data. Verification helps prevent another person from receiving your private details.
You can ask us to correct inaccurate account details where local law permits and where the change is supported by our systems. Some security or transaction records may need to remain unchanged for integrity.
We keep personal data only for as long as needed for account operation, security, legal duties and dispute handling. Retention periods can differ by data type, region and the reason the record exists.
Access is limited by role and purpose. Support, security and compliance functions may handle relevant data to answer requests or protect your account, while unrelated internal teams should not receive open access.