Scope
Privacy covers personal data only; terms cover account conduct. No overlap or contradiction between the two.
LEGAL REFERENCE
How rajacuan88 Handles Your Account Data
This page explains the privacy practices behind your rajacuan88 account. We cover what we collect when you register, how we use it across the slot lobby, live tables...
Data ScopeYour ControlsIndonesia RegionRetention WindowContact Path
Policy Posture and Jurisdiction Notes
Our privacy posture follows Indonesian personal data rules and the contract terms shown when you opened your account. We collect identity fields, login signals and transaction references — only what's needed to run your lobby session and clear a payout. Where local law permits, we keep KYC records for the retention window stated in your account agreement, then archive or delete them.
Cross-border processing is limited to vetted vendors in supported regions, and any sharing with payment partners covers DANA, OVO, GoPay and QRIS reconciliation only. You can ask us to export, correct or close the record at any time.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
WHY VISITORS TRUST US
Editorial Trust Signals Behind This Policy
Six checks shape how we draft, review and update this privacy text.
Legal Review
Indonesian counsel reviews the policy text before each release. Wording around retention, lawful basis and cross-border transfer is signed off in writing rather than copied from a template, so what you read matches what we do.
Versioning
Every change is dated in our internal log with a short note on what moved. If you want to compare today's policy to the version active when you registered, we can send the prior text on request.
Vendor Audits
Payment, hosting and KYC vendors are audited yearly against the data scope they actually need. Access is removed when a vendor leaves the stack, and audit notes are kept with the privacy file.
Staff Training
Our support and finance staff complete privacy refreshers twice a year. Handling rules for DANA, OVO, GoPay and QRIS references are part of that training, not a separate after-thought.
Breach Drill
We run a tabletop breach drill each quarter. The notification clock, regulator contact and customer email template are tested so a real incident wouldn't be the first time the team uses them.
Plain Wording
We rewrite this page in plain English-Indonesia phrasing rather than legalese. If a clause is unclear, the privacy desk will explain it in chat and feed the question back into the next revision.
WHY THIS PLATFORM
Consistency Across Our Policy Pages
This privacy text sits beside our terms, KYC and cookie pages. The seven points below show how they line up.
Retention
The retention window quoted here matches the figure in our KYC page exactly, down to the month count.
Vendors
Vendor list referenced here is the same one published on the cookie page, refreshed on the same release date.
Lawful Basis
Lawful basis language mirrors what your account contract states when you registered, so nothing shifts after sign-up.
Contact
Privacy inbox and chat route are identical to the contacts shown on the support and complaints pages.
Updates
Version date at the foot of this page matches the changelog entry shown on the terms page for the same release.
Region
Indonesia jurisdiction wording is consistent with the supported-regions note used across every legal page.
AT A GLANCE
What This Policy Page Includes
Six visible elements make up the privacy layout so you can find what you need without scrolling blindly.
01
Data Map
A short map of the fields we hold — identity, contact, session, transaction reference — sits near the top so you can scan the scope before reading the full clauses underneath.
02
Retention Table
Retention windows are shown as a table rather than buried in prose. Each data category has its own row with the keep-period and the trigger that starts the clock.
03
Rights Panel
Your rights — access, correction, deletion, portability, objection — sit in a single panel with the action button next to each one, so a request takes one click.
04
Vendor List
Named processors appear with their role and region. The list is updated whenever a vendor is added or removed, with the change date on the entry.
05
Change Log
A dated change log at the foot records every revision. Material changes are flagged so you can tell a wording tweak from a real policy shift.
06
Contact Block
The privacy contact block repeats at the foot with email, chat link and account-panel shortcut, so you don't have to scroll back up to act on what you read.
Privacy Questions We Hear Most
We collect your registration identity, contact details, login signals and transaction references tied to DANA, OVO, GoPay or QRIS. Lobby activity is logged for fraud checks. Nothing outside that scope is gathered for marketing without your explicit consent.
KYC and transaction records are retained for the period set in Indonesian financial rules, then archived or deleted. Marketing data is removed immediately on closure. The exact month count is shown in the retention table on this page.
Yes. Open your account panel or email the privacy inbox and we'll prepare an export file or a deletion confirmation once your identity is verified. Statutory records we must keep will be listed separately in the response.
Only the minimum needed for DANA, OVO, GoPay and QRIS reconciliation passes to those partners. They receive a transaction reference and amount, not your full profile. Sharing is governed by signed processor agreements on our side.
Primary storage sits in supported regions covered by our hosting agreement. Cross-border processing happens only with vetted vendors and within the lawful basis stated in your account contract. The vendor list on this page names every location.
Material changes trigger an email to your registered address and a banner in the lobby on your next sign-in. Minor wording tweaks are recorded in the change log at the foot of this page with the revision date.
Start with the privacy inbox or live chat — both reach the same handler. If the response doesn't resolve it, you can escalate to the Indonesian data protection authority. Contact details are repeated in the footer block.