LEGAL REFERENCE

Our Legal Notices, Plain and Current

This is the legal corner of alexisbet — the place where we set out how our account terms, privacy stance and jurisdiction language work. We keep it short...

Account TermsPrivacy StanceJurisdiction NotesPolicy UpdatesCookie Posture
alexisbet Our Legal Notices, Plain and Current

Policy Posture and Jurisdiction Wording

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

PLAYER SUPPORT

Reaching Our Policy Desk

If a clause needs clarifying, contact the legal desk directly rather than the lobby helpdesk — we route the two separately so...

Policy Email Send legal questions, takedown notices and term clarifications...
Privacy Contact Data access and deletion requests go to a...
Compliance Chat Live chat carries a compliance handoff option. Pick...
TRUST MARKERS

How We Edit These Legal Pages

Our policy pages aren't auto-generated. Each section is drafted, dated and signed off before it ships.

Drafted In-House

Clauses are written by our policy team, not lifted from a template. That keeps the wording tied to how alexisbet actually operates rather than to a generic boilerplate that might not match our flow.

Legal Counsel Review

External counsel reviews every material change before it goes live. We log the review date at the head of each section so you can see when the page was last touched by a qualified reader.

Version History

Older versions of the terms stay accessible on request. If you signed up under a previous draft, we can send the exact text that applied on the day your account opened.

Plain Language

We rewrite dense paragraphs into shorter ones where the meaning allows. The legal sense stays intact, but the reading load drops, which matters when you're checking terms on a phone screen.

Dated Clauses

Every clause carries an effective date. That removes guesswork about which version of a rule was active when a dispute, query or account action took place.

Change Notices

Material updates trigger an in-account notice and an email to the address on file. You see the diff before the new wording takes effect on your account.

Consistency Across Our Policy Pages

Our terms, privacy stance and jurisdiction notes are written to line up with each other.

Terms vs Privacy
Where the terms reference data handling, the privacy page carries the matching clause word-for-word. No drift, no contradictions between the two documents.
Privacy vs Cookies
The cookie notice points back to the privacy stance for storage durations, so you read one source of truth instead of two slightly different numbers.
Jurisdiction vs Access
Jurisdiction wording on this page matches the access notice in the lobby footer. Both use the same supported-regions language, dated the same day.
Account vs Identity
Account terms align with the identity-check policy. The clause numbering matches so you can cross-reference between the two without hunting.
Disputes vs Support
Dispute handling in the terms mirrors the escalation path support follows internally. What we promise on paper is what the desk actually does.
Updates vs Notices
Update logs on each policy page share a common date format and changelog style, which makes scanning revisions across documents quick.
English vs Indonesian
English clauses and Indonesian-language summaries are versioned together. When one changes, the other is reissued so the two stay in lockstep.

What Defines Our Policy Layout

A few editorial choices shape how this legal section reads and behaves on your screen.

Top-of-Page Dates

Every policy document carries its effective date at the top, in bold, before the first clause. You see the freshness of the text before you commit any reading time to it.

Clause Anchors

Each clause has a deep link. If support quotes a section number to you, the link drops you straight to that paragraph rather than the page top.

Plain-Language Sidebars

Dense legal paragraphs sit next to a short plain-language summary. The legal text governs, but the summary helps you decide whether to read further.

Mobile-First Layout

Policy pages are formatted for phone reading first. Line lengths, font sizes and spacing are tuned so a clause fits a thumb-scroll without horizontal swiping.

Print-Friendly Export

A print stylesheet strips the navigation and renders the document as a clean A4 sheet. Useful if you want a physical copy of the terms in force on your account.

Change Diff View

Recent updates show a side-by-side diff of the previous and current wording, so you don't have to guess which sentence shifted between two versions of the same clause.

Legal Questions We Hear Often

They apply to alexisbet accounts opened from supported regions where local law permits. The jurisdiction clause names the regions covered and is dated, so you can confirm the version in force when your account opened.

Send a written request to our privacy contact from the email on file. Include your account handle and the date range you want covered. We respond within the window stated in the privacy stance.

Material changes trigger an in-account notice and an email before the new wording takes effect. The previous version stays accessible on request, with the diff visible on the policy page header.

The English text governs. Indonesian-language summaries are provided to help reading and are issued alongside each English revision, but where wording differs the English clause is the controlling version.

Disputes follow the escalation path set out in the terms — internal review first, then policy desk, then external mediation if needed. Each step has a stated response window and a written record on your account.

No. Mentions of DANA, OVO, GoPay and QRIS in our policy pages describe context only. Actual availability sits in the lobby cashier and is governed by the access notice, not the legal text.

Yes. Email the policy desk with the date or version number you need and we'll send the exact text that was in force, along with the changelog entry that retired it.