Self exclusion
Excluded should mean excluded.
Not excluded until a new email address appears. Not excluded from checkout but still added to a campaign. Not excluded in one table but forgotten elsewhere.
The protection state needs to follow the customer through the platform.
Stop means stop.
The basic principle
The request is the start. Enforcement is the point.
Self exclusion is not useful because an operator has a form where somebody can request it. It is useful because that request changes what the system allows afterwards. A properly implemented state can affect participation, account access, marketing, future registration attempts and operator workflows.
Live Beaver's single operator self exclusion enforces a minimum period and survives re registration.
A new account should not erase an old protection decision.
- Entry eligibility
- Spending
- Marketing eligibility
- Operator review
Re registration
Try again. The protection should still matter.
This is the sequence we will demonstrate from the real product:
Account excludes
The customer requests self exclusion.
Exclusion is active
The minimum period starts.
New registration attempt
Somebody tries again with a new account.
Protected state recognised
Beaver matches it to the existing exclusion.
Participation unavailable
The exclusion holds.
Changing the account does not change the history.
-
Take a break
Different state. Different meaning.
Live
Take a break and self exclusion are kept distinct. They serve different purposes and may carry different durations and consequences. The DCMS Code also distinguishes a temporary suspension of at least six months from the shorter pause options it encourages. We do not blur them.
-
Marketing
Exclusion should reach the campaign engine.
Live
Marketing suppression on care status is Live, and closed accounts hear nothing except about a prize still owed.
For self exclusion specifically, we will show the targeting outcome from product evidence before we describe it as proven. We do not assume every suppression pathway is identical.
-
Account closure
Closure is not exclusion.
Live
Ordinary account closure has its own Live behaviour: no marketing, with communication still possible where the operator owes the person a prize.
-
Auditability
Sensitive state should not change invisibly.
The audit system records actor, reason, before and after for sensitive writes involving money, entries and marketing. We are confirming exactly which exclusion actions appear in that audit model before we list them. Demonstrate, not assume.
Cross operator register
What if the protection could travel further?
Built Beaver contains a cross operator exclusion register. It uses salted hashes and is visible across operators that opt in. The aim is to let a protection decision be recognised outside a single operator environment without sharing ordinary readable customer records through the register.
We do not call it national, universal, industry adopted, regulator backed or GAMSTOP.
The register exists in the product. The network still needs participants.
- Player exclusion
- Salted hash
- Shared register
- Participating operators
Privacy design
Hashed is a technical description. Anonymous is a much bigger claim.
Before we make detailed technical or privacy claims about the register, the design will receive a proper privacy review covering identifier choice, hash construction, salt handling, matching, retention, removal, legal basis and operator responsibilities.
Until then we will not call it anonymous.
What Beaver does not claim
Protection gets stronger when the claim stays accurate.
- cross operator exclusion is already an industry wide scheme
- the register replaces other external protection programmes
- salted hashes make the system legally anonymous
- the software eliminates attempts at circumvention
- self exclusion alone is a complete player protection programme
Questions
Asked and answered
Does Beaver support self exclusion?
Yes. Single operator self exclusion is Live and enforces a minimum period.
Can a customer just create another account?
Beaver self exclusion is designed to survive re registration.
Is take a break the same as self exclusion?
No. They are separate account protection states and are described separately.
Does Beaver have cross operator self exclusion?
A salted hash cross operator register is Built and intended for operators that opt into it. It is not an established industry wide scheme.
Is Beaver's cross operator register anonymous?
We do not make that claim. A salted hash design is not by itself enough to justify calling the system anonymous.
See what stop means
Follow the exclusion through the product.
From the customer request to the account state, re registration behaviour and downstream suppression.