Beaver Compliance

Compliance enforced by the platform, not left on a policy page.

A toggle is not compliance. An enforced rule is.

Beaver Compliance turns operating requirements into controls that sit where things actually happen: checkout, account state, marketing eligibility, prize fulfilment and the audit trail.

Control settings

Player monthly spend limit

Locked floor. A Compliance Pack sets a minimum here. You can make it stricter, not looser. The console says which pack set it, and why.

Illustration of a locked control. Not the product interface.

The problem

Settings only compliance is a promise, not a control.

Plenty of platforms have a settings screen with the right words on it. The question is what happens at the moment a customer tries to spend past a limit, re register after excluding, or receive a win back email while flagged.

If the answer is "nothing, unless somebody notices", the rule is decoration.

A policy page cannot stop a transaction. Beaver can.

Checkout enforcement

Rule. Control. Enforce. Audit. Evidence.

Each control has a place in the flow where it acts. Spend limits act at checkout and top up. Exclusion and breaks act on the account. Care flags act on marketing. Missing launch requirements act on going live.

And each action leaves a record.

Controls leave evidence.

Audit record

    Illustration of where enforcement happens, with example values. Not the Beaver product interface.

    What the engine does

    The machinery.

    • Compliance Packs

      Requirements as a package of controls.

      Live

      A Compliance Pack sets the controls and minimum levels an operation runs under.

    • Locked floors

      Stricter, never looser.

      Live

      A pack can impose a minimum an operator cannot loosen, and the console explains which pack set it and why.

    • Readiness gate

      No launch with gaps.

      Live

      A missing launch requirement stops an operator going live.

    • Audit trail

      Who, why, before, after.

      Live

      Sensitive writes touching money, entries or marketing are recorded.

    • Care signals

      Signals for a human to review.

      Built

      Behavioural rules and an intervention queue, in the product and not yet proven with live operators.

    Switch only means switch only

    Controls that exist on screen but are not wired yet.

    These appear in the control registry. We do not sell them, and they are not part of any Beaver compliance claim until they work.

    Controls that exist on screen but are not wired yet.
    CapabilityStatusWhat that means
    Instant win portfolio share capNot availableWe do not claim automatic enforcement of the Code's instant win share rule.
    Third party age verification on risk triggersNot availableThe age gate and pre prize age check workflow are Live. Verification by a provider is not.
    Rotating skill question bankNot availableOne configured, server validated question is Live.
    Configurable audit retentionNot availableA retention setting that does nothing is not a retention policy.

    Live proven on the deployed platform. Built in the product with passing tests, not yet proven with live customers. Roadmap planned, not a working feature.

    If the rule is not wired, we do not colour the box green.

    The boundary

    Software, not legal advice.

    Beaver enforces the configuration an operator chooses and records what happened. It does not decide which rules apply to your business, interpret the law for you or make an advert truthful.

    • A "make compliant" button
    • A regulator approval
    • A substitute for trained compliance staff

    The software can enforce the configuration. It cannot replace judgement.

    Compliance walkthrough

    See the controls on the real product.

    We will show you what is enforced, where, and the current status of each control.