Neil Bracken
My work is narrow and mechanical. Somebody claims a site protects players, and I ask where the protection is configured. Three answers are possible: in a written regulatory standard, in an account setting the operator controls, or nowhere. The third answer is more common than the industry likes to admit, and the second is what most pages mean when they say the first.
What I cover here
Layer attribution. Which obligation sets actually exist in published form, what each one requires, and which layer a given control sits in. I read Ontario's Registrar's Standards as an example of an obligation with an addressee, and the Kahnawake pre-authorization conditions as an example of requirements imposed at entry rather than continuously. Both are real. Neither is a guarantee, and I say so in both directions.
What I do not cover
I am not a provincial licensing authority and do not present as one. I do not walk readers through verifying a licence against an issuer, I do not describe how to file or escalate a complaint, I do not explain Canadian gambling law, I do not argue return percentages, and I do not benchmark payout speed or tabulate payment rails. Those are other people's specialisms.
What I will not print
A helpline number I could not source. A self-exclusion mechanism I could not source. A testing laboratory's name attached to an operator I have no evidence about. A claim that a particular brand offers a particular tool when I never checked. Four things, and the reason is the same for all four: a confident wrong answer costs a reader more than an honest gap does, because it stops them looking.
How I work
I quote what an operator publishes, in the currency it publishes it in, with the date I captured it. Where the record is empty I report the emptiness, which is why one brand on our list carries no bonus figure and why our main page has a section headed with what we could not source. An absence is a finding. Treating it as one is the whole method.
Corrections, and especially sourced facts that close one of those four gaps, are welcome at [email protected].