LEGAL REFERENCE

Our Privacy Policy, Written Plainly

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

Account DataIndonesia ScopePlain EnglishYour RightsUpdated Regularly
uya 123 Our Privacy Policy, Written Plainly

How We Handle Your Account Data

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

24/7 SUPPORT

Privacy Contact Paths

Reach our privacy desk through any of the channels below. We answer in en-ID and route data requests to a named handler.

Privacy Inbox Email [email protected] with your account handle and the...
In-Lobby Chat Open the chat bubble after you sign in...
Postal Channel For formal notices you can post a signed...
EDITORIAL CLARITY

Editorial Trust Signals For This Policy

This policy is reviewed by named people, not auto-generated. Here is who touches it and how often.

Named Reviewer

Our data lead signs off each version of this page before it ships. Their initials and the review date sit...

Quarterly Refresh

We revisit the wording every three months, or sooner if a supported region updates its rules. Material changes are flagged...

Plain-Language Pass

Every clause goes through a plain-English edit. If a sentence needs a lawyer to decode, we rewrite it. You shouldn't...

Indonesia Scope

The policy is written against Indonesian data expectations first. References to DANA, OVO, GoPay and QRIS are scoped to how...

Vendor Audit

Every processor that touches your data is logged in our internal register. We review their security posture annually and drop...

Change Log

Each edit to this page is recorded with a date stamp and a short note on what moved. You can...

BENCHMARKED

Consistency Across Our Policy Pages

This privacy policy lines up with our other legal documents. Here's how the pieces fit so nothing contradicts.

01

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.

02

Cookie Notice

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.

03

AML Notice

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.

04

Payment Disclosure

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.

05

Complaints Charter

The complaints charter points back here for any privacy-flavoured grievance. Response windows quoted there match the working-week target written into this policy.

06

Account Closure

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.

07

Regional Annex

Our regional annex for supported Indonesia areas extends this policy without overriding it. If the annex differs, the stricter clause wins, in your favour.

SERVICE CONTEXT

Brand Elements On This Policy Page

These are the visible pieces that frame this policy on screen — layout cues, not payment chips.

Top Banner A short banner at the top names the document and...
Section Anchors Each clause has its own anchor link. Copy it from...
Plain Summary Every long clause opens with a one-line summary in bold...
Inline Definitions Terms like processor, controller and identifier are defined inline the...
Request Buttons Export, correct and delete sit as buttons at the foot...
Version Footer The footer of this page carries the version number, review...

Privacy Policy Questions

Your registration email and phone, the device fingerprint of the browser you sign in from, and the e-wallet reference you link for top-ups. Nothing more is needed to run your lobby session day to day.

Only the minimum needed to settle a top-up or withdrawal — your account reference and the amount. The rails don't see your lobby activity, and we don't push marketing data to them in either direction.

For the period local law in your supported Indonesia region requires, then we delete or anonymise. Most records sit on a five-year clock from your last sign-in, set by financial record-keeping rules rather than us.

Yes. Open a ticket from the request buttons at the foot of this page or email the privacy inbox. We confirm receipt the same day and complete deletion inside five working days where law permits.

Material edits are flagged on your dashboard the next time you sign in, and the version footer at the bottom of this page updates immediately. Minor edits go into the change log without an alert.

Our named data lead signs off each version, with a quarterly review baked into the calendar. Their initials and the date sit at the foot of the page so you can see the document is genuinely current.

The core clauses apply everywhere we operate, but our regional annex extends the policy for specific supported Indonesia areas. Where the annex is stricter than this page, the stricter wording wins in your favour.