The OnlyPlay press release announcing Liberty Rush sits on our desk this morning. The text describes a video slot. It names the studio. It uses the word "launch" as a verb. It implies, without saying so, that the game is fit to be deployed in regulated markets.

What it does not contain is a certificate. It does not contain a regulator. It does not contain a jurisdiction. It does not contain an RTP empirically validated against any paytable that the reader is invited to inspect. There is no UKGC operating licence number adjacent to the announcement, no MGA approval reference, no test-house report ID with a scope and an expiry. This is not unusual. This is the rule, not the exception. Across the entire game-launch coverage stream on the English-language iGaming wire, the press release IS the launch — and the certification, when it exists, lives in a separate document the reader is not invited to read.

We will concede the strongest point the studios have. A press release is a marketing event. Slot studios do not file 10-Ks the way Flutter and Entain do. To demand a 10-K-shaped disclosure from a slot launch is to misunderstand the genre. Fine. We grant that.

But every claim adjacent to a launch — that the game uses certified RNG, that the RTP sits at some published percentage, that the math is fair, that it has been audited — every one of those is a regulatory artifact. And in the genre as it is currently written, the artifacts travel unaccompanied. The claim arrives. The document does not. That is the pattern we want to describe across the next four sections.

The Pattern: A Game Launch Without a Jurisdiction

Every slot-launch press release we read names the studio and the title. Almost none name the jurisdiction in which the game has been certified for deployment.

A jurisdiction is not optional. The UK alone runs 268 licensed online operators, each required by the UKGC public register to deploy only games approved by an independent test house against the Remote Gambling and Software Technical Standards. The MGA in Malta runs the same discipline. The AGCO in Ontario operates a similar approval list; 49 licensed operators sit on the Ontario register, and every game they offer has passed an independent compliance lab. Germany's GGL operates a centralized whitelist and enforces a cross-operator 1,000 EUR monthly deposit cap that depends on every approved game being registered to a specific provider entity.

When a release announces a game without naming any of these jurisdictions, the obvious question is: where is this game intended to be played? In a Curaçao-licensed casino? In a B2B feed to grey-market sites? In a UKGC-licensed environment? These are not equivalent perimeters. The compliance obligations on the operator differ in each case, and the game itself is approved under a different scope in each. A press release telling us a game launched without telling us where it launched is not a release the regulator would recognize. It is a vibe.

This matters because the contrast with how listed operators write IS on the public record. When Flutter discloses its regulated-markets footprint in its filings, it does so by jurisdiction by jurisdiction; the company reported that 52% of global iGaming activity now sits inside regulated markets. The number lives in a filing tied to specific licenses. The slot launch press release lives in nowhere in particular.

The Pattern: The RTP Number That Travels Without Its Audit

Studios publish RTP percentages routinely. Almost none publish the scope of the empirical test that produced the number.

Look at the public-facing pages of providers who do show their work. NetEnt lists its slot portfolio with RTP ranges between 94.00% and 96.70%. Evolution publishes live dealer RTPs to two decimal places: 99.28% on blackjack, 97.30% on European roulette. These numbers are useful only because a reader can ask the right follow-up: across how many rounds was that figure measured, by whom, against which paytable build?

The answer for GLI-audited games is on the public record. GLI's audit scope for a typical RNG slot covers NIST 800-22 statistical randomness tests, game math verification against the paytable specification, and RTP empirical validation across 10 million simulated rounds. Ten million rounds is not a casual figure. It is the threshold at which a 96% RTP claim stabilizes inside a narrow enough confidence interval to bind the studio to it across deployed instances.

Now read a slot launch press release. The RTP is published. The audit house is not named. The round count is not named. The scope is not described. The reader is asked to take the percentage on trust. A percentage on trust is not a percentage. It is a target.

A press release that mentions fair play without linking to the test house that certified the math is asking the reader to trust the studio more than the regulator does.

The Pattern: The Certification That Was Implied But Not Linked

This pattern has the longest record. Every major test house — GLI, iTech Labs, BMM, eCOGRA — publishes certificates by report ID. Each report has a scope, an expiry, a tested build hash. A studio that has been certified can cite the report. A studio that has not can use the word.

The two are not the same, and the UKGC enforcement record makes the difference visible at the operator layer. Flutter's UK licensee Sky Betting and Gaming was fined £1.17m in March 2023 for social responsibility and AML control failures — not for game integrity. Game integrity failures land differently. They land on the test houses and the studios behind them. iTech Labs publishes its audit cadence: quarterly per deployed game, annual re-certification for the RNG seed, and an incident re-audit within 48 hours if a player dispute is raised. That cadence exists because operators have to demonstrate it to keep their license; the studio either complies or its games come off the approved list.

When a release says "the game has been certified for fair play" without naming the certificate, what it means is that a certification process may have happened, in some jurisdiction, against some scope, expiring on some date. The reader is handed the conclusion and asked not to inspect the document. In any other regulated-financial-services context, this gap between claim and document would be the story.

Every game-launch piece on the English-language iGaming wire closes with a responsible gambling line. Almost none name a mechanism that binds the operator that will deploy the game.

There are real mechanisms. GAMSTOP covers every UKGC-licensed online operator automatically — a single registration blocks deposits across all UK-licensed brands for six months, one year, or five years at the user's choice. The registered user base sits at roughly 420,000 and has grown 35% year on year. Germany's OASIS register binds every licensed operator there. Portugal's RSA does the same for SRIJ-licensed sites. These are not slogans. They are enforcement systems with API integrations that operators must implement to maintain a license.

A press release that closes with "play responsibly" without naming GAMSTOP, OASIS, RSA, AGCO's voluntary self-exclusion register, or the jurisdictional equivalent is not invoking a mechanism. It is invoking a fig leaf. The reader knows a fig leaf when they see one. So does the regulator that runs the actual register.

So What Do You Actually Do

If you are reading a game-launch press release and you want to know what it actually means, the discipline is simple. Look for three artifacts. If they are not in the release, they should be one click away in a public registry — and if they are in neither place, the launch is a marketing event with no regulatory weight you can audit from outside.

The first artifact is the test house report ID. GLI, iTech Labs, BMM, eCOGRA all publish their certificate registries. A studio that has been certified can give you a report number with a scope, a date, and an expiry. A studio that has not will give you an adjective. The second artifact is the jurisdictional approval. UKGC, MGA, AGCO, NJDGE, GGL — each maintains a register of approved games and approved providers, and if the studio claims its title is live in a tier-1 market, the title appears there. The release does not need to link to the register; the register does the work the moment you search it. The third artifact is the responsible-gambling mechanism. Not the line — the mechanism. If the launch names a jurisdiction, the operator that deploys the game in that jurisdiction is bound by GAMSTOP or OASIS or RSA or the local equivalent, and a launch communication that respects its reader names which one.

This piece does not cover the technical details of OnlyPlay's corporate structure or its licensing footprint — none of the underlying documents on that front were in our dataset, and we will not speculate on a B2B provider's jurisdictional reach without filing-grade source. It does not cover the specific volatility math or hit-frequency profile of Liberty Rush — that lives in a paytable specification we have not seen. And it does not cover the question of whether OnlyPlay's distribution partners include any UKGC-licensed operators that would put the game inside the British perimeter — that would require pulling the public register entry by entry, which is a separate piece of work with a separate documentary trail. Each of those is a separate argument. We will write them when the documents are in front of us, and not before.