Definitions
Account, session, device signal and transaction reference carry the same meaning on every policy page across rajabola.
LEGAL REFERENCE
How rajabola Handles Your Account Data
This is the privacy policy page for rajabola. We wrote it so you can see, in plain terms, what we collect when you open an account with us...
Account dataDevice signalsPayment referencesIndonesia scopePlain-English policy
Policy Posture and Jurisdiction Scope
Our policy applies to you when you access rajabola from supported regions across Indonesia, where local law permits. We collect the account fields you submit at sign-up, the device signals your browser shares, and the transaction references your e-wallet returns after a top-up. We store these only for the operational purposes outlined on this page — session continuity, payment reconciliation, fraud checks
and lobby personalisation. We do not sell your data. Where Indonesian regulation requires retention, we hold records for the minimum period stated by the responsible authority, then purge them on schedule. You can request a copy of what we hold, ask for corrections, or close your account by contacting the channels listed further down. The policy is reviewed quarterly and any material
change is signalled on this page before it takes effect.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
24/7 SUPPORT
Privacy Contact Paths
If you have a question about your data, reach us through any of the channels below. Our policy desk handles requests separately from the general lobby helpdesk so your message gets to the right reviewer.
Team online
Policy email
Send data-access, correction or deletion requests to our policy inbox. We acknowledge within one business day and complete most reviews inside seven days, faster when your account is already verified.
In-lobby chat
Open the chat widget from your account header and choose the privacy topic. The agent routes you straight to a policy reviewer rather than the standard lobby queue, keeping your request on record.
Written request
For formal data requests tied to Indonesian regulation, you can send a signed letter to our registered correspondence address. We log receipt and reply through the same channel within statutory timeframes.
EDITORIAL CLARITY
Editorial Trust Signals for This Policy
We treat the privacy page as a living document. The signals below show how we keep it honest, current and aligned with how rajabola actually runs day to day.
Quarterly review
Our compliance team reads this policy every quarter and rewrites any clause that no longer matches operational reality. Change dates are logged internally and surfaced on this page when wording shifts materially.
Named reviewer
A single accountable officer signs off each version of this policy before it goes live. That removes ambiguity about who owns the wording when you raise a data question with us.
Plain language
We deliberately avoid legalese where Indonesian law allows. If a clause uses a technical term, you'll find a short explanation nearby so the policy reads like a brand talking, not a contract.
Versioned changes
Every revision carries an effective date and a short summary of what moved. Older versions are archived so you can compare what the policy said when you first opened your rajabola account.
Scoped collection
We only collect data we can point to a purpose for. If a field isn't needed for sign-in, payment routing, fraud checks or lobby personalisation, it isn't on the form in the first place.
Local alignment
The policy is drafted against Indonesian data-protection expectations and the operational realities of DANA, OVO, GoPay and QRIS rails, not copied from a generic template designed for another market.
PLATFORM COMPARISON
Consistency Across rajabola Policy Pages
This privacy page sits alongside our terms, cookie and payment policy pages. The table below shows how the wording lines up so you don't get conflicting answers depending on which page you...
Retention windows
Holding periods stated here match the windows quoted in our terms of service and payment policy without exception.
Contact routing
The policy email and chat path listed above are the same ones referenced from the cookie and terms pages.
Review cadence
All policy pages are refreshed on the same quarterly cycle so dated wording doesn't linger on one page while another updates.
Jurisdiction scope
Indonesia and supported regions language is identical across the privacy, terms and cookie notices to avoid coverage gaps.
Change signalling
Material updates are flagged in the same banner format on every policy page so you spot them quickly.
Data subject rights
Access, correction, deletion and portability requests follow one shared workflow no matter which policy page you arrived from.
How This Policy Page Is Laid Out
Before you scroll the full text, here's a quick map of what defines the policy-side layout so you can jump to the part you need.
Effective date header
The current version date sits at the top of the page so you can see at a glance whether the wording has shifted since your last visit to rajabola.
Scope summary
A short scope block tells you which products, regions and account types the policy applies to before the detailed clauses begin further down the page.
Clause anchors
Each clause has a stable anchor link so you can share a direct URL to a specific section when you raise a question with our policy desk.
Rights checklist
A dedicated block lists the data-subject rights you can exercise, written as actions you can take rather than abstract entitlements buried in paragraphs.
Contact footer
The policy contact paths repeat at the foot of the page so you never have to scroll back up to find where to send a request.
Change log
A compact change log near the bottom records the last few revisions with effective dates, giving you a transparent trail of how the policy has evolved.
Privacy Policy Questions
We collect the identity fields you submit on the sign-up form, the device signals your browser shares for session security, and the transaction references your e-wallet returns. Nothing beyond what the account flow actually needs.
Active account data stays with us while your account is open. After closure, we retain only the minimum records Indonesian regulation requires, then purge the rest on a fixed schedule documented in this policy.
Yes. Send a data-access request through the policy email or in-lobby chat. We acknowledge within one business day and return your file inside seven days for verified accounts, longer if extra checks apply.
We share data only with payment processors handling your top-ups, fraud-check providers and authorities where Indonesian law obliges disclosure. We do not sell your data and we do not pass it to marketing networks.
Open your account header, choose profile, and edit the fields you can change yourself. For locked fields tied to verification, message the policy desk and we'll update them after a quick identity check.
On closure, your lobby profile is deactivated immediately. Payment and compliance records remain only for the retention window Indonesian regulation sets, after which we delete them on our scheduled purge cycle.
Material changes are flagged in a banner on this page before they take effect, and the effective date at the top updates. The change log near the bottom records what moved and when.