The first question an About page answers is not what it says, but what it can prove
A reader lands on Yayz's About page with a simple question: who runs this site? The answer they get is a mixture of two very different things. Some of it is a statement of fact that can be checked against an outside register — a corporate name, a registration number, a group structure, a contact route. The rest is self-description: the operator's own account of its values, its history, its place in the market. An About page is useful exactly to the extent that a reader can tell those two apart. The page itself rarely draws the line, so the reader has to.
The practical consequence is that an About page is a starting point, not an endpoint. It tells a reader what the operator says about itself. Whether any of it is true is a question the page can only partly answer, and the parts it cannot answer are often the parts that matter most when money is at stake.
What an About page normally contains, and what each part is for
Across operators, an About page tends to carry a recognisable set of items. Each one has a different relationship to verification, and a reader who knows which is which can read the page in minutes instead of getting lost in marketing language.
| Item to confirm | Why it can change | Where it is stated |
|---|---|---|
| Corporate name and legal form | Operators rebrand, restructure, or move a site between corporate entities; the trading name on the homepage is not necessarily the name on the registration. | The About page, usually in a footer block or a section headed with a phrase like "operated by". |
| Registration number and jurisdiction | A company can change its registered office or be re-registered; the number only has meaning inside the register that issued it. | Sometimes printed on the About page; always checkable on the relevant national company register. |
| Group ownership and parent company | Ownership changes through acquisition or internal reorganisation, and a group may operate several sites under different names. | The About page may name a group; the corporate register shows the current shareholder structure. |
| Licence or authorisation claim | Licences lapse, are suspended, or apply only to a specific entity and territory; a claim without a number is not a claim a reader can check. | The About page may mention a regulator; the regulator's own public register is the only place the status is current. |
| Contact route for formal correspondence | Support emails and chat channels change; a registered office or formal address is more stable but still moves. | The About page or a separate contact page; the company register holds the registered address. |
| Founding date, team size, game counts | These are marketing figures and change as the business grows; they carry no regulatory weight. | The About page states them as self-description; no outside register confirms them. |
The table's third column is the point. For the first five rows, there is an outside place where the claim can be tested. For the last row, there is not, and that is itself information: a reader should treat founding dates and game counts as colour, not as commitments.
The split between verifiable statement and self-description
Every About page is built from two materials. The first is the kind of statement that can be false in a checkable way: a name, a number, a jurisdiction, a parent. If the page says the operator is registered under a particular name in a particular place, that claim is either true or false on a public register. The reader does not need to trust the page; they need to look up the register.
The second material is the kind of statement that cannot be checked at all, because it is not a claim about a fact. "We put players first", "we have been innovating since our founding", "our team is passionate about fair play" — these are expressions of positioning. They may be sincerely meant, but they are not evidence of anything. A reader who treats them as evidence has mistaken the genre of the page.
The practical rule is simple: carry every factual-looking item on Yayz's About page to the register that governs it, and leave every value statement where it is. The page's job is to tell the reader which registers to consult. If it does not name a register, a jurisdiction, or a corporate entity, the reader has learned something important: there is nothing to check.
What the absence of an item means
An About page is also read by what it does not say. Absence is not automatically suspicious — some operators put corporate details in a footer or a separate legal page rather than on the About page itself — but absence does change what a reader can do.
If the page does not name a corporate entity, the reader cannot look up the operator on a company register, and therefore cannot confirm that the site is run by a company at all. If the page does not name a regulator or a licence number, the reader cannot check the operator's status on a regulator's public register. If the page does not give a formal contact route, the reader has no channel for legal correspondence. Each of those gaps is an answer to the question the reader came with: it tells them what cannot be verified from the page, and what they would need to obtain elsewhere before relying on the operator for anything that matters.
This is not a judgement on Yayz specifically. It is how About pages work in general. The page is a statement by the operator about itself, and its omissions are as informative as its claims. A reader who notices what is missing has read the page correctly.
Which claims a reader should carry to an independent register
When an About page does contain verifiable items, the reader's next move is to take them somewhere independent. The page itself is not independent; it is published by the operator, and an operator's own statement about its registration or licensing is not the same as the register's statement.
The registers that matter are public and external. A national company register confirms that a named entity exists, where it is registered, and who its current officers are. A gambling regulator's public register confirms whether an operator holds a current authorisation, under what conditions, and for which territory. A data protection authority's register may confirm a controller's registration where that is required. None of these are reachable from the About page itself, and none of them take the operator's word for anything.
The reader's task is to match the items. The corporate name on the About page should appear on the company register. The licence claim should appear on the regulator's register, with the same entity named. If the names do not match, or the register has no record, the About page's claim has failed its only test.
Why the About page is not a substitute for the legal pages
One common misreading is to treat the About page as if it were a legal document. It is not. The About page is a profile; the terms and conditions, privacy policy, and responsible gambling policy are the documents that create obligations and define the relationship. A statement on the About page does not bind the operator the way a term does, and a reader who relies on the About page for anything contractual has mistaken one genre for another.
The division of labour is consistent across operators. The About page says who the operator is, in its own words. The terms say what the operator will and will not do. The privacy policy says what happens to the reader's data. The responsible gambling policy says what controls exist. A reader who wants to know whether a withdrawal will be paid, or how a dispute will be handled, will not find the answer on the About page; they will find it in the terms, and the About page's job is only to tell them which operator those terms belong to.
Reading the About page as a checklist
A reader can work through an About page in a fixed order, and the order matters because it separates what can be checked from what cannot.
First, find the corporate name and legal form. Second, find the registration number and jurisdiction. Third, find any licence or authorisation claim, and note whether a number or regulator is named. Fourth, find the group or parent company, if one is named. Fifth, find the formal contact route. For each of the first four, note the outside register that would confirm or refute the claim. For the fifth, note whether the route is formal enough to serve for legal correspondence or only a support channel.
Only after those five are located should a reader spend any time on the rest of the page. The history, the values, the team descriptions, the game counts — these are the operator's own account, and they carry no independent weight. A reader who does the checklist first will not mistake the marketing for the facts.
What changes over time, and why today's About page may not match tomorrow's
An About page is a snapshot, and the facts behind it move. A corporate entity can be renamed, moved to another jurisdiction, or replaced by a different entity within the same group. A licence can be renewed, amended, suspended, or surrendered. A parent company can sell the operator to another group. A contact route can change when an operator moves its support operation.
This is why a reader should not treat an About page as a permanent record. The page describes the operator at the time it was last updated, and the operator's own registers are the only places where the current position is visible. A reader who checked the About page a year ago and returns to it today should check again: the page may have changed, and the registers certainly may have.
The same applies to the reader's own reliance. A decision made on the strength of an About page is a decision made on the operator's self-description. A decision made on the strength of a register is a decision made on an independent record. The two are not equivalent, and the difference is the entire reason for reading the page carefully in the first place.
FAQ
What is the point of an About page if it is not legally binding?
The About page tells a reader which corporate entity runs the site, where it claims to be registered, and which regulator it claims to answer to. Those claims are the starting points for verification. The page itself does not bind the operator, but it points to the documents and registers that do.
How can a reader check what an About page says?
For corporate claims, the reader checks the relevant national company register. For licence claims, the reader checks the regulator's public register. For data protection claims, the reader checks the data protection authority's register. The About page is only the source of the claim, never the source of the confirmation.
What if the About page does not name a company or a licence?
Then there is nothing to check, and that absence is itself the answer. A reader cannot confirm that a corporate entity exists, or that any regulator authorises the operator, from a page that names neither. The reader would need to obtain that information from the operator through another channel, or treat its absence as a reason for caution.
Does an About page tell a reader whether the operator is safe or fair?
No. Safety and fairness are not properties an About page can establish. They are properties a reader infers from a licence on a regulator's register, from the terms that govern the account, and from the operator's actual conduct. The About page only tells the reader what the operator says about itself.
This page is an independent summary of what an operator About page covers, not a document published by Yayz, and it states no figure or status for that operator; the operator's own page is the only binding source for what it says about itself.
Play responsibly
Gambling should be treated as paid entertainment, never as a way to earn income or recover losses. 1-800-MY-RESET (1-800-697-3738)
18+ or 21+ depending on where you are; follow the minimum age that applies to you.
This article is general information about how these mechanics work. It is not legal advice and not a recommendation to gamble or to use any particular operator. Availability and legality differ by jurisdiction — check the rules that apply where you are.