LEGAL REFERENCE

How We Handle Your Account Data

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...

Account dataCookies explainedIndonesia readersPlain EnglishLast updated
pangeran99 How We Handle Your Account Data

Policy Posture and Jurisdiction Notes

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

24/7 SUPPORT

Privacy Contact Paths

If something in this policy isn't clear, or you want to exercise a data right, these are the channels we keep open...

Privacy Desk Email Write to our dedicated privacy mailbox with your...
In-Account Request Form Once you're signed in, the settings panel has...
Live Chat Escalation Open chat from any page and ask for...
WHY VISITORS TRUST US

How We Review This Policy

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...

Quarterly Review

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.

Named Reviewer

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.

Plain-Language Rule

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.

Change Log

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.

Processor Audits

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.

Reader Feedback Loop

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.

WHY THIS PLATFORM

Consistency Across Our Policy Pages

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...

01

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.

02

Last Updated Stamp

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.

03

Definitions

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.

04

Contact Routing

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.

05

Jurisdiction Wording

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.

06

Revision Cycle

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.

07

Reader Rights

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.

AT A GLANCE

What This Policy Page Shows You

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...

01
Section Anchors A sticky in-page menu lets you jump straight to data categories, retention, your rights or contact paths. Useful if you've been linked here for one specific clause rather than the whole document.
02
Last Updated Banner The revision date sits at the top of the page in plain view so you don't have to guess whether the wording you're about to read is current or months behind your last visit.
03
Glossary Tooltips Hover any underlined term — processor, retention, supported regions — and the definition appears inline. It saves opening a second tab to check what a clause actually means.
04
Change Summary At the foot of the page we list what moved in the last revision in two or three lines, so returning readers can skim the diff without re-reading the entire document.
05
Quick Request Links Inline buttons next to your rights clauses open the matching in-account request form pre-filled with the right category, so the path from reading to acting is one click.
06
Indonesia Reading Mode Long clauses are split into short paragraphs sized for phone screens, since most Indonesia readers reach this page from mobile rather than from a desktop browser.

Privacy Policy Questions We Hear Often

Your contact details, your verification documents, session and device logs tied to logins, and the routing identifiers for any DANA, OVO, GoPay or QRIS transaction. We don't keep card numbers or full wallet credentials on our side.

We hold the minimum record required by Indonesian financial and anti-fraud rules — typically a few years from closure — then the file is purged. Marketing-tied data drops out earlier, as soon as you opt out or close.

Yes. Use the privacy request form inside your account settings, or email the privacy desk with your account reference. We return a readable export of what we hold, usually inside seven working days from a verified request.

Only with processors who help run your account — payment routers for DANA, OVO, GoPay and QRIS, identity checkers, and fraud screening. They're contracted to handle data on our terms. We don't sell your record to advertisers.

Session cookies keep you logged in and analytics cookies help us see which lobby pages load slowly. The cookie notice has the full list; you can refuse non-essential ones from the banner without losing access to your account.

Where local law doesn't permit access, your account flow is blocked at sign-in and no further data is collected beyond the geolocation check itself. Existing records from supported regions stay handled under this same policy.

The last-updated date at the top moves whenever we revise wording, and material changes are summarised at the foot of the page. Significant shifts also trigger an in-account notice the next time you sign in.