How rajabuaya Handles Your Account Data
This is our privacy policy in plain English. We tell you what we collect when you open an account with rajabuaya, why we keep it, and how long...
Policy Posture and Indonesia Jurisdiction Notes
We process your details where local law permits and only for supported regions across Indonesia. When you register, we collect your name, contact channel, date of birth and the e-wallet handle you choose to fund your account with. We retain verification records for the period required by financial-services rules, then archive or remove them. You can ask us to export or correct
your data at any point — write to our policy desk and we'll respond inside seven working days. Third-party processors who help us run payouts and fraud screening are bound by the same confidentiality terms we hold ourselves to, and they only see the fields they need to complete the task you've asked for.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
How We Review This Policy
Legal Review
Our in-house counsel checks every clause against current Indonesian data-protection rules. When wording shifts in the law, we update the page and stamp the revision date at the foot so you can track changes.
Security Team Sign-off
The team that runs encryption and access controls signs off on each draft. They confirm the policy matches the technical reality — what we say we store is what's actually in the database.
Independent Audit
An external auditor reviews our handling of account records once a year. Their findings feed straight into the next policy revision rather than sitting in a filing cabinet somewhere.
Plain-Language Edit
After the lawyers finish, an editor rewrites dense passages into sentences you can actually read on a phone screen. We'd rather you understand the policy than be impressed by it.
Version History
Every change to this page is logged with a timestamp. If you want to see what the wording looked like six months ago, ask the privacy desk and we'll send the archived copy.
Indonesia Focus
Because we serve Indonesia, the policy is written around local payment flows — DANA, OVO, GoPay and QRIS — rather than copy-pasted from a generic global template that ignores how you actually fund an account.
Consistency Across Our Policy Pages
| Privacy vs Terms | This page covers data only. Our terms-of-use page handles account conduct, settlement rules and dispute steps. The two are written to dovetail without repeating each other. |
|---|---|
| Privacy vs Cookies | Cookie behaviour sits on a separate notice. There you'll find the analytics tags, session cookies and the toggle to switch optional tracking off. |
| Privacy vs KYC | Verification rules live on the KYC page. This privacy policy explains where those documents go after you upload them and how long we hold them. |
| Privacy vs Payments | The payments page lists supported wallets and timings. Privacy explains which payment fields we store and which we pass straight to the processor without retaining. |
| Privacy vs Marketing | Promo communication preferences are described here in summary and managed in the account panel. Marketing campaigns themselves run under our promo terms. |
| Privacy vs Security | Security details — encryption standards, login alerts — are referenced here and detailed in full on the security overview elsewhere on the site. |
| Privacy vs Support | Our support charter sets response times across channels. Privacy requests follow the same charter, with a dedicated reviewer for data matters. |