LEGAL REFERENCE

How raja76 Handles Your Account Data

This is the raja76 privacy page, written for Indonesia visitors who want a clear read on what we collect, why we collect it, and how long we hold...

Account dataWallet identifiersCookies explainedRetention windowsYour rights
raja76 How raja76 Handles Your Account Data

Policy Posture for Supported Regions

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

HELP CHANNELS

Privacy Contact Paths

Data Request Inbox Email our privacy desk to ask for a...
In-Lobby Chat Open the chat bubble after you sign in...
Account Settings Panel Head to your settings to toggle communication preferences...
WHY THIS PLATFORM

Editorial Trust Signals for This Policy

Reviewed Quarterly

Our policy text is read end-to-end every quarter by the compliance lead who signs off raja76 account flows, so the...

Plain-Language Pass

Each clause goes through a plain-language pass before publication. If a sentence needs a lawyer to decode it, we rewrite...

Version History

We keep a changelog of every privacy edit, dated and summarised, so you can see what shifted between your sign-up...

Named Reviewers

The policy is owned by a named data steward inside raja76, not an anonymous inbox. Escalations reach a human whose...

Processor Register

We publish the list of payment and verification processors that touch your account data, refreshed whenever a new e-wallet rail...

Independent Audit

An external reviewer checks our retention windows and deletion logs once a year, and we update this page if their...

Consistency Across raja76 Policy Pages

DefinitionsThe same defined terms — account data, wallet reference, session log — are used here and on the cookies notice, so you don't have to re-learn vocabulary between policy pages.
Retention WindowsRetention periods quoted on this page match the windows shown on the account-closure page, the KYC notice and the transaction-record page exactly.
Contact RoutesThe privacy inbox listed here is the same address printed on the terms page and the complaints page, so your request lands in one tracked queue.
Jurisdiction WordingWhere local law permits language is used identically across policy pages, keeping the Indonesia-specific carve-outs aligned with the terms of service.
Update CadenceQuarterly review applies to every policy document on raja76, not only this one, so version dates move together rather than drifting apart.
Reader RightsYour access, correction and deletion rights are described in matching wording on the KYC page, avoiding the gap where one page promises more than another.
Processor ListThe processor register referenced here is the canonical list; the cookies page and payments page link back to it rather than maintaining their own copies.
QUICK SIGNAL

What Defines This Policy Layout

Section Anchors Each clause has a stable anchor link so you can...
Last-Updated Stamp A visible date sits at the top of every clause...
Plain Summary Block Above each legal paragraph we place a short summary in...
Reader Rights Panel A fixed panel lists the actions you can take —...
Glossary Tooltips Defined terms are underlined and reveal a one-line meaning on...
Change Log Drawer A collapsible drawer at the foot of the page shows...

Privacy Questions Account Holders Ask

We collect your name, contact handle, date of birth for age checks, the device you sign up on, and the wallet reference you choose. Nothing beyond what the Indonesia account flow needs is stored.

Active account data stays for as long as you use raja76. After closure we hold transaction logs for the period our licence requires, then the record is purged on the schedule published in the retention clause.

Yes. Email the privacy desk or use the in-lobby chat and ask for a data export. We deliver a structured file covering your profile, wallet handles and session history within the window your region sets.

No. Your account data is not sold or rented. We only share processor-level details with the e-wallet rails — DANA, OVO, GoPay, QRIS — that you authorise at checkout, plus identity checkers where law requires.

Closure removes your lobby access immediately. Your record moves into a retention queue for the period set by licence rules, then deletion runs automatically. You receive a confirmation message when the purge completes.

Session cookies keep you logged in; preference cookies remember your lobby layout. Both are described in detail on the cookies notice linked from this page, using the same defined terms you see here.

Use the data request inbox listed in the contact section. A named steward handles the ticket, not general support, and you receive an acknowledgement within one business day along with a tracking reference.