Terms of Use
Shares the same definitions block as this page. Account, lobby and session are defined once and reused, so a word never means two different things across our policy set.
This is the legal corner of hokiunited. We've kept it short, plain and on-topic so you can scan our terms before you open an account. You'll find how...
hokiunited operates where local law permits and we ask you to confirm eligibility before opening an account. Our terms cover account ownership, accuracy of the details you submit, the records we keep against your session, and how we resolve disputes that touch your lobby activity. Wording is jurisdiction-dependent: clauses that apply in supported regions are flagged inline, and anything market-specific for Indonesia
is written so you don't need a lawyer to read it. We update dates whenever a clause moves, and we keep the previous version on file so you can compare. Payment method context is referenced for clarity only — the legal text itself governs the account, not the wallet.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
If a clause needs clarifying, reach our policy desk directly through any of the channels below. We log every request against your account so the answer stays consistent.
Editorial trust signals on the legal text — who reviews it, how often, and what changes when.
Every clause is re-read by our policy team each quarter. If a sentence no longer matches how the lobby actually works, we rewrite it and date the change at the top of the page.
After legal sign-off, an editor strips jargon. If you can't understand a clause on a phone screen during your commute, we rework it until the meaning is obvious.
Older versions stay on file. Ask support for a specific date and we'll send the snapshot that was live when you opened your account, so the terms you accepted are always retrievable.
Clauses that vary by region carry a footnote naming the supported area. Indonesia-specific notes live alongside the main text rather than buried in a separate document.
Each update is signed off by a named reviewer on our policy team. The initials sit beside the change date so you can see a human stood behind it.
When you next sign in after a policy change, the change log appears at the top of your lobby. You acknowledge it once and we record the timestamp against your account.
How this legal page lines up with our other policy documents so nothing contradicts.
Shares the same definitions block as this page. Account, lobby and session are defined once and reused, so a word never means two different things across our policy set.
Cross-references this page for account ownership clauses. What we collect there matches what we govern here, with identical wording on retention windows and your withdrawal rights.
Sits under the same review schedule. Quarterly pass, named reviewer, dated change log — the cookie text follows the exact cadence you see on this legal page.
Inherits the dispute path from this page. If a clause about lobby behaviour is enforced, the resolution route is the one published in our legal contact section.
References DANA, OVO, GoPay and QRIS as method names but defers to this page on account ownership. The two documents never disagree on whose name the wallet must match.
Built on the records clauses written here. The closure flow uses the same retention windows, so a request you make there has predictable timing set by this document.
Mirrors the escalation order described in our support section. Inbox first, chat queue second, formal records request third — same ladder, same timestamps, same archive.
The visible elements we use to keep our legal text scannable, not a wall of grey paragraphs.