Ambrose Kettlewell, player protection reviewer
Player Protection Reviewer
Our reviewer

Ambrose Kettlewell

Ambrose Kettlewell spent a decade in the compliance and customer-protection team of an online operator, handling complaints that began when a promise on a page did not match what happened on screen. He now reads game pages the way a sceptical member of the public would.

Player protectionWording checksCompliance read
2reads of every page
6questions before sign-off
1named source behind each statistic
Checklist

Six Questions Before Sign-Off

Six questions are asked of every page before Ambrose signs it off.

01

Could this mislead?

Each claim is read by someone with no slots background, to see whether a quick reader would take away the wrong idea.

02

Is the limit stated?

Stake caps, win caps and version differences must appear wherever a figure would be incomplete without them.

03

Is the source named?

Every statistic traces to the game, the provider or a named data set, and the page says which one.

04

Is anything promised?

Words that imply a result, such as easy, sure or effortless, are removed or replaced with what the game actually does.

05

Is help visible?

The age notice, safer-gambling information and a route to help sit on the page itself, not only in a footer.

06

Is it dated?

The date on the page reflects the last real review, and material changes are noted for the reader.

Reviewer profile

Reading a Page as the Person Who Could Be Misled

In his previous job, Ambrose read hundreds of complaints that started with a sentence somebody had misunderstood: a bonus described as free, a limit left out, a return figure quoted without the version it belonged to. That experience shaped how he reviews.

He reads each page twice. The first read is as a curious player with no background in slots, looking for anything confusing or overstated. The second is as a compliance officer, looking for statements that need a source, a caveat or removal.

He does not rewrite the author's work. He returns a list of specific lines with the reason each one fails, and the page is not approved until every line has been resolved.

He also watches for what is missing: the age notice, the help-line details, the stake limits, and the plain reminder that the outcome of any spin is random.

If a sentence could mislead someone reading quickly, it needs another clause or it needs to go.

Review flow

Two Reads and a Query List

First read

the page is read cold, as a newcomer, with notes on anything confusing or overstated.

Second read

the page is read as a compliance officer, marking every statement that needs a source or a caveat.

Query list

lines that fail are returned to the author with a one-line reason for each.

Sign-off

when every query is closed, the page is approved and the review date is recorded.

Written by a columnist, read by a sceptic

The pages Ambrose reads are written by Elowen Trethewey, a former trade-press reporter who says what a game does and shows her working.

Meet Elowen