Privacy Policy
This page — what we collect, why, how long, and your rights over the record. It is the master document for data handling on raja888.
LEGAL REFERENCE
How raja888 Handles Your Account Data
This is the raja888 privacy policy — the page that tells you, in plain language, what we collect when you open an account, why we hold it, and...
Plain-language policyIndonesia-focusedAccount data scopeWallet-awareUpdated regularly
Policy Posture and Jurisdiction Notes
Our privacy posture follows the data rules that apply where local law permits raja888 to operate, and we keep handling consistent across supported regions. When you register, we collect identity fields, contact details, device signals and transaction records tied to your wallet activity. We process this data to run your account, prevent fraud, settle payouts and meet legal record-keeping windows. We do
not sell your personal information. Third parties who help us — payment processors, KYC vendors, hosting providers — see only the fields they need, under written terms. You can ask us to access, correct or erase your data at any point, subject to retention rules.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
WHY VISITORS TRUST US
How We Review This Policy
Legal Review
Our retained counsel reads every clause before it ships. They check that the wording matches Indonesia data expectations and that...
Versioning
Each revision carries a date stamp and a short change note at the foot of the page, so you can...
Internal Audit
Our compliance lead audits data handling against this written policy quarterly. Gaps go onto a tracked remediation list, and the...
Vendor Vetting
Every processor that touches your data signs a written agreement covering scope, retention and security. We refuse vendors who cannot...
Staff Training
Anyone on our team who can see account records completes privacy training before access is granted, and refresher sessions run...
Incident Process
If something goes wrong, our incident playbook sets notification steps, timelines and the contact tree. You hear from us directly...
PLATFORM COMPARISON
Consistency Across Our Policy Pages
Cookie Notice
Sister page covering browser storage, analytics tags and the consent banner. Wording mirrors this policy on retention timelines and lawful basis language.
Terms of Service
Sets the contract between you and raja888. References this privacy policy whenever account data, KYC or payout records come up inside a clause.
KYC Statement
Explains identity verification specifically. Uses the same definitions for personal data and the same vendor list disclosed in this privacy policy.
Account Closure
Closure clauses point back here for retention rules, so the period your records remain on file matches what this policy commits to publicly.
Marketing Preferences
Opt-in and opt-out choices live in your account settings, and the descriptions there use the same lawful-basis language printed on this privacy page.
Data Requests
Form-based access and erasure requests follow the response windows set out in this document, with no shorter or longer timelines hidden elsewhere.
What This Policy Page Shows You
Scope Summary
A short summary at the top tells you which raja888 services the policy covers, so you do not have to read the full clause set to confirm your account is in scope.
Last Updated Stamp
The footer date stamp shows when wording last changed. We keep this visible rather than buried, so you can decide whether a re-read is worth your time.
Plain-Language Boxes
Each clause has a plain-language gloss next to the formal wording. The legal text still governs, but the gloss helps you grasp the point without a dictionary.
Your Rights Block
A dedicated block lists access, correction, erasure, portability and objection rights, with a one-line description of how to exercise each through your raja888 account.
Retention Table
A simple table shows how long each data category stays on file. No vague phrases — actual periods, tied to the legal or operational reason behind them.
Change History
At the bottom we list previous versions with their dates, so you can see how the raja888 privacy policy has evolved rather than only the current text.
Privacy Policy Questions
We collect identity fields you submit at registration, contact details, KYC documents, device and session signals, and transaction records tied to wallet activity. Each category is listed in the retention table further up this page.
Identity verification is required where local law permits us to operate. Documents confirm you are the account holder, prevent someone else opening an account in your name, and let us release payouts to the right wallet safely.
Retention varies by category. Transaction records sit on file for the period local financial law sets, while marketing preferences clear sooner. The retention table on this page lists each window precisely for you.
Yes. Submit an erasure request through the privacy email or in-lobby chat. We will erase what we are not legally required to retain, and we will tell you which records must remain and why.
We share only with processors who help us run the service — payment partners, KYC vendors, hosting and analytics providers. Each one is bound by written terms and sees only the fields needed for their specific function.
Material changes are flagged on your next login and the date stamp at the foot of the page updates. The change history block keeps older versions accessible so you can compare wording side by side.
We log the wallet brand you used — DANA, OVO, GoPay or QRIS — plus transaction references and timestamps. Full instrument numbers stay with the payment processor, not on raja888 systems, by design.