How uranustoto Handles Your Account Data
This is the uranustoto privacy policy — the page that tells you exactly what we collect when you open an account, what we do with it, and what...
Our Privacy Posture and Scope
Where local law permits, uranustoto processes the data you share at sign-up — name, contact handle, device fingerprint and the e-wallet reference you pick — strictly to run your account and the games you open. We don't sell your details to third parties, and we don't pass your wallet handle outside the payment rails you chose. For supported regions in Indonesia, we
keep records only as long as your account is active or as retention rules require. If you ask us to close the account, we wind down the data trail in line with the same rules. Questions about scope, retention or correction can be raised through the contact paths listed further down this page.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
How This Policy Is Reviewed
We treat the privacy page like a living document, not a one-time legal upload. The signals below show who reviews it, how often, and what triggers an update so you can read...
Quarterly Review
Our compliance lead re-reads this policy every quarter and after any material change in how the lobby collects or stores data, so wording stays in step with what actually happens behind the scenes.
Plain-English Drafting
Drafts are written in everyday English first, then checked against legal counsel notes — not the other way around. That keeps clauses readable for Indonesia members instead of buried in jargon.
Change Log Kept
Every revision is timestamped internally so we can tell you exactly when a clause shifted. Ask the privacy desk and we'll share the relevant entry covering your account window.
Independent Sign-Off
Major rewrites get a second pair of eyes from outside the product team before publication, reducing the chance that a marketing reflex slips into a clause about your data.
Reader Feedback Loop
If a member flags wording as confusing, the note goes into the next review cycle. Several past clarifications around session logs came directly from questions raised through chat.
Aligned With Operations
The policy reflects the actual data flows our engineers run, audited against system diagrams. We don't promise practices the lobby can't deliver, and we don't hide ones it does.
Consistency Across Our Policy Pages
This privacy page is one of several legal documents on uranustoto. The points below show how it lines up with sibling pages so you don't get conflicting answers...
| Versus Terms of Service | Terms cover the rules of using the lobby; this page covers what data those actions generate. Both reference the same account model so definitions stay aligned. |
|---|---|
| Versus Cookie Notice | The cookie notice details browser-side identifiers; this policy covers the wider account dataset. Cross-links sit at the foot of each so you can hop between them. |
| Versus AML Statement | AML wording explains identity checks for payment integrity; privacy explains storage and access of those check results once collected. |
| Versus Account Closure | Closure steps live in the account help page; data retention after closure is described here, ensuring the same retention windows are quoted in both places. |
| Versus Marketing Preferences | Opt-in language in promotional emails matches the consent definitions used in this policy, so toggling off in one place reflects across the system. |
| Versus Complaint Path | The complaints page lists the route for service issues; privacy disputes follow a parallel route described here, with the same response-time commitments. |
| Versus Regional Notes | Where supported regions in Indonesia have specific data rules, those notes appear in both the regional appendix and inside relevant clauses of this policy. |
What This Policy Page Covers
Below are the building blocks you'll find on this privacy page itself — the layout pieces that make it usable rather than a wall of text. Use them...