Every judgement here has a name on it, and the name is checkable.
BetJury is a small independent publication. Its reviews and guides carry the byline of an editor who spent thirteen years launching and running sportsbooks and casinos before he wrote about them, and whose record you can check outside this site; the research, audit and corrections behind him are the house desk’s. We would still rather you checked the work than took a name for it — so every audit shows the date it was last checked, every deduction shows its reason and its size, and nobody here, including the person named on a page, can type a score over the engine’s output.
- BetJury EditorialResearch, audit and corrections
Everything published here is researched, audited and corrected by BetJury. A review carries the date it was last checked; a TrustAudit carries every deduction with its reason and its points, including the checks still open; and the TrustAudit Index is computed from recorded findings. Separate Experience marks are editorial judgments, while the JuryScore uses eligible player testimony. Where we get something wrong, write to corrections@betjury.com and we will change it and say that we did.
1 piece on the record
- Editor & lead reviewer
Former iGaming operator turned writer: thirteen years launching and running sportsbooks and casinos in Africa and South-East Asia (EDITEC, Dafabet Kenya, StarSports, RPM Gaming, LiveScore Group), writing about the industry since 2008 and full time since 2021. University of Dundee; based in the Philippines.
30 pieces on the record
What a byline commits us to
Four things, and they are checkable rather than aspirational.
A date on every judgement. A review carries when it was last checked, not merely when it was written, because an operator’s licence, payout speed and terms all change and a two-year-old verdict presented as current is a false statement with a byline on it.
Reasoning published beside the conclusion. Every deduction in a TrustAudit is listed with its points and its reason, including the checks we have not finished — which is why some scores are marked provisional and some operators carry no number at all. You are meant to be able to disagree with a specific line rather than with a mood.
No hand-set scores. There is no mechanism — not in the code, not in the admin panel, not for the owner of this site — for a person to type a number over the engine’s output. Nobody here can overrule a score, and a test in the build fails if a commercial field is ever named anywhere in the scoring code. What an editor can do is add the evidence the engine reads.
Corrections that say so. When we get something wrong we change it and record that we changed it, rather than editing quietly — the log is on the editorial policy page. Tell us at corrections@betjury.com.
How the scores themselves are computed is set out on the methodology page, and what our own coverage actually amounts to — including the figures that do not flatter us — is on the transparency page.