Compliance
A policy page cannot stop a transaction. Beaver can.
Compliance in this category is three different things that often get blurred together: the law, voluntary good practice, and what the software actually enforces.
We keep them separate. Every guide here is sourced and dated, and every product claim carries its status.
The rules
Understand the model before you configure it.
-
Law
UK prize draw compliance
Free draws, prize competitions, lotteries and the Gambling Commission's role.
-
Law
Free entry routes
Cost, convenience, prominence and equal treatment in the draw.
-
Law
Skill questions
Why a question is not a magic loophole.
-
Good practice
The DCMS Voluntary Code
What it asks for, and how Beaver controls map to it, with status.
The machinery
Controls that do something.
-
Compliance Engine
Packs, locked floors, enforcement, audit and evidence.
-
Player protection
Limits, breaks, exclusion, care signals and suppression.
-
Spend limits
A limit should stop the transaction.
-
Self exclusion
Excluded should mean excluded.
-
Evidence packs
Show what was active at the time.
Try it
Push a purchase past the limit.
Move the sliders, tick a protection state and try to buy. The purchase is blocked where the rule says it should be, and the attempt is recorded.
Audit record
Illustration of where enforcement happens, with example values. Not the Beaver product interface.
How we write about compliance
Precise, sourced and restrained.
- Law, voluntary codes, platform controls and operational choices are kept apart.
- Every guide shows its sources and when it was last reviewed.
- Every product claim carries its status.
Beaver builds software. It does not give legal advice, and operators remain responsible for how they run their promotions.
See the compliance engine
Read the requirement. Configure the rule. Keep the evidence.
