The page a reader opens when they want to know who runs the site
A player looking at Mpo365's About page is usually trying to answer one question before anything else: who is behind this site, and can that identity be checked somewhere independent of the site itself. The About page is the natural place to look, because it is the one page an operator publishes specifically to describe itself. What a reader finds there splits into two categories that behave very differently. Some statements can be taken to an outside register and confirmed or contradicted. Others are self-description: the operator's own account of its values, its history, its standards and its intentions. Both categories are worth reading, but only one of them is evidence.
The practical difference is what a reader can do with each statement. A corporate name can be searched in a company register. A claimed group relationship can be checked against the parent company's own disclosures. A contact route can be tested by sending a message and seeing whether a reply comes back. A statement that the operator values fairness, cares about its players or was founded by people who love gaming cannot be checked anywhere. It may be true, but the About page is the only place it exists, and a statement that exists in only one place settles nothing.
What an About page normally contains, and what each item is worth
Across operators, an About page tends to carry a recognisable set of items. The company or trading name under which the site operates is usually there, sometimes with a registration number. The page may name a parent group or a brand family. It often gives a founding story, a mission statement, a description of the product range, and a contact or support route. Some pages mention the jurisdiction in which the company is established, and some link to a separate licensing or regulatory page. Each of these items has a different status, and the table below separates them by what a reader can do with them.
| Item to confirm | Why it can change | Where it is stated |
|---|---|---|
| Corporate or trading name | Operators rebrand, merge or move a site between group companies; the name on the About page today may not be the name on the invoice tomorrow. | The About page itself, and the footer of the operator's site where the legal entity is usually repeated. |
| Parent group or brand family | Ownership changes without any visible change to the site; a group relationship stated today may be historical within months. | The About page, the group's own corporate site, and any public filings the group publishes. |
| Founding story and mission | This is narrative, not record; it is rewritten whenever the brand is repositioned and carries no independent confirmation. | Only on the operator's own pages, where it functions as marketing rather than evidence. |
| Contact or support route | Channels are added, removed or changed as support operations shift; an address or form that works today may not exist next quarter. | The About page, the Contact page, and the support section of the operator's site. |
| Jurisdiction or registration claim | Company registration can move between jurisdictions, and the claim on the About page may lag behind the actual register. | The About page, but the binding version is the public company register of the jurisdiction named. |
The table's third column is the point. For every item, the About page is a starting point, not a finish. A reader who wants the item to be true in any enforceable sense has to leave the operator's site and look at the register, the group's disclosures or the actual behaviour of the contact channel. The About page tells the reader what to look for; it does not provide the confirmation.
The difference between a verifiable statement and a self-description
A verifiable statement is one that exists in at least two independent places. If Mpo365's About page names a corporate entity, and a public company register shows an entity of that name with the same registration details, the statement has been checked. If the page says the site is part of a group, and the group's own published materials list the site among its brands, that is a second source. If the page gives a support email address, and a message to that address produces a reply, the channel is real. In each case the About page has done its job: it has pointed to something that can be confirmed elsewhere.
A self-description is a statement that exists only in the operator's own voice. "We put players first" is a self-description. "Our team has decades of combined experience" is a self-description. "We are committed to fair and responsible gaming" is a self-description. None of these is false merely because it is unverifiable, but none of them is evidence of anything. A reader who treats them as facts has converted the operator's marketing into a finding, and that conversion is the single most common error people make on an About page. The correct response to a self-description is not disbelief; it is to note that the statement carries no weight and to look for the verifiable item that would support it if it were true.
This distinction matters because an About page is written by the operator about itself. It is the one page on the site where the operator has the strongest incentive to present itself favourably and the weakest external constraint on what it says. A promotions page is constrained by the need to state terms that will be enforced. A privacy policy is constrained by data protection law. An About page is constrained by almost nothing except the operator's own judgement and, in some jurisdictions, general advertising standards. That is why the page is useful for identifying what to check, and useless as the check itself.
What the About page cannot tell a reader, and where that information lives instead
There are several things a reader might reasonably hope to learn from an About page that the page, by its nature, cannot provide. The most important is the operator's regulatory status. An About page may mention a licence or a regulator, but the page itself is not the licence. The licence is a record held by the regulator, and the regulator's public register is the only place where a reader can confirm that the licence exists, that it is current, and that it covers the site the reader is using. If Mpo365's About page names a regulator, the reader's next step is to open that regulator's register and search for the operator's name. If the page does not name a regulator, that absence is itself information: there is no register to check, and the reader is left with the operator's own word as the only assurance.
The same applies to any claim about security, fairness or testing. An About page may say that games are tested or that player funds are protected. The testing laboratory, the certificate number and the scope of the test are not on the About page; they are on the laboratory's own certificate, which the operator should make available, and which a reader can verify with the laboratory. A claim on the About page that is not backed by a named certificate is a claim with no checkable content. The reader should treat it exactly as they would treat a self-description: note it, and look for the document that would make it true.
Company ownership is another area where the About page can gesture but not confirm. A page may say "operated by" a named company, but the actual ownership structure may involve intermediate holding companies, trusts or nominee arrangements that no About page discloses. The public company register shows the registered entity and its directors; it does not necessarily show the beneficial owners. A reader who needs to know who ultimately controls the operator may have to go well beyond the About page, into corporate filings and, in some cases, regulatory disclosures that are not public at all. The About page is the first step on that path, not the last.
How to read the About page in practice
The practical method is to read the page twice, with two different questions. The first reading asks: what does this page give me that I can check? The reader extracts every name, number, jurisdiction, group relationship and contact route, and writes each one down. The second reading asks: what does this page claim that it does not give me the means to check? The reader notes every statement about values, standards, experience, fairness and commitment, and treats each one as a claim awaiting evidence rather than a fact.
Then the reader leaves the About page and does the checking. The corporate name goes into the company register of the jurisdiction named. The group relationship goes into the group's own site and any public filings. The contact route gets a test message. The regulatory claim, if any, goes into the regulator's public register. Anything that survives that process is now a fact the reader has confirmed. Anything that cannot be checked remains what it was on the About page: a statement by the operator about itself, carrying no independent weight.
This two-reading method protects the reader from the most common failure mode on an About page, which is not being lied to but being persuaded. An About page is written to make the operator look like a reasonable, established, trustworthy business. Many operators are exactly that. The page cannot show it. Only the outside sources can.
FAQ
Whether Mpo365's About page proves the site is licensed turns on which regulator issued any licence and what its public register currently shows.
No. An About page can mention a licence or a regulator, but the page itself is not the licence and cannot prove that one exists. The regulator's public register is the only place where a reader can confirm a licence, its current status and the sites it covers. If the About page names a regulator, the reader should search that regulator's register for Mpo365. If it does not name one, there is no register to check, and the reader has only the operator's own word.
What is the most useful thing to look for on an About page?
The most useful items are the ones that can be checked elsewhere: a corporate or trading name, a registration number, a named parent group, a jurisdiction, and a working contact route. Each of these can be taken to an independent source and confirmed or contradicted. Statements about values, experience or commitment are not checkable and should be read as self-description.
Can an About page tell me who owns the operator?
It can tell you who the operator says owns it, which is not the same thing. The actual ownership structure may involve intermediate companies or arrangements that no About page discloses. The public company register shows the registered entity and its directors, and a parent group's own disclosures may show the brand relationship, but beneficial ownership is often not visible from the About page alone.
Should I trust an About page that says the operator is committed to fair gaming?
A statement of commitment is a claim, not evidence. The evidence would be a named testing laboratory, a certificate number and a scope of testing that the reader can verify with the laboratory. If the About page makes the commitment without pointing to such a certificate, the claim has no checkable content and should be treated as self-description.
This page is an independent summary of what an operator About page covers, it is not published by Mpo365, and it states no corporate fact, licence, ownership detail or regulatory status for the operator; Mpo365's own About page and the public registers it points to are the only binding sources for those facts.
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.