Responsible play
What the game will not do, however it is configured
Five things that are unconditional in code, the market rules layered on top of them, and the mechanisms our research archive talked us out of.
- Unconditional in code
- 5
- Settings that turn them off
- 0
- Mechanisms we took out or never built
- 5
- Targets attached to the near-miss rate
- 0
each one with the function or the clause that enforces it
none for an operator, a licence or us
with the finding that decided each one
it is measured and published, nothing more
Provisional: this document is not approved yet
Everything below is a draft. It becomes the studio's approved position only when every administrator has signed this exact version in the client area. Until then, read it as an accurate description of what we do and intend, not as a document anybody has signed off.
Written in-house, not reviewed by a lawyer, and no Maltese entity exists yet to be a party to it. What approval means here
We do not have players. The operator has the players, the duty of care and the licence, and we are one supplier among many. What we control is the game: what it shows, what it celebrates, how fast it goes, and what it will not do however an operator configures it. That is what this page covers.
Everything below is enforced. Where a rule comes from a market, it lives in that market's pack and is applied last, after every operator override. Where it is ours, it is unconditional and there is no setting for it.
Unconditional, in every market
Each one names the function or clause that enforces it, so you can check it. A commitment cannot be checked; a function can.
A loss is never celebrated as a win
A round that pays less than it cost does not get the win presentation, and in a tumbling game where a round pays in steps, every paying event carries the running total and whether the player is actually ahead. There is one definition for every game and no per-game override.
mayCelebrate() · unconditional, in the shared contract
Near misses cannot be manufactured
The reels draw one stop per column and read the strip. The substitution that produces a near miss on purpose, by showing a symbol next to the payline more often than the strip would, has no code path here. The rate is measured and reported with no threshold attached, because a number with a target is a lever.
spinGrid() · UKGC RTS 7C
The player can see what they are down
Net position since the session opened and elapsed session time are always visible, and both are kept in a ledger with no reset button. Net position is shown untinted in both directions, because green on a gain beside grey on a loss is the same problem at session scale.
UKGC RTS 2E and 13C
The feature does not run faster than the game
Free spins used to run 28% quicker than the base game. We set that deliberately, with an argument about dead time that was real and wrong. A feature is the highest-arousal phase of a round, so compressing it puts the highest event frequency exactly where response inhibition is measurably worst. A client that shortens its own animation is also doing what turbo does, unasked, in markets that removed turbo.
Our own timing rules, with the research behind them
A demo must represent the paid game
Our demos replay recorded rounds, so a pool's realised return is exactly the demo's return. That is not enough on its own. Every one of our cabinets used to start the rotation at the same index, and on one game the single largest win sat near the end, so a player watching fifty spins saw about two thirds of the advertised return while a chip beside the balance claimed the full figure. The rotation now starts at a random offset, so the advertised figure is the expected return at every session length, not only over a full cycle.
GLI-19 §4.9.1(a)
How long a market makes a player wait
The floor under a paid round is the most consequential number a jurisdiction gives us. It changes how a feature feels, though not what it pays. Every pack here sets one, and one of them sets it at double everybody else's.
- Germany DE20 spins · 100s
- Malta MT20 spins · 50s
- Great Britain GB20 spins · 50s
- Netherlands NL20 spins · 50s
- Sweden SE20 spins · 50s
- Denmark DK20 spins · 50s
A twenty-spin feature in Germany takes 100 seconds of floor alone. That is intended, and we do not design around it. The floor is enforced on the control and on the server, so a client cannot spin faster by asking twice, and turbo cannot buy a quicker game. A client that shortens its own animation to get round it would be doing the same prohibited thing under another name.
And what a market adds on top
These live in data: a pack per market, applied last, with clamps so an operator cannot configure themselves out of one.
| Control | What it does |
|---|---|
| Minimum interval between paid rounds | A floor on how often a round can be staked. Clamped upward only: an operator can make it slower and never faster, and turbo cannot buy a faster game. |
| Autoplay | Denied outright in several markets. Where it is denied the control is removed rather than greyed out. |
| Feature buy | Denied where a market's guidance reaches it. The mode is still described in the rules of play, because a paytable with a silent hole in it describes a game nobody certified. |
| One player action per free spin | A run of spins that plays itself through is what the Dutch guidance describes. Where a market requires it, each spin needs its own press. The outcomes are still resolved in one call from one seed; only the reveal changes. |
| Maximum stake | Clamped downward only. |
| Reality check | Where a market sets one, it is enforced server-side rather than offered as a setting. |
Where the rules come from
The research behind these rules is kept in a database: published work on schedules of reinforcement, the near miss, the loss disguised as a win, the anticipatory interval, sound, mental accounting, and what the interventions measurably achieve. Each source carries a weight and an evidence class, and each derived rule a confidence. One of the rules contradicts the received wisdom and is stored as contested, next to the replication that found the opposite.
Most of what it records is a mechanism we decided not to build, with the citation for why. The archive is read before something is designed, not after it ships.
The palette
Colour is a contract
Six colour pairs in our shipped palette were once below their accessibility floor, and none of them was obvious by eye. The worst: in the mode that costs the most per spin, the spin key measured 1.12:1 against its own frame, which made the primary control the least distinguishable object on screen. We got there by accident, which is how the deceptive-design patterns found on a third of licensed sites tend to arrive.
Every theme of every skin, checked against a contrast floor on every build.
Where to turn
Help, wherever you are
BeGambleAware in the UK and Loket Kansspel in the Netherlands. An operator’s own tools (deposit limits, time-outs, self-exclusion) sit with the operator, because that is where the account is.
Shown in the client and in this site's footer.
What the archive talked us out of
Most of what the research archive records is a mechanism somebody declined, with the citation for why. These are the ones we took out or never built.
A near miss you can tuneShowing a symbol beside the payline more often than the strip would is the one presentational lever with a measured effect on how long somebody keeps playing. There is no code path for it here: the reels draw one stop per column and read the strip, so the substitution has nowhere to happen.UKGC RTS 7C · prevented by constructionA faster featureFree spins ran 28% quicker than the base game, set deliberately, with a real argument about dead time. A feature is the highest-arousal phase of a round, so compressing it puts the highest event frequency exactly where response inhibition is measurably worst. Removed.our own timing rules, rewritten 2026A Skip buttonIt was a second turbo on a different key, offered in all three markets that deny turbo spin. A control that shortens the game is turbo whatever it is labelled.UKGC RTS 14E, and the markets that removed itA tinted net positionGreen on a gain beside grey on a loss is a loss disguised as a win at session scale. The figure is untinted in both directions and it has no reset button, so it cannot be turned into a scoreboard.UKGC RTS 2ERed, because red makes people bet biggerThe received wisdom that red raises risk-taking is in the archive as CONTESTED, next to the replication that found the opposite, so we do not design with it. A finding we would like to be true is the one to store with its contradiction attached.stored as contested, with the replication
What we do not do
We have no relationship with the player, and that is a limit
We cannot see a player’s deposits, their losses across other games, their self-exclusion status or their account history, and we do not want to. The only identifier that reaches us is an opaque reference the operator chooses, and adding a name, an email or a date of birth to our schema would be a legal decision, not an engineering one. So the interventions that work at the account level are the operator’s to make. Ours stop at the game.
For the person who has to sign this off
Ask for the enforcement, not the statement
Every line here is backed by a function, a clause or a market pack, and we will show you the one behind whichever claim matters to your licence. If something here is weaker than your jurisdiction expects, tell us before an integration, not after.
hello@getawaygaming.com · Help with gambling: BeGambleAware.org in the UK, Loket Kansspel in the Netherlands. An operator’s own tools sit with the operator, because that is where the account is.
Provisional until every administrator has approved this version. Written in-house, not reviewed by a lawyer, and no Maltese entity exists yet to be a party to it.