Terms of Service
The Terms describe what you and we promise each other. This privacy policy describes the data side of that promise — the two read together without contradicting any clause.
This is the postogel privacy policy — the page that tells you, in plain words, what we store when you open an account, browse our slot rooms, sit...
We process your personal data on the legal basis of contract performance — you opened an account with postogel, so we need identifiers, contact fields and transaction references to run that account where local law permits. Data tied to your DANA, OVO, GoPay or QRIS top-ups is stored only as a wallet reference, never as full card credentials. We retain records for
the period required by Indonesian financial and gaming rules in supported regions, then we age them out. You can write to us at any time to ask what we hold, request corrections, or close the account. Cross-border transfers, when they happen, follow contractual safeguards we publish on request.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
If anything in this policy needs clarifying for your account, reach us through one of the channels below. Each one routes to the same privacy desk.
This policy isn't a copy-paste. Here's how we keep it honest and current.
Every edit to this privacy policy carries a date stamp at the foot of the page. You can compare older versions on request so nothing changes quietly behind your account.
A named data protection lead inside postogel signs off each revision. That person is the same one your privacy emails reach, not a generic shared mailbox routed through marketing.
We write in short sentences. Where a clause has legal weight, we say so and link the underlying Indonesia rule rather than burying it inside jargon you'd need a lawyer to parse.
This policy covers postogel only. Third-party game studios and wallet providers publish their own notices, and we point to them rather than pretending their handling is ours.
We list how long each category of data sits on our systems. When the clock runs out, the record is purged or anonymised, and that schedule is audited internally.
Material changes are flagged on your account dashboard the next time you sign in, so you don't have to monitor this page yourself to know something moved.
Our policy pages are written as a set. Here's how this one lines up with the rest.
The Terms describe what you and we promise each other. This privacy policy describes the data side of that promise — the two read together without contradicting any clause.
Cookies get a dedicated page because the controls are interactive. This policy summarises categories; the Cookie Notice is where you actually toggle them on or off.
Identity verification has its own statement covering document handling. This policy points to it so you can see why ID images are kept separately from gameplay logs.
Anti-money-laundering checks are referenced here at a high level. The dedicated AML page explains the thresholds and the wallet pattern triggers in more depth.
If a privacy answer doesn't satisfy you, the complaints page sets out escalation. This policy names the first contact; that page names the next two.
Closing your account is covered in the account terms; this policy adds what happens to residual data after closure and the legal hold periods that may apply.
Opt-in choices for emails and push messages live in your account settings. This policy describes the lawful basis; the settings panel is where you actually change them.
These are the building blocks on this page — the layout pieces that make our privacy policy easy to read and act on.
A clean list of what we collect: identifiers you give at sign-up, session telemetry from your lobby visits, and wallet references created when you fund your account through a supported channel.
Each data field is mapped to a purpose. You can see at a glance whether a piece of information is held for account safety, for tax reporting, or for product improvement work.
A short table showing how long each category stays on file. The numbers reflect Indonesian record-keeping obligations and our own internal review cycle, nothing longer.
Access, correction, deletion, portability and objection are laid out as separate rows so you can pick the one you need and follow the steps without scrolling for clauses.
A simple diagram of who receives what. Game studios get session tokens, wallet partners get transaction references, regulators get only what local law requires in supported regions.
At the foot of the page you'll find a dated log of revisions. Hover any line and we show a short summary of what changed and why we made the edit.