LEGAL REFERENCE

How raja22pro Handles Your Account Data

This privacy policy is the part of raja22pro that tells you, plainly, what we collect when you open an account and switch between our slot rooms, live tables...

Policy v3Indonesia-firstPlain EnglishAccount dataUpdated quarterly
Browse the Lobby Read FAQ
raja22pro How raja22pro Handles Your Account Data

Our Privacy Posture, Written for You

We collect only what your raja22pro account needs to function: the handle you sign up with, the wallet reference you link, session signals that keep your lobby secure, and the support notes you send us. Where local law permits, we store this inside supported regions and share it only with the payment rails you actually use. We don't sell your contact details

to third parties, and we don't pad your inbox with messages you didn't ask for. If a regulator in your jurisdiction asks us for records, we follow the legal route on file. You can ask to see, correct or close your account data any time, and we'll action that request inside the window our policy commits to.

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

PLAYER SUPPORT

Privacy Contact Paths You Can Use

If something about your data feels off, reach our privacy desk directly through one of the channels below.

Team online

Privacy Inbox

Email our data team at the address listed in your account footer. We acknowledge every privacy request within one business day and respond fully inside the statutory window for Indonesia.

In-App Chat

Open the chat bubble inside your raja22pro lobby and ask for the privacy queue. The agent routes you straight to the reviewer handling data, access and deletion tickets, not general support.

Written Request

Send a signed letter to the registered address shown in our footer. Include your account handle and the last DANA, OVO, GoPay or QRIS reference so we can match the request quickly.

PLATFORM TRUST SIGNALS

How We Keep This Policy Honest

These are the editorial checkpoints behind every revision of the raja22pro privacy text.

Quarterly Review

Our compliance lead re-reads this policy every quarter and flags anything that drifted from how the lobby actually works. Edits get version-stamped at the top so you can see what changed.

Plain-Language Pass

A second editor rewrites legal phrasing into the Indonesia-friendly English you're reading now. If a clause can't be explained in one sentence, we restructure it until it can.

Engineering Sign-Off

Before any clause about data storage goes live, our engineers confirm the systems actually behave that way. Policy and product stay aligned instead of drifting apart over time.

Payment Rail Audit

We re-check how DANA, OVO, GoPay and QRIS references are stored on our side every release cycle. Anything we no longer need gets purged from the active account record.

Access Request Log

Every data access, correction and deletion request is logged with a reviewer name. That log is what we'd hand a regulator if your jurisdiction asked for proof of process.

Reader Feedback

If you tell our support team a clause reads strangely or contradicts what you saw in the lobby, that feedback enters the next quarterly pass. Real reader notes have reshaped this page twice.

Consistency With Our Other Policy Pages

Here's how this privacy policy lines up with the sibling legal pages on raja22pro.

Terms of Service
The terms page covers account behaviour and lobby rules; this page only covers data. Where they overlap on account closure, both pages quote the same window.
Cookie Notice
Cookies are summarised here and detailed on the cookie page. The categories, retention periods and opt-out controls match between the two documents word for word.
KYC Statement
Identity checks are described at a high level in this policy and step-by-step on the KYC page. Both reference the same supported-region list for Indonesia readers.
Payments Policy
DANA, OVO, GoPay and QRIS storage is named here; transaction-level handling sits on the payments policy. Retention windows are identical across both.
Complaints Path
Privacy complaints route through the contacts above; service complaints follow the dedicated complaints page. The escalation ladder is the same on both sides.
Data Retention
Retention timelines summarised in section two of this page are expanded into a table on the retention policy. No clause contradicts the other; we cross-check each release.
Change Log
Every policy page on raja22pro carries the same version stamp format at the top, so you can tell at a glance whether your previous read is still current.
PLATFORM SNAPSHOT

What This Policy Page Actually Shows You

These are the on-page elements that make the privacy text easier to navigate.

Version Stamp The header carries the policy version and last-edited date. If...
Section Anchors Each clause has its own anchor link so you can...
Plain-English Sidebar Legal phrasing sits beside a one-line summary in the margin...
Jurisdiction Note A short note at the top reminds you this policy...
Request Buttons Inline buttons launch the access, correction and closure forms straight...
Change Log Link At the foot of the page, a link opens the...

Privacy Questions We Hear Most

Your handle, the wallet reference linked to DANA, OVO, GoPay or QRIS, session signals that keep your lobby secure, and any support notes you send us. That's the full list — nothing about your device contacts or social graph.

Active records are purged shortly after closure, but anti-fraud and tax-relevant fields are retained for the period local Indonesia law requires us to keep them. The retention policy page lists each field with its exact window.

Yes. Open a privacy request through chat, email or the inline button on this page. We verify it's really you, then return a structured export of your account data inside the statutory response window.

No. We don't sell contact details and we don't hand your record to ad networks. Marketing inside raja22pro is sent only to the channel you opted into, and you can turn it off from your account settings any time.

Inside supported regions agreed with our infrastructure providers. Where local law permits cross-border processing for payment verification, only the minimum fields travel, and the receiving party is bound by the same handling rules we follow.

The version stamp at the top updates and the change log entry explains what shifted. Material changes also trigger an in-lobby notice the next time you sign in, so you won't miss a clause that affects your account.

Reply to the same privacy ticket and ask for escalation. A second reviewer re-opens the case. If you're still not satisfied, the complaints page lists the regulator in your jurisdiction you can contact directly.