LEGAL REFERENCE

How rajabola99 Handles Your Account Data

This is the privacy policy for rajabola99, written so you know exactly what we collect when you open an account, browse our slot rooms or place a wager...

Account dataCookiesRetentionYour rightsIndonesia
rajabola99 How rajabola99 Handles Your Account Data

Privacy Posture and Data Handling

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

PLAYER SUPPORT

Privacy Contact Paths

Team online

Privacy Desk Email

Write to our privacy desk for any access, correction or deletion request tied to your rajabola99 account. We aim to respond within five working days across Indonesia time zones.

Live Chat Privacy Queue

Open live chat from the lobby footer and pick the privacy queue. Our agents can confirm what data sits on your profile and escalate deletion requests straight to the data controller.

Data Controller Address

Postal correspondence reaches the registered data controller listed in our footer. Use this channel for formal complaints, regulator escalations or third-party legal notices about your stored account data.

TRUST MARKERS

How We Review This Policy

Quarterly Policy Review

Our compliance team revisits this privacy notice every quarter so wording stays aligned with Indonesia data rules and the partner agreements we sign with payment processors handling DANA, OVO, GoPay and QRIS flows.

Legal Counsel Signoff

External legal counsel signs off on every material change to this policy before it goes live, and the version date in the footer reflects the last counsel-approved revision visible to you.

Encryption in Transit

Every form on rajabola99 — registration, cashier, support — runs over TLS so the data you submit reaches us encrypted. We rotate certificates on a fixed schedule audited by our security partner.

Access Logged Internally

Staff access to your account record is role-gated and logged. Only agents handling an open ticket or a verification step can read the relevant fields, and supervisors review the access trail.

Vendor Due Diligence

We screen every vendor that touches your data — payment, KYC, analytics — against a written checklist covering data residency, breach notification windows and the deletion guarantees they offer us on contract exit.

Breach Notification Plan

If a data incident were to affect your account, we follow a written notification plan that contacts you directly through the channel on file and informs the relevant Indonesia authority within the required window.

Consistency Across Our Policy Pages

Privacy vs Terms
This privacy page covers data handling only. Account conduct, wagering rules and payout disputes sit on our terms page, and the two documents are written to read together without contradicting each other.
Privacy vs Cookie Notice
Cookies and similar trackers get their own short notice. This privacy policy references it but keeps the granular tag list, lifetimes and opt-out switches on the cookie page itself.
Privacy vs KYC Policy
Identity checks have a dedicated KYC page. Here we describe what verification data we keep and for how long; the KYC page explains which document types we accept at cashier.
Privacy vs AML Notice
Anti-money-laundering screening uses a defined subset of your account data. This policy lists that subset; the AML notice explains the thresholds that trigger an enhanced check on your profile.
Privacy vs Marketing Prefs
Marketing consent lives on your account preferences screen, not in this policy. We describe the legal basis here and let you toggle channel-level consent inside your logged-in dashboard.
Privacy vs Complaints
Privacy complaints follow the contact paths above. General service complaints route through our standard complaints page so each track reaches the correct handler without delay.
Privacy vs Regional Notices
Indonesia-specific addenda, where local law permits, appear as dated appendices at the foot of this page rather than rewriting the core policy each time a regional rule changes.
PLATFORM SNAPSHOT

What This Policy Page Shows You

Version Date Header The header carries the live version date so you can...
Section Anchors Each policy section has its own anchor link on the...
Plain-Language Summary Above every dense clause we keep a one-line plain-language note...
Contact Block A persistent contact block on the right rail shows the...
Change Log Footer At the bottom of the page we keep a dated...
Print-Friendly View A print-friendly toggle renders the policy as a clean single-column...

Privacy Questions We Hear Often

We collect what your account needs to function: your name, contact handle, device and session identifiers, the e-wallet reference you select at cashier and the verification documents you upload during KYC. Nothing else.

Only with payment processors, KYC vendors and infrastructure partners that need a specific data field to deliver their part of your session. We never sell your personal information to advertising networks or data brokers.

Active account data stays with us while your profile is open. After closure we retain the records our licence obliges us to keep, then delete or anonymise the rest on a documented retention schedule.

Yes. Write to our privacy desk from the email on file and we will close the account and erase the data we are not legally required to retain. We confirm completion in writing to you.

Every page on rajabola99 runs over TLS and our internal databases sit behind role-gated access with full audit logs. Staff see only the fields needed for the ticket or check they are working on.

Yes, where local law permits. Indonesia-specific addenda appear as dated appendices at the foot of the page, so the regional wording stays visible without rewriting the core policy each time.

We update the version date in the header and add a line to the change log at the foot. Material changes also trigger a notice on your next login to your rajabola99 account.