Terms of Service
Account data definitions match exactly. What we call 'verification record' here is the same dataset described in the terms, with identical retention windows.
This privacy policy tells you what we collect when you open a rajamaxx88 account, why we hold it, and how long it stays on our systems. We've written...
rajamaxx88 processes your personal data under privacy expectations recognised where local law permits, with handling tuned to supported regions across Indonesia. We collect what we need to run your account: name, contact channel, verification documents, device fingerprint and payment reference tied to your chosen wallet. We don't sell your data, we don't pass it to advertising brokers, and we don't keep verification
files longer than the retention window our compliance team sets. If a regulator in a supported region requests records, we respond through formal legal channels only. You can request a copy of your stored data, ask for corrections, or close your account and trigger deletion under the timelines listed further down this page.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
If you need to reach our privacy desk directly, use any of the channels below. We route privacy requests separately from general account support so your message lands with the team that...
Our privacy text is reviewed by people, not autogenerated. Here's how we keep this page honest and current for everyone reading it across Indonesia.
Our in-house counsel reads this policy each quarter and flags any clause that drifted from current Indonesia data practice. Changes are versioned so you can see what shifted between reads.
Each revision carries the initials of the editor who signed off. We keep a changelog at the foot of the page so you can match wording changes to a real human reviewer.
We run the text through a readability check so the policy reads at a normal English level for Indonesia readers. Legal precision stays intact; clause stuffing gets cut.
Where we reference a data handling rule, we link the underlying source so you can verify it yourself. No vague claims about standards we don't actually follow.
Older versions of this policy remain accessible on request. If wording changed after your account opened, you can compare both texts side by side through our privacy inbox.
Twice a year we ask an outside reviewer to read the page cold and flag anything unclear. Their notes feed straight into the next revision cycle without internal filtering.
Our privacy policy lines up with the wording you'll see on related rajamaxx88 legal pages. Here's how the key clauses match up so nothing contradicts between documents.
Account data definitions match exactly. What we call 'verification record' here is the same dataset described in the terms, with identical retention windows.
Tracking categories named here mirror the cookie notice. If a cookie isn't listed there, it isn't dropped by us, and this policy doesn't authorise it either.
Identity documents collected for anti-money-laundering checks are the same files referenced in this policy. Storage location and retention timelines are quoted identically in both texts.
The verification flow described on our KYC page uses the data categories named here. No extra fields are requested beyond what this privacy text already lists.
Privacy complaints flow into the same intake form as general disputes, with a separate tag. Both pages quote the same response timeline for acknowledgement and resolution.
Retention figures cited in this policy match the standalone schedule document. If one is revised, the other follows in the same release window with matching effective dates.
Deletion timelines after closure are stated identically across both pages. You won't find one document promising 30 days while another quotes 90.
These are the visible elements that shape how this privacy page reads. We've focused on making the policy itself easy to navigate rather than burying the clauses you...