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.

This applies across the models Beaver runs: prize draws, prize competitions and licensed society lotteries, where lottery support is Built and no lottery is live on Beaver yet. In every one of them the operator holds whatever licence or registration applies, and Beaver provides the platform underneath it.

The rules

Understand the model before you configure it.

The machinery

Controls that do something.

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.