Which copies were opened, on what dates, and what stayed shut
The method, with its holes marked
Two archived captures of one operator’s own text were read in full for this site, 902,657 characters and 444,165 characters, fifteen months apart. Everything quoted here comes out of those two files, out of the terms of eleven other operators, or out of a public licence register.
| Casino | Operator | Licence | Countries barred | Withdrawal limit | Visit |
|---|---|---|---|---|---|
| Vavepaid placement | TechOptions Group B.V. | Curaçao no number | list not read | from 50,000 USDT in instalments cl. 8.8 | Visit |
| Gamdom | not published | not published | 37 | not published | |
| Rocketpot | Danneskjold Ventures B.V. | Curacao | 34 | not published | |
| Bitcasino.io | Moon Technologies B.V. | Curaçao Gaming Authority | 1 | not published | |
| Wild.io | Stack Gaming Ltd. | Curaçao Gaming Authority | 45 | not published | |
| Wild Fortune | Metlait SRL | Anjouan Gaming Board | 47 | not published | |
| Instant Casino | Igloo Ventures SRL | Curaçao Gaming Authority | 48 | not published | |
| CoinCasino | Igloo Ventures SRL | Anjouan Gaming Board | 36 | not published | |
| Bets.io | Techno Wave Systems S.R.L. | Curaçao Gaming Authority | 42 | not published | |
| Playbet.io | Bitx Operations N.V. | Curaçao Gaming Authority | 30 | not published | |
| CryptoLeo | Uno Digital Media B.V. | Curaçao Gaming Authority | 74 | not published | |
| BetPlays | not published | not published | 15 | not published |
What was opened, and on which day
Three sources were read for the operator this site is named after, all opened on 2 September 2026.
The first is an archived response of the operator’s own translation endpoint, captured by the archive on 9 August 2026: 902,657 characters, 16,077 separate text strings. It carries the Terms and Conditions in force, seventeen sections with decimal sub-clauses, together with the Refund Policy, the Privacy Policy and the help-centre answers. Every field on this site marked as current comes out of that file.
The second is an archived response of the same endpoint captured on 24 April 2025: 444,165 characters, 8,919 strings, holding the earlier Terms of Service in eight numbered sections. Its only job here is comparison. Nothing from it is presented as the arrangement a reader would sign up to today.
The third is the archive’s index of addresses that once existed under the operator’s domain, 20,000 rows of it, used for two narrow purposes: to establish that the legal pages sit under a help directory rather than at the addresses a reader would guess, and to list the game-supplier names appearing inside archived lobby addresses.
The eleven comparison operators were read separately, on 26 August 2026, from their own terms, live where those opened and from archived copies otherwise. The permit numbers beside them come from public registers.
Why the two dates travel separately
Every archived field on this site carries a snapshot date and a reading date, and they are kept apart on purpose.
The snapshot date says when the archive captured the operator’s document. The reading date says when we opened the archive’s copy of it. Collapsing the two would let a September reading of an August capture sound like a September reading of the operator, and the difference between those is the amount of change a contract can absorb in a month. So the rule runs one way: a claim built on archived text is dated to the capture.
What the closed doors mean, and what they leave untouched
Four legal addresses under the operator’s domain were requested from our capture machine, in the Netherlands, on 2 September 2026. Each returned the same 391-character refusal page, which named the Netherlands. Four further addresses, guessed from conventions other operators use, returned 404.
That refusal page proves one thing, stated as narrowly as it deserves: a request from an address in the Netherlands on 2 September 2026 received that response. The wording of it appears inside the operator’s own translation bundle as two strings, so the page is the operator’s own component rendering rather than an intermediary’s error screen. Even so, its reach ends at that sentence.
Evidence about a request is all it is. The screen falls short of being the operator’s document, and it falls short of establishing that any country is refused. Anything this site says about the Netherlands and this operator rests on clause 3.4 of the contract, where the country appears in the operator’s own list, and rests on nothing else. A refusal screen turned into a statement about a market is a mistake this network has made before, and preventing it is why these paragraphs exist.
A register entry and a clause answer different questions
The licence column carries a source label because the label decides what a reader may conclude.
Eight of the comparison rows carry a permit number that resolves in an issuing register, with a holder company and a status attached. One of those statuses reads Revoked, and it is printed as read. That is a regulator speaking about a permit.
An operator’s terms are a different instrument, binding the operator to conduct and naming the law a dispute runs under, and they can be edited overnight. Where a number appears in both places, the reader gets two independent handles on one company; where it appears in one, the table says which of the two is missing.
What an empty cell records
An empty cell means the document answering that question stayed unread. That makes it a fact about our reading rather than a fact about the operator.
An empty cell is never a zero, never a permission and never a finding. The subject of this site has three of them, and the reason differs in each case. Anything numeric about a permit sits behind template placeholders in both copies we hold. The amount at which verification is demanded appears nowhere in either file, though clause 2.1 says checks may run especially where financial thresholds are met. And the payout ceiling has a stranger shape again: the operator states there is no fixed monthly maximum while reserving a right to pay large sums in instalments, with no threshold attached, so the cell holds an absent figure rather than a figure we failed to find.
Filling any of those from a comparison page would take a minute and would substitute a number of unknown parentage for an honest gap.
Five places where this reading is weak
The current edition may already have moved. What we hold is a capture dated 9 August 2026, opened three and a half weeks later. The whole argument of this site is that this contract changes underneath its readers, and that argument applies to our own copy with equal force. A reader who opens the operator’s terms today may find a longer list than the 37 names quoted here.
Four clause numbers are our pairing rather than the document’s layout. In the export we read, some headings and their paragraphs were stored apart. Section 16 for governing law, 3.2 for responsible gambling, 6 for promotions and 17 for complaints are attached to their text by content, on the reasoning that each is the only heading and the only paragraph of its kind in the bundle. Wherever that applies, this site says so on the page.
The Refund Policy has headings instead of numbers. Two of its own paragraphs refer to a section 1.1 of itself, so a numbering exists in the rendered page that the string export left behind. Quotations from it therefore travel with a document name and a date rather than a clause, which is a weaker handle than everything else here.
Some figures come from help-centre answers. The self-exclusion durations offered in account settings, and two maximum-bet figures, sit in answers rather than in numbered clauses, and one of them hedges with the word typically. Each is labelled as a help-centre reading, because an answer can be rewritten without amending a contract.
The register was opened and left unqueried. The Curaçao portal at cert.cga.cw rendered from our capture machine on 2 September 2026. Its online gaming licence register runs on a search control that the tooling available in that session could not drive, so zero queries by domain were executed. Until one is, the permit question stays where the contract left it: three jurisdictions printed in one download and no way to tell which is live.
One further artefact deserves recording so that a later reader avoids mistaking it for a finding. Opening an archived copy of the operator’s help pages in a real browser lets the operator’s own script run during replay; the script decides the visitor is somewhere it refuses, and moves the page to an archived copy of a geo-block screen. The country that screen names belongs to the replay rather than to our location or to the operator’s rules.
The four movements this comparison actually supports are set out on the home page, and the territory clause in full sits on the restricted countries page.