Terms of Use
Mirrors the structure here: jurisdiction posture, account rules, dispute path. Clause numbering is shared so cross-references between Terms and this Legal page always resolve to the same paragraph.
This is the legal home of usd777 — the page where we set out the terms behind your account, the jurisdiction posture we work under, and how our...
We publish our terms, privacy notice and acceptable-use clauses in plain English so you can scan them on a phone before you open an account. Access to usd777 is offered where local law permits, and we use supported-regions language throughout our policy stack rather than blanket claims. If you reach us from a region we cannot serve, the lobby will say so
on entry. Each policy carries a revision date at the foot, and material changes are flagged on your account dashboard before they take effect, so nothing important slips past your notice quietly.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
Every policy we publish carries the initials of the reviewer who signed it off, so you know a real person on our side stands behind the wording rather than an anonymous template pulled from elsewhere.
We keep a public revision log at the bottom of each policy. You can see what changed, when it changed, and which clause numbers moved without having to compare two documents side by side.
Our clauses are drafted in plain English first and legal-checked second. If a sentence needs three reads to parse, we send it back to drafting before it reaches your screen.
Where Indonesian regulation shapes a clause — payment routing, identity checks, regional access — we say so directly in the clause rather than burying it in a generic worldwide footer.
External counsel reviews material policy changes before they go live. Their sign-off date appears alongside our internal reviewer initials so the chain of approval is visible.
If you flag wording that reads ambiguously, we record the comment, route it to the reviewer, and credit the change in the revision log when the next version ships.
Mirrors the structure here: jurisdiction posture, account rules, dispute path. Clause numbering is shared so cross-references between Terms and this Legal page always resolve to the same paragraph.
Uses the same supported-regions language we use here, with an extra section on data retention. Revision dates align with the legal-page footer so a single update touches both.
Lifts its definitions block from this page verbatim, meaning words like account, lobby and supported region carry one meaning across every policy you read on usd777.
Slimmer than this page but inherits our plain-English drafting rule. The reviewer initials and revision log format match exactly so you can scan it in the same rhythm.
Points back to the Policy Desk contact paths listed here. Escalation timelines are stated in hours and business days, not vague phrases, mirroring the precision we hold ourselves to in this notice.
Shares the Indonesia-context callouts you see here, particularly around identity documents accepted for account verification under supported-regions wording.
Every policy change shows up on your dashboard with the same banner format. One read, one click, one acknowledgement — across every document we publish.
Each major clause has a deep-link anchor in the URL so you can share a precise paragraph with our policy desk or with your own advisor without screenshotting and cropping the page yourself.
The footer of every policy block carries the version number, publish date and reviewer initials. One glance tells you whether you are reading current wording or an archived snapshot.
Above each dense clause we publish a short plain-language summary in italics. The legal text still governs, but the summary helps you decide whether the full clause is worth a careful read right now.
Where a rule applies only in certain supported regions, a small callout box names the region context. You will not have to infer applicability from a footnote buried at the bottom.
A clean print stylesheet strips navigation and chrome so a printed or PDF-saved copy reads as a proper document, with page numbers and the revision footer carried through.
Older policy versions stay reachable from a dated index at the foot of the page, so a clause you agreed to last quarter can still be pulled up exactly as it read then.