Our Privacy Policy in Plain Language
This is the ug125 privacy policy page, and it explains exactly what we collect when you open an account, how we store it, and the choices you have...
Policy Posture and Jurisdiction Scope
Our privacy policy applies wherever local law permits you to hold a ug125 account, with Indonesia treated as a supported region under en-ID terms. We collect the data you submit at signup — name, contact handle, device fingerprint and the e-wallet reference you link for funding — and we keep it only as long as your account is active or local retention
rules require. We process this data to verify identity, run your sessions, prevent fraud, and reconcile DANA, OVO, GoPay and QRIS transaction references against your wallet. We don't sell your records. Where supported regions ask for breach notification, takedown or correction rights, we honour those routes through the contact paths below.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
Privacy Contact Paths
Privacy Inbox
Email our privacy desk if you want to see, correct or delete the records tied to your ug125 account. We reply within the window required by your supported region's data rules.
In-App Chat
Open the chat tile inside your account and ask for the privacy team directly. They handle data export, consent withdrawal and cookie preference resets without bouncing you between agents.
Postal Channel
For formal data requests that need a paper trail, write to our registered address listed in the footer. We log the request the day it arrives and confirm receipt back to you.
How This Policy Is Reviewed
Quarterly Review
Our privacy policy is read end-to-end every quarter by the team that runs your account flow, so wording stays aligned with how the lobby, wallet and KYC steps actually behave today.
Indonesia Counsel
We brief Indonesia-facing legal counsel on changes before they go live, ensuring the en-ID phrasing matches local data expectations rather than a translated template lifted from another market.
Versioned Drafts
Every revision of this policy is dated and archived. If a clause changed last month, we can show you the previous wording and the reason we updated it.
Named Owner
A single privacy owner signs off each release. That person's role and contact route are reachable through the support channels, not hidden behind a generic webform.
Independent Audit
Our data handling for DANA, OVO, GoPay and QRIS reconciliation is sampled by an external auditor each year, with findings folded into the next policy update you read here.
Reader Feedback
If a clause confuses you, tell us. We log plain-language complaints and rewrite sections that readers flag as unclear, because a policy nobody understands protects nobody.
Consistency Across Our Legal Pages
| Terms of Service | Our terms set the contract; this privacy policy explains the data side of that contract. Definitions for account, wallet and session are kept identical across both documents. |
|---|---|
| Cookie Notice | The cookie notice drills into tracker categories. This page references it but doesn't duplicate the table, so you only update preferences in one place. |
| KYC Statement | Identity checks are described here at a high level and detailed in the KYC statement. Both pages list the same document types we accept from Indonesia residents. |
| Payment Terms | DANA, OVO, GoPay and QRIS handling appears in payment terms for timing rules, and here for data flow. The two are written to be read side by side. |
| Complaints Path | The complaints page covers how to escalate a dispute. Privacy-specific complaints reuse that same intake so you never get bounced between forms. |
| Account Closure | Closure mechanics live on the account page. Here we cover what happens to your data after closure and how long retention runs. |
| Marketing Consent | Opt-in toggles sit in your account settings. This policy explains the legal basis behind each toggle so the two never contradict each other. |