LEGAL REFERENCE

Terms & Conditions for Your rajalotre Account

These Terms & Conditions set the rules between you and rajalotre when you open an account, browse our slot rooms, sit at a live table or place a...

Account RulesLobby AccessPolicy PostureIndonesia ScopeLast Updated
rajalotre Terms & Conditions for Your rajalotre Account

Policy Scope, Eligibility and Account Conduct

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

PLAYER SUPPORT

Policy Contact Paths

If a clause on this page is unclear, reach us before you place a session. Our policy desk handles wording questions, jurisdiction...

Policy Email Send wording queries, clause references or jurisdiction questions...
Live Chat Desk Open the chat bubble inside your account and...
Written Notice For formal disputes tied to these Terms, send...
WHY VISITORS TRUST US

How We Review This Policy

These Terms are not a copy-paste template. Our editorial and compliance leads review the wording on a fixed cycle so the document matches the lobby you actually see when you sign in.

Drafted In-House

Our compliance writers draft each clause against the live product, so what you read here mirrors the account flow, lobby behaviour and session rules running on rajalotre today.

Quarterly Review

We revisit every section on a quarterly schedule and stamp the page with the revision date. Older versions stay archived for your reference if a clause changes mid-session.

Plain Wording

We strip legalese where we can. If a clause must stay technical for jurisdiction reasons, we add a short note underneath so you understand the practical effect on your account.

Dual Sign-Off

No clause goes live until both our policy lead and product owner sign it off. This stops the Terms drifting away from how the lobby and sportsbook actually behave.

Version History

Every amendment is logged with a date, a short summary of what changed and the reason. You can request the archive through the policy inbox at any time.

Reader Feedback

If you flag a clause as confusing, it goes into the next review cycle. Several sections on this page exist because account holders asked us to spell something out clearly.

Consistency With Our Other Policy Pages

This page sits inside a small family of policy documents. We keep the wording aligned so one clause never contradicts another.

Privacy Policy
Terms cover account conduct and lobby rules; the Privacy Policy covers what data we hold and why. The two cross-reference each other where account verification is discussed.
Cookie Notice
Cookie behaviour sits in its own notice. These Terms only reference cookies where session integrity or login persistence is tied to a specific account rule.
AML Statement
Anti-money-laundering checks are summarised here and detailed in the AML Statement. Both pages share the same definitions for verification holds and source-of-funds requests.
Promo Rules
Campaign-specific wording lives on each promo card. These Terms set the umbrella rules; the card sets the campaign rules; if they conflict, the campaign card wins.
Sportsbook Rules
Market settlement, void conditions and dead-heat handling sit in the Sportsbook Rules. These Terms govern your account; the Sportsbook Rules govern your market.
Casino Rules
Game-specific behaviour, disconnection handling and round validity are covered in the Casino Rules. These Terms apply on top, not instead.
Dispute Process
The escalation ladder is summarised in clause form on this page and expanded in the Dispute Process document. Timelines and contact addresses match across both.

What Defines This Policy Page

A few structural elements run through every clause on this page. They are not legal jargon — they are the design choices that keep the document...

Dated Revisions

Each clause carries the revision date in the source file. When you scroll the page you always see when the wording last moved, so you can match it against your account history.

Numbered Clauses

Every paragraph is numbered. If our policy desk replies to your query, the answer cites the clause number so you can jump straight back to the exact wording.

Jurisdiction Notes

Where a clause depends on regional law, a short note flags it. You see immediately whether the rule applies to your supported region or to a different market.

Defined Terms

Words like Account, Session, Lobby and Market carry capitalised definitions at the top. The same definitions run through every other policy page on rajalotre.

Change Log

A short change log sits at the foot of the page. It names the clause that moved, the date and a one-line summary of the edit.

Plain Summary

Heavier clauses include a one-line plain summary in italics underneath. The legal wording still controls, but the summary tells you the practical effect on your account.

Common Questions About These Terms

From the moment you submit your registration form on rajalotre. Ticking the agree box confirms acceptance, and the Terms remain in force until your account is fully closed and any open sessions are settled.

We post the revised wording on this page with a new date and a short change-log line. Continued use of your account after the update means you accept the new clause in full going forward.

They apply to every rajalotre account where local law permits access. Jurisdiction notes inside specific clauses flag any rule that behaves differently for a supported region versus a restricted one.

Only at a high level. DANA, OVO, GoPay and QRIS handling is referenced here, but transaction limits, processing windows and refund timing live inside the dedicated payments policy linked from this document.

Send a written notice through the contact form marked Legal. We log the timestamp, assign a case number and respond within the windows set out in the dispute clause of these Terms.

Yes, where verification fails, where a clause is breached, or where a regulator requires it. We notify you in writing, name the clause we relied on, and explain what you can do next.

Every revision is archived. Email the policy desk with the date range you need and we'll send the prior wording, the change-log entry and the reason the clause was updated.