Brand name versus legal entity
A familiar brand can appear in documents that refer to different companies.
THE KNOWLEDGE HUB
A little context.
A lot more clarity.
Not sure what a licence proves, how to read a review or where a complaint starts? Find a practical explanation, an example and the questions worth asking.
104 reference guides13 topic collections4 operator files
Browse the 13 topic collections
Operator identity8 guides Licensing research8 guides Evidence and sources8 guides Reading terms8 guides Withdrawal case records8 guides Complaints and resolution8 guides Review literacy8 guides Account security8 guides Crypto risk literacy8 guides Privacy and records8 guides Jurisdiction and scope8 guides Editorial standards8 guides Support and next steps8 guides
104 guidesORIGINAL EDITORIAL GUIDANCE
Why the exact domain matters
A research claim should identify the complete hostname it concerns.
Building an operator identity sheet
An identity sheet keeps names from drifting between sources.
Reading a website footer critically
A footer is a convenient place to find identity claims, but it remains a statement made by the website.
Ownership changes and historical records
Historical sources should remain attached to the entity and date they originally describe.
Help centres as identity clues
A help centre can reveal how a service describes its brand, policies and support structure.
Similar names and mistaken matches
Name searches often produce businesses that merely sound alike.
Recording rebrands without losing context
A rebrand changes how a service presents itself; it does not explain every change in the underlying business.
What a licence number can establish
A licence number is an identifier to investigate.
Company registration is not a licence check
A corporate register and a gambling register answer different research questions.
Reading the scope of a register entry
Do not stop at a register entry's headline status.
A historical licence screenshot
A saved register screenshot is evidence of what was captured at a particular moment.
What to do with a broken licence link
A broken link is an incomplete research path.
Separating operator claims from register findings
A useful licence section has two clearly labelled parts: what the operator says and what the independent register shows.
When a register search returns no result
A negative search can reflect the search terms, the register's coverage or the absence of an entry.
Writing a country-specific research note
A country note should state its research question before discussing any evidence.
Primary sources and secondary summaries
A primary document is closest to the event or decision being described; a summary interprets it.
Source date versus check date
A document's publication date and the day you accessed it answer different questions.
Building a useful evidence timeline
A timeline should separate events from the dates on which they were reported.
Reading a regulatory notice
Begin with who issued the notice, who it names and what action it describes.
Claims, observations and conclusions
Label what someone says, what you directly observed and what you infer.
Handling conflicting sources
Start by checking whether the sources actually discuss the same entity, domain and time period.
Using archived webpages carefully
Archived pages can help reconstruct what a website displayed in the past.
How much evidence supports a conclusion
Match the strength of the wording to the evidence actually available.
Keeping a dated copy of terms
Terms can be difficult to discuss when each person is looking at a different version.
Finding the complaint procedure in terms
A complaint procedure is easier to use when its steps are extracted into a short reference sheet.
Reading withdrawal restrictions as evidence
When documenting a withdrawal dispute, identify the exact restriction being cited instead of summarising it as unfair or standard.
Policy changes and notice records
When a policy changes, compare the earlier and later versions and document how the change was communicated.
Ambiguous wording in a policy
If a clause can reasonably be read in more than one way, write down the specific ambiguity and ask for a written explanation.
Separating marketing copy from terms
Promotional headlines and detailed terms may describe an offer differently.
Creating a policy comparison table
Compare policies using fixed questions instead of selecting whichever details make one website look better.
When support cites an unnamed rule
A reference to our policy is hard to investigate without a clause or document.
Documenting an existing withdrawal delay
Start a dated record of the request, the amount as displayed and each status message.
Requested, approved and completed statuses
Status labels can refer to different stages within a service.
Keeping transaction references private
Transaction identifiers can help an authorised reviewer investigate an existing dispute, but public posts should reveal only what is necessary.
Comparing an amount with its record
A discrepancy report should state exactly which two figures differ and where each came from.
Repeated requests for the same document
If the same information appears to be requested repeatedly, create a log of what was requested, when it was sent and what acknowledgement arrived.
Writing a clear payment-status question
A focused status request is easier to answer than a long message mixing several disputes.
Closing a resolved payment case
When an issue appears resolved, record what changed and what remains uncertain.
Avoiding escalation by assumption
Long silences and unclear status messages can be upsetting, but a case record is stronger when it separates uncertainty from established facts.
Preparing a one-page complaint summary
A concise summary should make the central issue understandable before the reader opens attachments.
Writing a factual complaint chronology
Use a simple table with date, event, evidence reference and open question.
Separating support from a formal complaint
Some services describe distinct support and complaints processes.
Organising complaint attachments
Give every attachment a short, consistent name and include an index explaining why it matters.
Asking for a written explanation
A decision is easier to evaluate when the reason and supporting rule are identified.
Checking an escalation body's remit
Before submitting a case to an outside body, read what it says it can consider.
Tracking complaint responses
Maintain a compact response log that records promised next steps as well as completed ones.
Updating a public complaint responsibly
If you publish a complaint account, distinguish your experience from wider claims about the business.
What makes a review checkable
A checkable review explains what was examined, when it was examined and what evidence supports its conclusions.
Affiliate disclosures in reviews
A commercial relationship can affect how a review is presented and what it emphasises.
Why a score needs a method
A numerical score is only interpretable when its criteria and calculation are explained.
Spotting unsupported first-hand claims
Words such as tested, verified and experienced imply work that should be described.
Reading negative reviews in context
A negative account can identify a question worth investigating, but it does not automatically establish a pattern.
Review dates and recycled freshness
An updated date is useful only when it corresponds to meaningful work.
Recognising copied review clusters
Similar wording across many websites may reflect a shared source rather than independent agreement.
Balanced does not mean equal certainty
A review can discuss strengths, limitations and unresolved questions without giving every claim equal evidential weight.
Checking an unexpected support message
Unexpected contact deserves an identity check before you share account information.
Urgency as a warning sign
A demand to act immediately can make it harder to check who is contacting you and what is being requested.
Protecting one-time security codes
A one-time code is intended for the process that generated it.
Password reuse and account exposure
Reusing a password connects otherwise separate accounts.
Recognising a lookalike address
Read the actual address before trusting a page's branding.
Remote-access requests from strangers
A person claiming to fix an account problem may ask to view or control your device.
Saving suspicious messages safely
Preserve enough information to explain a suspicious message without interacting with its links or attachments.
Reviewing account sessions
If a service offers a session or device list, review it through the genuine account settings.
A transfer record is not an identity check
A public transfer record can describe activity associated with an address, but it does not automatically identify the legal person controlling that address.
Crypto recovery guarantees
Be cautious of anyone promising a guaranteed recovery of lost cryptocurrency, especially after contacting you unexpectedly.
Why a screenshot of a balance is limited
A displayed balance is an observation about an interface.
Price changes and complaint evidence
When a dispute concerns a crypto-denominated amount, record the asset quantity separately from any currency estimate.
Requests to pay to unlock funds
A demand for another payment to release allegedly recoverable money deserves independent scrutiny.
Private keys and recovery phrases
A wallet recovery phrase or private key is sensitive access information.
Technical language does not prove legitimacy
Complex terminology can make an unsupported claim sound authoritative.
Reporting a suspected crypto scam
Prepare a factual summary, preserve relevant communications and find the reporting route appropriate to your location.
Making a redacted evidence copy
Preserve an untouched original before editing a copy for sharing.
Choosing what evidence to share
Start with the recipient's stated need and send the minimum relevant material.
Public posts versus private case files
A public account should be a carefully reduced version of a private evidence file.
Keeping an evidence folder organised
A clear folder structure reduces accidental sharing and makes records easier to find.
Reading a privacy notice for a case
Focus on the parts relevant to the information involved in your issue: the named organisation, purposes described, contact route and any stated retention arrangements.
Preparing a personal-data question
A specific question can clarify how information in an existing case is being handled.
Sharing evidence with a trusted adviser
Before transferring a case file, confirm who will receive it, why they need it and how they want it supplied.
Reviewing records after a case ends
When a case closes, review which records you still need and how they are stored.
A source country is not an availability list
A jurisdiction label in a research directory should tell readers what the source concerns.
Great Britain versus a global brand
A notice concerning a Great Britain service should retain that scope when summarised.
Reading an Australian enforcement record
An Australian enforcement record should be read for the entity, service, conduct and date it specifies.
International readers and local rules
An English-language article can be read around the world, but the sources behind it may be local.
Residence, location and source scope
Different documents may refer to residence, physical location or the territory in which a service is regulated.
Why there is no universal licence badge
A single badge cannot communicate all the entity, activity, territory and timing questions relevant to licensing research.
Comparing jurisdictions without ranking them
A useful comparison explains what each source covers and where the information differs.
Checking the age of jurisdiction guidance
Guidance can become outdated even when the webpage remains accessible.
What source documented means
On Operator Atlas, source documented means a research file has an attached primary-source record.
What research pending means
Research pending identifies an incomplete operator file.
Why this directory uses no star ratings
The current directory has no comparable first-hand testing dataset or defined performance-scoring model.
How a correction should be documented
A correction should explain what changed, why it changed and which source supports the new wording.
AI assistance and editorial limits
This edition uses AI-assisted drafting and software-assisted publishing.
When a profile is ready for a conclusion
A conclusion needs a defined question and evidence that directly addresses it.
Editorial independence and financial links
Readers should be able to understand how commercial relationships affect a publication.
Reading the limitations of this edition
Operator Atlas is a developing research publication with a small operator evidence register and a broader reference library.
Taking a break from a difficult case
A dispute can become harder to organise when every new message feels urgent.
Finding gambling-related support
If gambling is affecting your wellbeing, a dedicated support service can help you explore options.
Helping someone organise a complaint
Practical help can begin with listening and arranging the person's records in a way they understand.
Separating recovery hopes from evidence
After a financial loss, a confident promise of recovery can be especially persuasive.
Preparing questions for an adviser
An adviser can usually work more efficiently when the issue and uncertainties are clear.
Reducing repeated checking
Reopening the same pages without a new research question can add stress without producing new information.
A calm handover note
If someone else will help with a case, prepare a short handover describing the issue, current stage, relevant documents and next unanswered question.
Knowing the limits of a research website
A research website can organise public information and explain how to read it.
No matching guides
Try a shorter term or choose another topic.