Terms of Service
Privacy wording here mirrors the data clauses inside our Terms. Where the Terms reference account closure, this policy explains exactly which records survive that closure and for how long.
This privacy policy explains what we collect when you open an account with rajaslotjp, how your details move through our slots, live casino and sportsbook lobby, and the...
We process your account data under Indonesia data-protection norms and only where local law permits. When you register, we capture identifiers needed to verify your account, fund your wallet through DANA, OVO, GoPay or QRIS references, and keep the lobby secure. Session logs, device fingerprints and payout records are retained for the windows our payment partners require, then archived or deleted. We
don't sell your data. We share it only with regulated processors handling KYC, fraud screening and settlement for supported regions, and we notify you if material policy terms shift.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
Indonesia counsel reviews this policy each quarter against current regulations. Changes get version-stamped at the foot of the page so you can see when terms last moved and what was adjusted.
Our internal security group signs off on retention windows, encryption defaults and access logging before any wording reaches this page. Nothing here is aspirational — it reflects controls already running in production.
DANA, OVO, GoPay and QRIS settlement records carry their own data rules. Our payments desk maps those rules into the policy so you understand why certain transaction fields stay on file.
A named data protection lead owns this document. Privacy requests escalate to that desk if first-line support can't resolve them within the published response window for your region.
Independent auditors test our handling of account identifiers and session data annually. Findings feed back into this policy, particularly around third-party processors used for KYC and anti-fraud checks.
Each revision is logged with a date and short note on what changed. If the shift affects your consent, we surface a notice in-lobby before the new wording takes effect on your account.
Privacy wording here mirrors the data clauses inside our Terms. Where the Terms reference account closure, this policy explains exactly which records survive that closure and for how long.
Cookies, pixels and local storage are catalogued in our Cookie Notice. This policy points to that document rather than duplicating it, so you read one source for browser-level tracking.
Identity checks sit in our KYC Notice. This policy summarises which fields KYC needs and how long verification artefacts stay attached to your rajaslotjp account record.
DANA, OVO, GoPay and QRIS handling is detailed in Payments Terms. This page references those flows to explain why transaction metadata is processed alongside your gameplay data.
Promotion participation creates extra data points — opt-in flags, eligibility checks. Our Promotions Rules explain those, and this policy confirms they fall under the same retention windows.
The closure page describes how to leave. This policy specifies which residual records remain post-closure for legal, anti-fraud and tax purposes in supported Indonesia regions.
If a privacy answer doesn't satisfy you, the Complaints page lists escalation steps. We keep both pages aligned so the route from question to resolution stays the same.
We've split the policy into short, labelled sections so you can jump straight to retention, sharing or your rights without scrolling through legal preamble that doesn't apply to your account.
A dated version stamp sits at the foot of the page. If you bookmarked an earlier draft, the stamp tells you immediately whether wording shifted since your last visit.
Terms like processor, controller and retention window are defined inline the first time they appear, so you don't need to keep a separate glossary tab open while reading.
Action buttons sit beside each right — access, correction, deletion, portability. One tap routes the request to the privacy desk with your account context already attached.
A scope panel confirms this policy applies to Indonesia accounts and notes where supported-region wording kicks in. You won't have to guess which clauses cover your sign-up.
A short change log records material edits in chronological order. Each entry links to the section affected so you can read the new wording without re-reading the whole document.