Terms of Service
Account-level rules live in Terms. This legal page summarises and points to the binding clauses there, so the two pages always tell you the same story.
This is the legal corner of berkah99. Here we set out the policy terms that sit behind your account, our lobby and the sportsbook you open each day...
berkah99 operates for Indonesia visitors where local law permits, and we apply the same policy across supported regions. Your account agreement covers identity checks, fair-use rules, dispute steps and the way we hold balances tied to DANA, OVO, GoPay and QRIS references. We update clauses when regulation shifts, and we date every revision at the foot of this page. Nothing on the
lobby overrides what's written here: if a promo card and a clause disagree, the clause wins. Read the section that matches your situation, then reach our policy desk if anything reads unclearly to you.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
If a clause needs clarifying, or you want a written copy of a specific term, our policy desk handles it directly. We keep three contact paths open so you can pick the...
Every clause on this page goes through review before it appears. We treat policy text the same way we treat lobby code — versioned, dated and signed off.
Each policy clause carries a version number, so when you ask which wording applied on a given date, we can pull the exact text from our archive and send it back to you.
We stamp the foot of this page with the last review date. If nothing has changed in a quarter, the date still moves so you know we've checked the text against current rules.
Our policy writers draft with Indonesian payment habits in mind, which is why DANA, OVO, GoPay and QRIS references sit inside clauses rather than as a footnote tagged on the end.
After legal sign-off, an editor rewrites dense clauses into shorter sentences. The legal meaning stays, but you don't need a lawyer beside you to understand what you're agreeing to.
Two reviewers must approve any clause change before it goes live. One checks legal accuracy, the other checks that the wording matches what your account screen actually does in practice.
When a rule shifts, this page updates before any marketing card mentions it. That order is deliberate so the binding wording is always the wording you saw first on berkah99.
This notice sits beside our other policy pages, and we keep the wording aligned so you don't get one rule on one page and a different one elsewhere.
Account-level rules live in Terms. This legal page summarises and points to the binding clauses there, so the two pages always tell you the same story.
Data handling sits under Privacy. Where this page mentions identity checks, the deeper detail on retention and lawful basis is held in that document.
Tracking and consent rules are kept in the cookies page. We reference them here only where a clause depends on the consent you've already given.
Lobby promo cards link to their own clause set. If a promo and this page conflict, we treat the promo terms as the narrower, ruling text for that offer.
Wording about DANA, OVO, GoPay and QRIS references is held in payment terms. This page links across so the obligations match what you see at the cashier.
The escalation steps live in our dispute page. We mirror the contact paths here so you reach the right desk whichever page you opened first.
Account closure rules sit in their own page. We reference them so a clause about ending the agreement reads the same wherever you find it on berkah99.
The legal page is built for scanning. Below are the visible elements we've placed so a clause, a contact path or a revision date is never...
Each clause has its own anchor link. Copy the URL, send it to a friend or paste it into a support thread, and the page opens directly at the wording you were reading.
The footer holds the last review date and a short note on what changed. You can see at a glance whether the text shifted since your last visit.
Policy contact paths sit pinned near the top, so a question about a clause never sends you searching the site for the right inbox or chat route.
A short note marks where this policy applies. It names supported regions plainly so you know upfront whether the clauses on this page bind your account.
Above each dense clause sits a one-line summary in plain English. Read the summary first, then drop into the formal text only if you need the precise wording.
Where a clause depends on another policy page, we link straight to the matching section. No hunting through menus to reach the document we just referenced.