Our Legal Posture, Plain and Readable
This is the tnb11 legal hub — the page where we set out the terms behind your account, the jurisdiction wording we follow, and the policy contacts you...
Account Terms and Jurisdiction Wording
tnb11 operates where local law permits, and our terms are written around that posture. When you open an account, you confirm you're accessing us from a supported region and that you meet the age threshold set by your local rules. We log policy versions, so if our terms shift, your account view shows the change date and a short note explaining what
moved. Disputes follow the resolution path described in our user agreement: first contact our policy desk, then escalation if we can't close the matter inside ten working days. Payment context — DANA, OVO, GoPay and QRIS — is covered under separate cashier terms linked from your wallet panel.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
Policy Contact Paths You Can Use
If a clause needs clarifying or you want a copy of the terms in force on the day you registered, our policy desk handles those requests directly. We keep these channels separate from general support so legal questions get a written answer with a reference number you can quote later.
Policy Desk Email
Send clause questions, term-version requests or jurisdiction queries to our policy inbox. We reply with a written reference number, and we archive the thread against your account so future requests can pick up where the last one left off.
In-Account Ticket
Open a legal ticket from inside your account panel and we route it straight to the policy team. This path is preferred for anything that touches your specific terms version, since we can attach the relevant document directly.
Escalation Line
If a matter isn't closed within ten working days, the escalation line lifts your case to a senior reviewer. We keep this contact reserved for unresolved policy disputes so it stays responsive when you genuinely need it.
How We Keep Policy Pages Honest
Our legal content is reviewed on a fixed cadence and signed off before it reaches your screen. The signals below describe how the policy side of tnb11 is maintained, who touches it...
Versioned Terms
Every policy update carries a version stamp and an effective date. You can request the version active on the day you opened your account, and we'll send the exact document with no edits applied after the fact.
Named Reviewers
Each policy page is signed off by a named reviewer on our compliance side. We log who approved which clause and when, so any later question can be traced to a specific decision rather than a vague team note.
Change Log
A running change log sits behind every legal page. When wording shifts, the log captures the old text, the new text, and a one-line reason — useful when you want to confirm a clause moved between two visits.
Indonesia Awareness
Our policy team writes with Indonesian regional context in mind, including how DANA, OVO, GoPay and QRIS interact with cashier terms. That keeps the wording relevant rather than generic boilerplate copied from another market.
External Counsel
We retain external counsel to review high-impact clauses before they go live. Their input is recorded against the version they reviewed, giving the document an outside check beyond our internal compliance pass.
Reader Feedback Loop
If a clause reads ambiguously, you can flag it from the page itself. Flagged items go into the next review cycle, and we publish a short note when wording changes as a direct result of reader feedback.
Consistency Across Our Policy Pages
Our legal section is split across several pages — terms, privacy, cookies, cashier rules — and they're written to a shared standard. The points below show what stays...
| Shared Definitions | Key terms like account, supported region and policy version mean the same thing on every legal page. We maintain a single glossary, so a clause referencing one of these phrases carries identical meaning across documents. |
|---|---|
| Single Effective Date | When we publish a policy update, all affected pages receive the same effective date. That avoids the situation where one document references a rule that another hasn't picked up yet. |
| Matched Jurisdiction Wording | Phrases such as where local law permits and supported regions are reused identically. You won't find one page softening the wording while another tightens it on the same underlying point. |
| Linked Cashier Terms | Anywhere a policy page touches payments, it links to the cashier terms rather than restating them. That stops the same rule drifting into two slightly different versions across the legal section. |
| Aligned Contact Paths | Every policy page points to the same contact channels — policy desk email, in-account ticket, escalation line — so you never have to guess which route applies to which document. |
| Uniform Review Cadence | All legal pages sit on the same review cycle. When one is refreshed, the others are checked in the same pass, even if no changes are needed, and the review date is logged. |
| Consistent Change Log Format | Change logs follow one structure across the whole legal section, so reading the history of the privacy page feels the same as reading the history of the terms page. |
What Defines Our Legal Page Layout
This page is built so policy content stays scannable on a phone. The elements below describe what's actually on the page — the structural pieces we...
Clause Anchors
Each major clause has its own anchor link, so you can share a direct line to a specific paragraph rather than the whole document. Useful when you're discussing a single rule with our policy desk over email.
Effective Date Stamp
A clear effective date sits at the top of every legal page. You'll see when the current wording came into force and, where relevant, the date the previous version was retired so the timeline reads cleanly.
Version Selector
A small selector lets you switch between the live version and previous editions still relevant to existing accounts. Each entry shows the date range and a short summary of what changed.
Plain-Language Notes
Alongside formal clauses, we add short plain-language notes that summarise the intent. The formal text governs, but the notes help you read the page without legal training when you're just looking for a quick answer.
Inline Cross-Links
Where one clause depends on another document — privacy, cashier terms, account rules — we link inline rather than burying references in a footer. The link previews show you the destination before you click.
Reader Flag Button
A flag button next to each section lets you mark wording that reads unclearly. Flags feed straight into the next review cycle, with the originating section and date attached for the reviewer.