How pgs88 Handles Your Account Data
This is the pgs88 privacy policy — the plain rundown of what we collect when you open an account, why we hold it, and how long it stays...
Our Privacy Posture and Data Scope
We collect the minimum needed to run your account: your registration details, the device you sign in from, the e-wallet reference you choose, and the lobby actions tied to your session. None of this is sold to third parties. Where local law permits, we share fragments only with licensed payment partners so your DANA, OVO, GoPay or QRIS transfer can clear. Retention
windows follow the supported regions we operate in, and any record tied to a closed account is purged on the schedule set by our compliance team. If a regulator requests data through proper channels, we respond inside the legal window — nothing more, nothing less.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
How We Keep This Policy Honest
Editorial Sign-off
Every change to this policy is reviewed by our in-house compliance editor before it goes live. We do not push...
Legal Review
Outside counsel checks the wording against current Indonesia data-handling expectations. Where supported regions differ, we note the variance instead of...
Encryption Standard
Your registration details, wallet references and session tokens move over TLS and sit encrypted at rest. We rotate keys on...
Access Discipline
Only staff who need to see a record to do their job can open it. Marketing never touches raw payment...
Breach Protocol
If something goes wrong, we tell affected account holders directly and post a public note. No quiet patches, no delayed...
Version History
Every prior version of this policy is archived on our side. Ask through the privacy inbox and we will send...
Consistency Across Our Policy Pages
| Scope Match | This page covers your personal data only. Cookie behaviour, terms of service and bonus rules each sit on their own page so the wording here stays focused and the legal scope stays clean. |
|---|---|
| Definitions | Words like account, session, wallet reference and supported regions mean the same thing on every policy page we publish. We keep a shared glossary so nothing drifts between documents. |
| Update Cadence | All policy pages share a single review calendar. When one moves, the others are checked the same week so cross-references never point at outdated clauses. |
| Jurisdiction Wording | Where local law permits appears across every policy doc with identical meaning. We do not soften it on one page and tighten it on another to suit the topic. |
| Contact Routes | The same privacy inbox and chat queue handle questions on any policy page. One route, one logged ticket, one written answer — never a runaround between teams. |
| Retention Tables | Retention windows quoted here match the figures on our terms page. If a number changes, both pages update in the same release with the new effective date noted clearly. |
| Reader Tone | Plain English with Indonesia context runs through every policy page. No legalese walls, no buried clauses, no marketing creeping into the parts that should stay strictly informational. |