LEGAL REFERENCE

How rojobet88 Handles Your Account Data

This privacy policy explains how we collect, store and use the information tied to your rojobet88 account. We've written it for our Indonesia audience so you can see...

Account dataCookiesSession logsPayment metadataKYC checks
rojobet88 How rojobet88 Handles Your Account Data

Policy Scope and Jurisdiction Notes

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

SUPPORT

Privacy Contact Paths

If you need to ask about your data, reach us through any of the channels below. Each one routes to the privacy...

Privacy Inbox Email the privacy desk directly for data access...
Live Chat Open chat from the lobby header and ask...
Account Settings Head to your account settings to download a...
WHY VISITORS TRUST US

How We Review This Policy

Our privacy posture isn't a one-off document. Here's how we keep it honest.

Internal Review

Our compliance team revisits this policy on a fixed cycle and after any change to how the casino, slots or sportsbook side of the lobby handles your account data. Versions are dated.

Processor Audits

Every external processor that touches your DANA, OVO, GoPay or QRIS top-up metadata is audited for handling standards before we route a single Indonesia transaction through them.

Encryption in Transit

Sessions between your device and rojobet88 ride over TLS. Login tokens, deposit references and KYC uploads stay encrypted from the moment you submit them until they reach our store.

Access Controls

Only staff with a reviewed business reason can open your record. Every read is logged. We don't let general support or marketing pull personal data outside their defined scope.

Retention Limits

We hold account and transaction data only for the window Indonesia regulators expect. After that, records are anonymised or removed so old data doesn't sit on our systems without purpose.

Plain-Language Drafting

This policy is written for you, not for a courtroom. If a clause reads as legalese, we rewrite it. You shouldn't need a lawyer to know what we do with your data.

Consistency Across Our Policy Pages

This privacy policy lines up with the rest of our legal pages. Here's how the pieces fit.

Terms of Service
Our terms describe account rules; this policy describes data handling. The two are written together so language about your account stays consistent across both pages.
Cookie Notice
Cookie behaviour is summarised here and detailed on the cookie page. Categories, vendors and opt-out paths match across both documents without drift.
KYC Statement
Identity verification steps referenced in this policy expand on the dedicated KYC page, with the same document list and the same retention windows quoted.
AML Posture
Anti-money-laundering checks on DANA, OVO, GoPay and QRIS deposits follow the rules laid out in our AML page and surface here only as a data-handling note.
Complaints Path
If a privacy request becomes a complaint, the escalation route mirrors what's on our complaints page — same desk, same timeline, same reviewer chain.
Data Requests
The access, correction and deletion rights summarised here use the exact same form and same response window described on the data-rights page.
Policy Updates
When we update one legal page, we revisit the others on the same cycle so version dates stay aligned and you never read contradictory statements across them.
SERVICE CONTEXT

What's Visible On This Policy Page

A few elements anchor the privacy side of the rojobet88 layout. Here's what you'll see as you scroll.

Version Date Every published version of this policy carries a date at...
Section Anchors The page is broken into anchored sections — scope, contact...
Plain Summaries Each legal block opens with a short plain-language line before...
Contact Block A pinned contact block sits in the policy footer with...
Change Log A short change log lists what shifted between versions. We...
Print View A print-friendly view is one click away if you want...

Privacy Policy FAQ

We collect your name, contact details, date of birth, device identifiers and the wallet reference you use for top-ups. KYC documents are added when verification is required for your account tier.

Wallet metadata is held only for the period Indonesia regulators expect. We use it to confirm the deposit, run AML screening and resolve disputes — never for marketing or external sharing.

Yes. Open account settings or email the privacy desk and we'll prepare an export of your record. The standard response window is a few working days, depending on request complexity.

Submit a deletion request from settings or via the privacy inbox. We close the account and remove personal data, keeping only what regulators require us to retain for audit purposes.

We share data only with processors that support a specific function — KYC checks, fraud screening, wallet routing for DANA, OVO, GoPay and QRIS. Each one is bound by contract to our privacy posture.

We revisit it on a fixed internal cycle and after any change to how account data moves through our systems. The version date at the top of the page tells you which revision is live.

Session cookies keep you logged in; preference cookies remember your lobby layout; analytics cookies help us improve the site. Categories, vendors and opt-out paths are detailed on the cookie notice.