Terms of Service
The terms reference this policy by name when account data is involved. Wording on retention, deletion and processor scope matches across both documents — no gap, no surprise.
This is the uya 123 privacy policy. We wrote it so you can see exactly what account data we collect when you open a lobby session, how we...
We collect only what your account needs: the email and phone you register with, the device you sign in from, and the e-wallet reference you link for top-ups. Where local law permits in Indonesia, we keep this data for the period required to run your lobby, settle balances, and meet record-keeping duties. We don't sell your data. We share it with payment
partners — DANA, OVO, GoPay and QRIS rails — strictly to move your funds, and with regulators when a supported region requires it. You can ask us to export, correct or delete your record at any point, and we'll confirm the action by email within a working week.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
This policy is reviewed by named people, not auto-generated. Here is who touches it and how often.
Our data lead signs off each version of this page before it ships. Their initials and the review date sit...
We revisit the wording every three months, or sooner if a supported region updates its rules. Material changes are flagged...
Every clause goes through a plain-English edit. If a sentence needs a lawyer to decode, we rewrite it. You shouldn't...
The policy is written against Indonesian data expectations first. References to DANA, OVO, GoPay and QRIS are scoped to how...
Every processor that touches your data is logged in our internal register. We review their security posture annually and drop...
Each edit to this page is recorded with a date stamp and a short note on what moved. You can...
This privacy policy lines up with our other legal documents. Here's how the pieces fit so nothing contradicts.
The terms reference this policy by name when account data is involved. Wording on retention, deletion and processor scope matches across both documents — no gap, no surprise.
Cookie categories listed in the cookie notice match the data buckets named here. If you reject a category there, the matching processor here stops receiving your identifier.
Anti-money-laundering checks store the same identifiers we describe in this policy. Retention windows are aligned with the period stated under our account data clause.
References to DANA, OVO, GoPay and QRIS in the payment disclosure use identical scoping language to this page, so your e-wallet data is treated the same wherever it appears.
The complaints charter points back here for any privacy-flavoured grievance. Response windows quoted there match the working-week target written into this policy.
The closure flow honours the deletion clause on this page. Once you close, the same retention window applies — nothing is held longer than this policy permits.
Our regional annex for supported Indonesia areas extends this policy without overriding it. If the annex differs, the stricter clause wins, in your favour.
These are the visible pieces that frame this policy on screen — layout cues, not payment chips.