LEGAL REFERENCE

Legal Notices for Your idr138 Account

This is the legal corner of idr138 — the page where we set out the terms behind your account, the jurisdictional limits we operate under, and how our...

Account TermsJurisdiction NotesPrivacy PosturePolicy ContactsDispute Path

View Game Library Read FAQ

Policy Posture and Jurisdiction Statement

Our legal posture is built around supported Indonesia regions and the wording we use throughout the policy set is intentionally consistent: services are made available where local law permits, and accounts are opened on that basis. We publish our terms, privacy notice, cookie statement and account-closure policy as a single connected set, so when you read one document the others line up

with it. If a clause changes, we date the revision and keep the previous wording archived so you can compare. Disputes follow the path described in the support card row below, and our policy team logs every contact for traceability.

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

24/7 SUPPORT

Policy Contact Paths You Can Use

Team online

Policy Inbox

Email our legal desk directly when you need a written record of a query about terms, privacy or account closure. We log each message and reply within the window stated in our service standards page.

In-App Policy Chat

Open the chat widget from any page footer and tag your message as policy-related. The agent routes it to the legal queue rather than general support, so the reply comes from someone trained on the document set.

Dispute Escalation

If a first reply doesn't resolve your point, ask for escalation in writing. Our senior policy reviewer picks it up, re-reads the relevant clause with you, and confirms the outcome in a follow-up note.

WHY THIS PLATFORM

Editorial Trust Signals Behind These Notices

Versioned Clauses

Every clause carries a revision date. When we update wording, the older text stays accessible so you can see exactly what changed and when, instead of finding a silently rewritten paragraph on your next visit.

Plain-English Drafting

Our policy team rewrites legalese into readable English before publishing. The intent of each clause is summarised in the opening line so you don't have to parse three paragraphs to find the rule.

Internal Review Cycle

Two reviewers sign off on each policy edit — one from operations, one from compliance. That cross-check keeps the document set internally consistent and stops contradictions creeping between terms and privacy.

Indonesia-Aware Wording

References to access, eligibility and payments are framed for supported Indonesia regions, with DANA, OVO, GoPay and QRIS named where they appear in the operational flow rather than buried in footnotes.

Traceable Decisions

Policy decisions about your account are logged with reference numbers. When you ask why something was applied, we can point at the specific clause and the timestamp behind it.

Archived Versions

Superseded policy versions remain available on request. If you opened your account under earlier wording, you can ask us for that exact text and compare it line by line with the current set.

Consistency Across Our Policy Documents

Terms vs Privacy

Both documents use the same defined words for account, session and identifier, so you won't read one rule in terms and a contradicting one in privacy.

Privacy vs Cookies

The cookie statement extends the privacy notice rather than restating it, keeping data-handling language in one place and tracking technology details in another.

Terms vs Closure

Account closure rules in the terms link directly to the closure policy, so the steps and timelines you read match across both pages without rewording.

Disputes vs Support

Dispute language in the legal set mirrors the escalation steps shown on the support page, with identical contact routes named on both sides.

Eligibility vs Access

Eligibility wording in terms uses the same supported-regions phrasing the access notice uses, so there's no gap between who can open an account and who can reach the lobby.

Payments vs Policy

Where DANA, OVO, GoPay and QRIS appear in operational pages, the policy set references them with the same names and the same scope wording.

Updates vs Archive

The change log on each policy points to the archived prior version, keeping the update history symmetric across every document we publish.

Brand Elements Defining This Policy Layout

Document Index

A sidebar index lists every policy document in the set so you can jump from terms to privacy to closure without backtracking through menus or losing the clause you were reading.

Clause Anchors

Each clause carries a stable anchor link. When our support team references a rule, they paste the anchor and you land on the exact paragraph instead of scrolling through the page.

Revision Banner

A small banner at the top of each policy shows the last revision date and a link to the change summary, so you immediately see whether the wording has shifted since your last read.

Defined Terms Panel

Hovering a defined term opens a short panel with its meaning. The panel pulls from a single glossary, keeping definitions identical wherever the term appears.

Print-Ready Layout

Each policy page renders cleanly when printed or saved as PDF, with headers and clause numbers preserved so your offline copy matches the online structure exactly.

Contact Footer

Every policy ends with the same contact footer pointing to our legal inbox and escalation path, so you never have to search for the right channel after finishing a document.

Questions About Our Legal Notices

They apply to accounts opened from supported Indonesia regions where local law permits the service. The eligibility clause in our terms sets out the specific scope and we keep that wording aligned across the rest of the policy set.

Each document carries a revision date and a change-summary link in the top banner. We don't silently edit clauses — every update is logged, dated, and the previous version stays available if you want to compare wording.

Two internal reviewers sign off on every edit: one from operations and one from compliance. That cross-check is the reason terms, privacy and closure documents stay consistent with each other rather than drifting apart.

Email our policy inbox or open the in-app chat and tag the message as policy-related. If the first reply doesn't resolve your point, ask for escalation and a senior reviewer will pick it up directly.

Yes. Superseded versions are archived and available on request. If you opened your account under earlier wording and want to see that exact text, our policy team will send the archived copy with its revision date.

They're named because the policy set references the same payment routes the operational pages use. Keeping the names identical across documents avoids gaps between what you read in terms and what you see at checkout.

No. Check the revision banner at the top of each policy — if the date hasn't moved since your last read, the wording is unchanged and there's nothing new to review before heading back to your account.