Tone
Same plain-English voice across all four policy pages — no document is written tighter or looser than the others, and capitalised legal jargon is avoided everywhere.
This is the pangeran99 privacy policy — a plain reading of what we collect when you open an account, why we keep it, and how long it stays...
We process your personal data where local law permits and only within supported regions. The categories we keep are limited to what your account needs: contact details, verification documents, session logs, and payment routing identifiers tied to DANA, OVO, GoPay or QRIS transactions. We don't sell your data to third parties, and marketing communications stay opt-in. Where Indonesian data-handling rules apply, we
follow them; where cross-border processing is unavoidable for fraud checks, we use contractual safeguards. You can request access, correction or deletion of your record by writing to our policy desk, and we'll respond within a reasonable window.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
We don't treat this document as set-and-forget. Here's the editorial routine behind it so you can see why the wording on this page is current and who signs off on changes when...
Our compliance lead re-reads the full policy every quarter and after any change to our processors. Revised wording lands here with a fresh last-updated stamp at the top.
A single accountable reviewer signs off each version rather than a committee. That keeps tone consistent and means you can ask who approved the wording you're reading right now.
We rewrite legal phrasing into Indonesia-friendly English before publishing. If a clause needs a lawyer to decode it, it gets sent back for a second pass before going live.
Material changes are summarised at the foot of this page with the date and the section affected, so returning readers can see what shifted since their last visit.
Payment routing partners covering DANA, OVO, GoPay and QRIS sign data-handling terms with us, and we review their attestations on the same quarterly cycle as this policy.
If you flag wording that reads as ambiguous, it goes into the next review batch. Several lines on this page exist because readers asked us to be clearer.
This privacy policy sits alongside our terms, cookie notice and account rules. We keep the four documents aligned so you don't get one answer here and a different one two clicks away...
Same plain-English voice across all four policy pages — no document is written tighter or looser than the others, and capitalised legal jargon is avoided everywhere.
Every policy page carries the same date format at the top so you can tell at a glance which document was touched most recently and whether they were refreshed together.
Terms like account, session, processor and supported regions mean the same thing on this page as they do in our terms — we maintain one shared glossary behind the scenes.
Privacy questions land at the privacy desk; billing lands at finance; account locks land at security. Each policy page points to the correct desk rather than a generic inbox.
All four documents use the same where-local-law-permits and supported-regions phrasing, so access conditions read identically whether you're on terms, cookies or this page.
The quarterly review covers privacy, terms, cookies and account rules in the same pass, which prevents one document drifting ahead of the others between updates.
Access, correction, deletion and objection rights are described in matching language on every relevant page, so you don't have to cross-read to understand what you can request.
Beyond the legal text, this page is laid out so you can find the clause you came for without scrolling through everything. These are the on-page elements we've built into the privacy view specifically...