Four documents, read 26 August 2026
What is different on a phone, according to the documents that govern the account
Four documents were opened for Stake.com: the terms, the verification clause at 4.8, the territorial clause and the register entry for permit OGL/2024/1451/0918. Not one of the four distinguishes a phone from a desktop, and the seven properties recorded for a hundred operators contain nothing about a device either.
The question assumes there are two things to compare. On the evidence read for this index there is one thing, rendered at two widths, and the interesting part is what the second rendering hides rather than what it changes.
What the four documents say about devices
Four documents were opened for this operator on 26 August 2026: the terms of service, the verification clause at 4.8, the territorial clause published at stake.com/licenses, and the register entry for permit OGL/2024/1451/0918, held by Medium Rare N.V. and showing the status active.
None of them mentions a phone, a tablet, an application or an operating system.
That is not an oversight in the reading. Contracts of this kind are drafted around an account rather than around a screen: they describe who may open one, what may be demanded of the holder, and when funds may be withheld. The device is not a party to any of it.
So the plain answer to what changes on a phone is that the obligations do not.
The vocabulary has no word for it
Something similar shows up in the wider file. Seven properties are recorded across the hundred operators in this library: a crypto-only cashier, a sportsbook, live tables, instant withdrawals, a loyalty programme, in-house games, and a published fairness scheme.
Not one of them is about a device.
Those seven were not chosen in advance; they are what a hundred operators actually assert about themselves on their own pages, and the absence of a mobile claim among them says that this is not a distinction the trade markets on. A mobile version is assumed rather than advertised, in the way a working search box is assumed.
Which leaves the question with no cell to sit in, and this article standing in place of one.
The one thing a small screen genuinely takes away
A page saved to a home screen normally opens without the browser's address bar. That is a rendering choice, it is entirely ordinary, and it removes the single most useful thing on the screen.
The address is what says which product is open. This matters more here than it would almost anywhere else, because one brand name in this field covers two products, run in different markets under different arrangements, and the terms that govern one are not the terms that govern the other. What separates them, field by field, is set out on the two products under one name.
On a desktop the domain is visible without being looked for. On a home-screen shortcut it is not visible at all, and a reader who has forgotten which of the two they installed has no way to tell from the interface.
That is the practical difference, and it is a difference in what can be checked rather than in what has been agreed.
What a home-screen icon actually is
Some sites offer to be added to a phone's home screen, and the result looks like an installed application: an icon among the others, opening full-screen with no browser furniture around it.
It is a bookmark with a picture on it. The address it opens is the address that was open when the shortcut was made, the session belongs to the same browser, and the terms governing what happens inside it are the terms of the site. Nothing is downloaded from a store, no publisher is named anywhere, and no second company enters the arrangement.
That matters in one direction only, and it is the direction this index cares about. Because no publisher is named, a home-screen shortcut produces no new fact about who a reader is dealing with — while a store listing would, which is the whole reason store listings are worth opening at all.
So the shortcut is convenient and evidentially empty. It adds an icon and subtracts the address bar, and the second of those is the part to be deliberate about.
Where the documents that decide access live
Two clauses do most of the work for any reader on any device: the territorial clause, which lists the countries an operator declines, and the verification clause, which says when documents can be demanded. For this operator the first names one country and the second is clause 4.8, which reserves the right to request documentation at any time and to restrict service, payment or withdrawal until identity is sufficiently determined. Neither carries a threshold.
Both live behind footer links, and footers are the part of a page that a narrow layout compresses hardest. The documents are the same; the number of taps to reach them is not.
For a reader who wants both without hunting: the clause with the country list is at the licences page, and the verification wording is inside the terms. What clause 4.8 reserves and what it leaves out is worked through on the verification clause.
What would make a mobile version a fact worth recording
Three things, and none of them was found.
A separate set of terms attached to the application, which would make the app a distinct legal object rather than a wrapper. A separate publisher on the store listing, which would put a second company name beside the one on the permit. A separate permit or a separate register entry, which would make the app a different operation entirely.
Zero store listings have been opened for the twelve operators compared on this index, so the second of the three is not merely absent — it has not been looked for. That is a gap in the reading and it is printed as one. What a listing would prove, and why the publisher line is the part worth having, is set out on the store listings.
Until one of the three turns up, the honest position is the narrow one. There is an account, governed by documents that mention no device, reachable through a browser of whatever width the reader happens to be holding.